[ovirt-users] Re: oVirt test clustered DOA after upgrade to latest 4.4.2 (AFAIK). Network issue?

Hello, Many thanks for the prompt reply. Answers in-line On Fri, Oct 23, 2020 at 9:16 AM Ales Musil <amusil(a)redhat.com&gt; wrote: > > It would be nice to know when this happens as it might be a serious problem. I can't offer much beyond the logs I uploaded. I had a similar event in one of my production GlusterFS / oVirt clusters, but restoring the missing ifcfg- files from backup and restarting NetworkManager solved the problem.

> > Unfortunately this won't work. From this it seems like vdsm persistence was broken somehow during the upgrade. > > For start you can really ensure that the network is not saved in the vdsm configuration. > By using vdsm-tool on the host, if you run "vdsm-tool list-nets" it won't produce anything most likely. > > To restore your previous configuration on the host you can use: > > cat << EOF > ovirtmgmt.json > { > "networks": { > "ovirtmgmt": { > "netmask": "255.255.255.0", > "ipv6autoconf": false, > "nic": "onb0", > "bridged": true, > "ipaddr": "192.168.2.117", > "defaultRoute": true, > "dhcpv6": false, > "gateway": "192.168.2.100", > "mtu": 1500, > "switch": "legacy", > "stp": false, > "bootproto": "none", > "nameservers": [ > "192.168.2.100", > "8.8.8.8" > ] > } > }, > "bondings": {}, > "options": { > "connectivityCheck": false > } > } > EOF > > vdsm-client -f ovirtmgmt.json Host setupNetworks > > If that works, you have to persist the configuration before reboot, so either from the engine UI > or from the host itself: > > vdsm-client Host setSafeNetworkConfig Worked like a charm! Thanks! Have a good weekend, Gilboa