Description of problem: Networks that not created via TUI are not persistent After upgrading rhev-h 6.6 from 3.5.0(rhev-hypervisor6-6.6-20150128.0.el6ev.noarch.rpm >>to 3.5.1(rhev-hypervisor6-6.6-20150402.0.el6ev). When host rebooting after upgrade, 'rhevm' doesn't exists(no ifcfg file), or any other network that wasn't created via TUI. But manually configured bond0(TUI), for example is persist after boot. Version-Release number of selected component (if applicable): 3.5.1-0.3.el6ev rhev-hypervisor6-6.6-20150128.0.el6ev How reproducible: always Steps to Reproduce: 1. clean host with rhev-hypervisor6-6.6-20150128.0.el6ev installed(3.5.0) 2. Via TUI, configure for example bond0 and bond0.162 and save 3. Install host in RHEV-M(vt14.2), 'rhevm' will be created on the NIC with the ip 4. Attach VM vlan tagged network(162) to bond0 via SetupNetworks and approve operation 5. install rhev-h 6.6 3.5.1, for example- rhev-hypervisor6-6.6-20150402.0.el6ev(unsigned build) on engine 6. Put host in maintenance and press 'Upgrade' via GUI/webadmin Actual results: After installation finished and host finished rebooting, there is no networks exists on host, no ifcfg files for those networks. host has no ip. Expected results: All networks should be persistent after reboot. Additional info: Looks like there is no 'persist' for networks that wasn't created via TUI on rhev-h 6.6 3.5.0 build.
Created attachment 1011755 [details] relevant logs
consider this bug is duplicate of bug 1209401. Bug 1209401 - ifcfg-rhevm is not persisted when rhevh network is configured contain vlan+bond via TUI
*** Bug 1209401 has been marked as a duplicate of this bug. ***
Hi, I have provided a good data about this behaviour in: https://bugzilla.redhat.com/show_bug.cgi?id=1209401#c7 Copy/paste here: ===================== - Install RHEV-H 20150127.0 # cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor 7.0 (20150127.0.el7ev) # rpm -qa | grep -i vdsm vdsm-xmlrpc-4.16.8.1-6.el7ev.noarch vdsm-python-4.16.8.1-6.el7ev.noarch vdsm-cli-4.16.8.1-6.el7ev.noarch vdsm-yajsonrpc-4.16.8.1-6.el7ev.noarch vdsm-4.16.8.1-6.el7ev.x86_64 vdsm-hook-ethtool-options-4.16.8.1-6.el7ev.noarch ovirt-node-plugin-vdsm-0.2.0-18.el7ev.noarch vdsm-python-zombiereaper-4.16.8.1-6.el7ev.noarch vdsm-jsonrpc-4.16.8.1-6.el7ev.noarch vdsm-reg-4.16.8.1-6.el7ev.noarch vdsm-hook-vhostmd-4.16.8.1-6.el7ev.noarch - Setup the nic to dhcp via network TUI - Register to RHEV-M via TUI (or call via shell /usr/share/vdsm-reg/vdsm-reg-setup) - Approve in RHEV-M Web admin * Host will be up, the network settings will be available via /etc/sysconfig/network-scripts/ but not persisted. Data from tests ======================= #1 Settings when configuring network via ovirt-node TUI # ls -la /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 137 Apr 8 17:06 /etc/sysconfig/network-scripts/ifcfg-ens3 -rw-r--r--. 1 root root 64 Apr 8 17:06 /etc/sysconfig/network-scripts/ifcfg-lo # cat /config/etc/sysconfig/network-scripts/ifcfg-ens3 BOOTPROTO="dhcp" DEVICE="ens3" HWADDR="52:54:00:da:98:4e" IPV6INIT="no" IPV6_AUTOCONF="no" NM_CONTROLLED="no" ONBOOT="yes" PEERNTP="yes" # cat /config/etc/sysconfig/network-scripts/ifcfg-lo DEVICE="lo" IPADDR="127.0.0.1" NETMASK="255.0.0.0" ONBOOT="yes" Both files are persisted correctly: **************************************************** # ls /config/etc/sysconfig/network-scripts/ ifcfg-ens3 ifcfg-lo Registered the node into rhevm ===================================== Host will be pending approval in RHEV-M web admin, however the network settings in the node vdsm now owns it: # cat /etc/sysconfig/network-scripts/ifcfg-ens3 # Generated by VDSM version 4.16.8.1-6.el7ev DEVICE=ens3 HWADDR=52:54:00:da:98:4e BRIDGE=rhevm ONBOOT=yes NM_CONTROLLED=no IPV6_AUTOCONF=no PEERNTP=yes IPV6INIT=no # cat /etc/sysconfig/network-scripts/ifcfg-rhevm # Generated by VDSM version 4.16.8.1-6.el7ev DEVICE=rhevm TYPE=Bridge DELAY=0 STP=off ONBOOT=yes BOOTPROTO=dhcp DEFROUTE=yes NM_CONTROLLED=no IPV6_AUTOCONF=no PEERNTP=yes IPV6INIT=no HOTPLUG=no However, there is no more ifcfg-ens3 persisted or ifcfg-rhevm file: # ls /config/etc/sysconfig/network-scripts/ ifcfg-lo The persist command in ovirt-node also is working, as example in the same scenario I have execute the persist into ifcfg-rhevm: # ls /config/etc/sysconfig/network-scripts/ ifcfg-lo # persist /etc/sysconfig/network-scripts/ifcfg-rhevm # ls /config/etc/sysconfig/network-scripts/ifcfg-rhevm Additional data ================= vdsm-reg.log MainThread::DEBUG::2015-04-08 17:27:37,754::deployUtil::487::root::Bridge rhevm not found, need to create it. MainThread::DEBUG::2015-04-08 17:27:37,754::vdsm-reg-setup::94::root::renameBridge begin. MainThread::DEBUG::2015-04-08 17:27:37,754::deployUtil::1015::root::makeBridge begin. MainThread::DEBUG::2015-04-08 17:27:37,755::deployUtil::438::root::_getMGTIface: read host name: 192.168.122.70 MainThread::DEBUG::2015-04-08 17:27:37,755::deployUtil::446::root::_getMGTIface: using host name 192.168.122.70 strIP= 192.168.122.70 MainThread::DEBUG::2015-04-08 17:27:37,755::deployUtil::453::root::_getMGTIface IP=192.168.122.70 strIface=ens3 MainThread::DEBUG::2015-04-08 17:27:37,756::deployUtil::1059::root::makeBridge found the following bridge paramaters: ['BOOTPROTO=dhcp', 'IPV6INIT=no', 'IPV6_AUTOCONF=no', 'ONBOOT=yes', 'PEERNTP=yes'] MainThread::DEBUG::2015-04-08 17:27:37,760::deployUtil::140::root::['/usr/share/vdsm/addNetwork', 'rhevm', '', '', 'ens3', 'BOOTPROTO=dhcp', 'IPV6INIT=no', 'IPV6_AUTOCONF=no', 'ONBOOT=yes', 'PEERNTP=yes', 'blockingdhcp=true'] MainThread::DEBUG::2015-04-08 17:27:42,537::deployUtil::149::root:: MainThread::DEBUG::2015-04-08 17:27:42,538::deployUtil::150::root::libvirt: Network Driver error : Network not found: no network with matching name 'vdsm-rhevm' MainThread::DEBUG::2015-04-08 17:27:42,538::deployUtil::140::root::['/usr/share/vdsm/get-conf-item', '/etc/vdsm/vdsm.conf', 'vars', 'net_persistence', 'ifcfg'] MainThread::DEBUG::2015-04-08 17:27:42,555::deployUtil::149::root::unified MainThread::DEBUG::2015-04-08 17:27:42,555::deployUtil::150::root:: MainThread::DEBUG::2015-04-08 17:27:42,556::deployUtil::140::root::['/usr/share/vdsm/vdsm-store-net-config', 'unified'] MainThread::DEBUG::2015-04-08 17:27:43,869::deployUtil::149::root:: MainThread::DEBUG::2015-04-08 17:27:43,869::deployUtil::150::root:: MainThread::DEBUG::2015-04-08 17:27:43,869::deployUtil::1144::root::makeBridge return. MainThread::DEBUG::2015-04-08 17:27:43,870::deployUtil::140::root::['/usr/share/vdsm/vdsm-store-net-config'] MainThread::DEBUG::2015-04-08 17:27:43,883::deployUtil::149::root:: MainThread::DEBUG::2015-04-08 17:27:43,883::deployUtil::150::root:: MainThread::ERROR::2015-04-08 17:27:43,883::vdsm-reg-setup::124::root::renameBridge: failed to chmod bridge file MainThread::DEBUG::2015-04-08 17:27:43,883::vdsm-reg-setup::126::root::renameBridge return. MainThread::DEBUG::2015-04-08 17:27:43,884::vdsm-reg-setup::238::root::execute: after renameBridge: False MainThread::DEBUG::2015-04-08 17:27:43,884::vdsm-reg-setup::316::root::Registration status: False Please note that the first registration failed after /usr/share/vdsm/vdsm-store-net-config and /var/lib/vdsm/netconfback is empty so in the end the chmod operation couldn't be executed or even file persisted. More detailed from vdsm-reg-setup.in ========================================== SCRIPT_NAME_SAVE = "vdsm-store-net-config" # Rename existing bridge fReturn = deployUtil.makeBridge(self.vdcName, self.vdsmDir) if not fReturn: logging.error("renameBridge Failed to rename existing bridge!") # Persist changes if fReturn: try: out, err, ret = deployUtil._logExec( [os.path.join(self.vdsmDir, SCRIPT_NAME_SAVE)]) <snip> os.chmod( ( "/config/etc/sysconfig/network-scripts/ifcfg-" + MGT_BRIDGE_NAME ), 0o644 ) except: fReturn = False logging.error("renameBridge: failed to chmod bridge file") From deployUtil.py ======================= # Add bridge if fReturn: try: lstBridgeOptions.append('blockingdhcp=true') out, err, ret = _logExec([os.path.join(vdsmDir, SCRIPT_NAME_ADD), bridgeName, vlan, bonding, nic] + lstBridgeOptions) if ret: raise Exception('Failed to add bridge') # Save current config by removing the undo files: try: if fReturn: if fIsOvirt: out, err, ret = _logExec( [os.path.join(vdsmDir, SCRIPT_NAME_GET_CONFIG), P_VDSM_CONF, 'vars', 'net_persistence', 'ifcfg']) if ret: raise Exception('Failed to retrieve vdsm persistence ' 'mode. Stderr: %s' % err) net_persistence = out.strip() out, err, ret = _logExec( [os.path.join(vdsmDir, SCRIPT_NAME_STORE_NET_CONFIG), net_persistence]) if ret: raise Exception('Failed to persist vdsm networking ' 'configuration. Stderr: %s' % err) else: setSafeVdsmNetworkConfig() From this perspective ovirt-node is working as expected, I am moving to vdsm component for the vdsm. Please let me know if you guys have any patch or test so I can quickly help.
Thanks Douglas! Unfortunately changing the component clears acks - Yaniv and Meni, please (re)ack.
Thanks Douglas. Root cause analysis: 1. rhev-h 3.5.x is installed. 2. Host is configured with initial network configuration manually using the rhev-h TUI. This configuration (ifcfg files) is persisted in disk. 3. Host is registered on an engine, which in turn installs a "rhevm" mgmt network which is a bridged network, meaning, the IP address will be now configured on a new bridge device, that is connected on top of the devices that were configured in step 2. * The bridge device's ifcfg files are never persisted by vdsm but the unified persistence JSON files are. This behavior is specific to 3.5.X and later + rhev-h configuration. 4. After an upgrade to 3.5.y (which includes a host reboot) the bridge is gone and with it, the IP address. The host is left with no mgmt IP. If this happened to be the only device with IP the host had, it is left with no IP. This will fail libvirt and vdsm process to run on boot and restore all network configuration. The comment on step 3 explains why this does not reproduce if step 1 includes a thev-h 3.4.x installation.
the above behavior was introduced into vdsm after https://bugzilla.redhat.com/show_bug.cgi?id=1165203
Hi, (In reply to Ido Barkan from comment #7) > * The bridge device's ifcfg files are never persisted by vdsm but the > unified persistence JSON files are. This behavior is specific to 3.5.X and > later + rhev-h configuration. That explains why I cannot find it in comment#4, thanks for the reminder Ido. Based on the above statement and my last talk with Michael Burman which says to reproduce this issue is not required vlan (different issue, probably bz#1209401), I tried a new tests, below the results: RHEV-M version: 3.5.1-0.4 Scenario #1: =============== - Installed rhev-h-6.6-20150128.0 and configured via TUI the 2 nics for bonding and setup *static* ip address. - Put root password (and enabled sshd) via RHEV-M TUI tab. - From RHEV-M web admin install the rhev-h, wait until it get UP in the status - Put in maint. - Reboot - Activate the host when it's back, host is UP. Additional notes: - vdsm-4.16.8.1-6.el6ev - After approval in RHEV-M interface no file are persisted in /config/etc/sysconfig/network-scripts, only ifcfg-lo is available but it's okay as the above statement from Ido. I also noticed the vdsm created the files correctly in /etc/sysconfig/network-scripts (ifcfg-bond0, ifcfg-eth0, ifcfg-eth1, ifcfg-rhevm). Scenario #2: ================ Using the scenario#1, rhev-h-6.6-20150128.0 is up and working, I have upgraded to rhev-h-6.6-20150402.0.el6ev. - Put the host rhev-h-6.6-20150128.0 in Maintenance. - Click in Upgrade item via RHEV-M webadmin page and selected the iso rhevh-6.6-20150402.0.el6ev - Host upgraded and rebooted - Host is UP in RHEV-M admin webpage. Additional notes: - vdsm-4.16.13-1.el6ev - No file are persisted in /config/etc/sysconfig/network-scripts, only ifcfg-lo is available but it's okay as the above statement from Ido. I also noticed the vdsm created the files correctly in /etc/sysconfig/network-scripts (ifcfg-bond0, ifcfg-eth0, ifcfg-eth1, ifcfg-rhevm). Scenario #3: ================= - Installed rhev-h-6.6-20150304.0.el6ev and configured via TUI the 2 nics for bonding and setup static ip address. - Put root password (and enabled sshd) via RHEV-M TUI tab. - From RHEV-M web admin install the rhev-h, wait until it get UP in the status - Put in maint. - Reboot - Activate the host when it's back, host is UP. Additional notes: - vdsm-4.16.8.1-7.el6ev - ifcfg-bond0, ifcfg-eth0, ifcfg-eth1, ifcfg-rhevm, ifcfg-lo are available in /etc/sysconfig/network-scripts and *also* persisted in /config/etc/sysconfig/network-scripts Scenario #4: =================== Using the scenario#1, rhev-h-6.6-20150304.0.el6ev is up and working, I have upgraded to rhev-h-6.6-20150402.0.el6ev. - Put the host rhev-h-6.6-20150304.0.el6ev in Maintenance. - Click in Upgrade item via RHEV-M webadmin page and selected the iso rhevh-6.6-20150402.0.el6ev - Host upgraded and rebooted - Host is UP in RHEV-M admin webpage. Additional notes: - vdsm-4.16.13-1.el6ev - In /config/etc/sysconfig/network-scripts/ is persisted (ifcfg-bond0, ifcfg-eth0, ifcfg-eth1, ifcfg-lo) *not* ifcfg-rhevm - However, in /etc/sysconfig/network-scripts/ there are ifcfg-rhevm, ifcfg-bond0, ifcfg-eth0, ifcfg-eth1, ifcfg-lo and everything is working. Scenario #5: =============== - Installed rhev-h-6.6-20150304.0.el6ev and configured via TUI the 2 nics for bonding and setup *DHCP* ip address. - Put root password (and enabled sshd) via RHEV-M TUI tab. - From RHEV-M web admin install the rhev-h, wait until it get UP in the status - Put in maint. - Reboot - Activate the host when it's back, host is UP. Scenario #6: =================== Using the scenario#5 (network settings as DHCP), rhev-h-6.6-20150304.0.el6ev is up and working, I have upgraded to rhev-h-6.6-20150402.0.el6ev. - Put the host rhev-h-6.6-20150304.0.el6ev in Maintenance. - Click in Upgrade item via RHEV-M webadmin page and selected the iso rhevh-6.6-20150402.0.el6ev - Host upgraded and rebooted - Host is UP in RHEV-M admin webpage. Scenario #7: =================== - Installed rhev-h-6.6-20150128.0 and configured via TUI the 2 nics for bonding and setup *DHCP* ip address. - Put root password (and enabled sshd) via RHEV-M TUI tab. - From RHEV-M web admin install the rhev-h, wait until it get UP in the status - Put in maint. - Reboot - Activate the host when it's back, host is UP. Scenario #8: =================== Using the scenario#7 (network settings as DHCP), rhev-h-6.6-20150128.0 is up and working, I have upgraded to rhev-h-6.6-20150402.0.el6ev. - Put the host rhev-h-6.6-20150304.0.el6ev in Maintenance. - Click in Upgrade item via RHEV-M webadmin page and selected the iso rhevh-6.6-20150402.0.el6ev - Host upgraded and rebooted - Host is UP in RHEV-M admin webpage. Ido/Fabian/Lior/Michael, I do believe we should close this bug as not a bug and focus in the below bug as it involves vlan: [RHEV-H] vdsm is down after upgrade from 3.5.0 to 3.5.1 https://bugzilla.redhat.com/show_bug.cgi?id=1209401 Thanks Douglas
So this is the last update regrading this issue, Danken/Ido please add your comments. thank you. My last reproduction: Clean rhevh-6.6-20150128.0.el6ev.iso installed from USB 1) Via TUI configured bond0.162 ls -l /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:36 /etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 126 2015-04-19 12:36 /etc/sysconfig/network-scripts/ifcfg-bond0.162 -rw-r--r--. 1 root root 99 2015-04-19 12:36 /etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:36 /etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 64 2015-04-19 12:36 /etc/sysconfig/network-scripts/ifcfg-lo ls -l /config/etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:36 /config/etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 126 2015-04-19 12:36 /config/etc/sysconfig/network-scripts/ifcfg-bond0.162 -rw-r--r--. 1 root root 99 2015-04-19 12:36 /config/etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:36 /config/etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 64 2015-04-19 12:36 /config/etc/sysconfig/network-scripts/ifcfg-lo grep ifcfg /config/files /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-em1 /etc/sysconfig/network-scripts/ifcfg-em2 /etc/sysconfig/network-scripts/ifcfg-bond0.162 /etc/sysconfig/network-scripts/ifcfg-lo ls -l /var/run/vdsm/ ls -l /var/lib/vdsm/ 2) Rebooted host 1 time, without installing in RHEVM s -l /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 126 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-bond0.162 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 64 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-lo ls -l /config/etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 126 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-bond0.162 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 64 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-lo grep ifcfg /config/files /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-em1 /etc/sysconfig/network-scripts/ifcfg-em2 /etc/sysconfig/network-scripts/ifcfg-bond0.162 /etc/sysconfig/network-scripts/ifcfg-lo ls -l /var/run/vdsm/ ls -l /var/lib/vdsm 3) Installed host in RHEV-M, 'rhevm' created on bond0.162 and 2 networks attached to 2 NICs via SN 'ff' and 'lior' ls -l /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-bond0 -rw-rw-r--. 1 root root 132 2015-04-19 13:25 /etc/sysconfig/network-scripts/ifcfg-bond0.162 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-em2 -rw-rw-r--. 1 root root 142 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-ff -rw-rw-r--. 1 root root 144 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-lior -rw-r--r--. 1 root root 64 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-lo -rw-rw-r--. 1 root root 128 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-p1p1 -rw-rw-r--. 1 root root 130 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-p1p2 -rw-rw-r--. 1 root root 162 2015-04-19 13:25 /etc/sysconfig/network-scripts/ifcfg-rhevm ls -l /config/etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 64 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-lo grep ifcfg /config/files /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-em1 /etc/sysconfig/network-scripts/ifcfg-em2 /etc/sysconfig/network-scripts/ifcfg-lo ls -l /var/lib/vdsm/persistence/netconf/nets/ total 6 -rw-r--r--. 1 root root 62 2015-04-19 13:26 ff -rw-r--r--. 1 root root 62 2015-04-19 13:26 lior -rw-r--r--. 1 root root 173 2015-04-19 13:26 rhevm - no bonds under /netconf ls -l /var/run/vdsm/netconf/nets/ total 12 -rw-r--r--. 1 root root 62 2015-04-19 13:26 ff -rw-r--r--. 1 root root 62 2015-04-19 13:26 lior -rw-r--r--. 1 root root 173 2015-04-19 13:26 rhevm - no bonds under /netconf 4) Upgrade host to rhev-hypervisor6-6.6-20150416.0.iso(unsigned build) via USB and rebooted host: ls -l /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-em2 -rw-rw-r--. 1 root root 142 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-ff -rw-rw-r--. 1 root root 144 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-lior -rw-r--r--. 1 root root 64 2015-04-19 12:56 /etc/sysconfig/network-scripts/ifcfg-lo -rw-rw-r--. 1 root root 128 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-p1p1 -rw-rw-r--. 1 root root 130 2015-04-19 13:26 /etc/sysconfig/network-scripts/ifcfg-p1p2 ls -l /config/etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 101 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 99 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 64 2015-04-19 12:56 /config/etc/sysconfig/network-scripts/ifcfg-lo grep ifcfg /config/files /etc/sysconfig/network-scripts/ifcfg-bond0 /etc/sysconfig/network-scripts/ifcfg-em1 /etc/sysconfig/network-scripts/ifcfg-em2 /etc/sysconfig/network-scripts/ifcfg-lo ls -l /var/lib/vdsm/persistence/netconf/nets/ total 6 -rw-r--r--. 1 root root 62 2015-04-19 13:26 ff -rw-r--r--. 1 root root 62 2015-04-19 13:26 lior -rw-r--r--. 1 root root 173 2015-04-19 13:26 rhevm ls -l /var/run/vdsm/netconf/nets/ total 8 -rw-r--r--. 1 root root 62 2015-04-19 13:26 ff -rw-r--r--. 1 root root 62 2015-04-19 13:26 lior no 'rhevm', no 'bond0.162'. no ip. - Note, that this build rhev-hypervisor6-6.6-20150416.0.iso includes Fabian's fix for the libvird issue. libvirtd running and so vdsmd. dummyuglyhack: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN link/ether 9e:26:79:91:c9:77 brd ff:ff:ff:ff:ff:ff inet 99.99.99.99/32 scope global dummyuglyhack
This seems to require predefined bonds, therefore a duplicate. *** This bug has been marked as a duplicate of bug 1205711 ***