frr package upgrade loses default OSPF area field and package upgrade hangs
I've seen this twice now. I just updated frr on this one unit to 0.6.7_2. The frr upgrade hangs at "Writing configuration... done.". This upgrade hang is also a common problem lately on upgrades.
After rebooting the default area is missing. The only reason I checked is because we recently had a different unit fail and discovered the field was mysteriously blank.
No idea what the real issue is... but just mentioning it case someone else finds this or has any ideas. I have a feeling it's going to be more of a problem in the future for us.
Losing the area value should be fixed in the latest update I just pushed.
The upgrade hanging is something we're still working on. It's not isolated to FRR, it happens to several packages.