Thanks for the tip. I upgraded my cluster and one node (which started this thread) again picked up DHCP address after reboot. I checked /var/lib/vdsm/persistence/netconf/nets/ovirtmgmt and it _still_ had DHCP settings in it. And I had previously removed and added node to cluster. It seems that VDSM doesn't compare between settings in engine DB and node. Don't know if it because it "knows" that they are correct.
-Juhani On Sun, Mar 3, 2019 at 11:02 AM <[email protected]> wrote: > > I had this issue, I believe that when I tried to fix the network manually so > that ovirt could sync the correct config, vdsm was kicking in and overwriting > my changes with what it had stored in /var/lib/vdsm/persistence/netconf/ > before the sync took place. For whatever reason this was dhcp. > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/23MLUL2YU7VYFGQXSHZJ3CTC3ZMIHAMR/ -- Juhani Rautiainen [email protected] _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/OITO2EXPJZJJHTXO5SMYQLN7J7NOQ6K6/
