OSPF just stops (different status flag)

Anyone have a solution to this OSPF problem?

My routers can be going and have adjacency for weeks or months and out of the blue they drop and won’t reform adjacency.
Different master status flag error.

So far only on RB750s it seems.

And up to at least 5.14

I had this problem a year or so ago when using PtMP or Broadcast. Switched to NBMA and it went away.

More recently I had a problem with NMBA using Mikrotik’s in Bridge mode - same error. Replaced the bridges with switches and so far no further issue but it’s only been a few days.

16:14:12 route,ospf,info Database Description packet has different master status flag 
16:14:12 route,ospf,info     new master flag=false 
16:14:12 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:14:34 route,ospf,info Database Description packet has different master status flag 
16:14:34 route,ospf,info     new master flag=false 
16:14:34 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:18:12 route,ospf,info Database Description packet has different master status flag 
16:18:12 route,ospf,info     new master flag=false 
16:18:12 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:18:35 route,ospf,info Database Description packet has different master status flag 
16:18:35 route,ospf,info     new master flag=false 
16:18:35 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:18:57 route,ospf,info Database Description packet has different master status flag 
16:18:57 route,ospf,info     new master flag=false 
16:18:57 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:21:53 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to Init 
16:22:19 route,ospf,info Database Description packet has different master status flag 
16:22:19 route,ospf,info     new master flag=false 
16:22:19 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:23:12 route,ospf,info Database Description packet has different master status flag 
16:23:12 route,ospf,info     new master flag=false 
16:23:12 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way 
16:23:35 route,ospf,info Database Description packet has different master status flag 
16:23:35 route,ospf,info     new master flag=false 
16:23:35 route,ospf,info OSPFv2 neighbor 10.255.3.3: state change from Full to 2-Way

v5.18

When I’ve raised this with MT support they’ve just said that it’ll be fixed in a ‘future version’ ‘maybe in october’ or similar. Not exactly the kind of response you’d hope for with a showstopper bug like this.

Can I ask if you have a routed or bridged network and what version did it happen on.