OSPFfv3 routes sync issue in FRR 8.1

[ammaryounus]

The new ipv6 ospf6 area command introduced in frr 8.1 to add the interface in an area was found to introduce an unexpected functionality. That is, when the machine is added to a certain topology, it only captures the routes already present but does not learn the new routes afterward.
Another noticeable difference found b/w the two commands after comparison of the source code was that the old interface area command schedules a recurring function ospf6_abr_task_timer on a separate thread that performs ABR related processing on uniform intervals. Whereas the new ipv6 ospf6 command doesn’t. Refer to the code snippets attached below.
/ospf6d/ospf6_top.c → ospf6_interface_area

FRR 8.0
/ospf6d/ospf6_top.c → ospf6_interface_area
/* If the router is ABR, originate summary routes */
if (ospf6_check_and_set_router_abr(ospf6)) {
ospf6_abr_enable_area(oa);
ospf6_schedule_abr_task(oa->ospf6);
}
FRR 8.1
/ospf6d/ospf6_interface.c → ospf6_interface_start

/* If the router is ABR, originate summary routes */
if (ospf6_check_and_set_router_abr(ospf6))
ospf6_abr_enable_area(oa);

It seems after adding "ospf6_schedule_abr_task(oa->ospf6);" to (/ospf6d/ospf6_interface.c → ospf6_interface_start ) the issue is gone