Created attachment 998284 [details] logs libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-rhevm' Description of problem: When adding new host to setup and running [root@localhost ~]# vdsm-tool restore-nets it ends up with following error libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-rhevm' however network vdsm-rhevm seems to be existent root@localhost ~]# virsh net-list Please enter your authentication name: vdsm@rhevh Please enter your password: Name State Autostart Persistent -------------------------------------------------- ;vdsmdummy; active no no vdsm-rhevm active yes yes Version-Release number of selected component (if applicable): RHEV 3.5.0-2 vdsm-4.16.8.1-7.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. install new host to RHEVM 2. run vdsm-tool restore-nets on the host Actual results: Network not found: no network with matching name 'vdsm-rhevm' Expected results: network configuration is restored to pre-vdsm state Additional info: this test was done on nested VM used as a host
The error message quoted in the summary is a red herring. See bug 1121571. On the relevant host I see that the rhevm network has been successfully persisted: # cat /var/lib/vdsm/persistence/netconf/nets/rhevm {"bondingOptions": "arp_all_targets=0", "mtu": "1500", "bonding": "bond0", "bootproto": "dhcp", "STP": "no", "bridged": "true", "defaultRoute": true} So that vdsm-tool restore-nets seems to be doing what it should. Could you repeat the installation process, but ask Engine not to call setSafeNetworkConfig after setting up the rhevm network?
Based on the verification of bug 1197668 with my suggestion on comment 1, I understand that this was a false alarm due to bug 1121571.