Out-of-sync - Host Network's configurations differ from DC
Hello Team, We had a power outage last week and we started observing the error on our oVirt cluster, where all the hosts went out-of-sync. When I select my ovirtmgmt interface it shows the out-of-sync symbol and shows IPv4 gateway ( Host - Null, DC - 10.xx..xx.xx) Same with my VM traffic network, it shows the out-of-sync symbol and shows IPv4 gateway ( Host - Null, DC - 10.xx..xx.xx) Please help me with my troubleshooting as we lost access to VM's access after our power outage. Thanks, Dawood.
Hello If you have done an update lately check this patch/commit Fix default route with libnl3.8+ Since libnl3.8, the nl_addr_parse function does not return 'none' anymore for 'default', but it returns a 0.0.0.0/0 addr. thom311/libnl@0c0aee8 But since we depend on that value in vdsm, it never reports a default gateway anymore, causing networks to be out of sync. So next to 'none' we also check for '0.0.0.0/0' or '::/0'. Signed-off-by: Jean-Louis Dupond <jean-louis@dupond.be> https://github.com/oVirt/vdsm/commit/49eaf70c5a14eb00e85eac5f91ac36f010a9a32...
Thank you! Noticed I am running below libnl versions on all my hosts yum list installed | grep libnl libnl3.x86_64 3.9.0-1.el9 @anaconda libnl3-cli.x86_64 3.9.0-1.el9 @anaconda I modified the file directly (./usr/lib/python3.9/site-packages/vdsm/network/netinfo/routes.py) based on github links - and route['destination'] == 'none' + and route['destination'] in ('none', '0.0.0.0/0', '::/0') - if r['destination'] == 'none' + if r['destination'] in ('none', '0.0.0.0/0', '::/0') After changing this, out-of-sync errors disappeared
participants (2)
-
g.vasilopoulos＠uoc.gr -
munnadawood＠gmail.com