Description of problem: After applying the workaround in vdsm.conf from https://access.redhat.com/solutions/1346443, none of the network interfaces are working so RHEV-M cannot connect. When trying to change it on the RHEV-H console, it gives me this error: "An error appeared in the UI: UnknownNicError("Unknown network interface: 'eth0'",)" Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization Hypervisor 6.6 (20150128.0.el6ev) How reproducible: Unknown Steps to Reproduce: 1. Hit issues in Solution 1346443 2. Attempt to configure this in Unified Persistence as workaround 3. Error: "An error appeared in the UI: UnknownNicError("Unknown network interface: 'eth0'",)" Actual results: "An error appeared in the UI: UnknownNicError("Unknown network interface: 'eth0'",)", reinstall Expected results: eth0 is an accepted network interface and configuration sticks. Additional info:
RHEV-H QE can reproduce this bug. Test version: rhev-hypervisor6-6.6-20150128.0 ovirt-node-3.2.1-6.el6.noarch RHEVM VT14.3 (3.5.1-0.4) Test steps: 1. Install RHEV-H 6.6-20150128. 2. Configure network with [bond+ vlan]. 3. Add rhevh to RHEV-M via RHEV-M UI. 4. Maintenance the host. 5. Upgrade to rhev-hypervisor6-6.6-20150128 via RHEVM Test results: 1. The host show as Non responsive status. 2. Networking show as "Unknown" and the host can't obtain IP. 3. Try to configure bond1, below error appeared. "An error appeared in the UI: UnknownNicError("Unknown network interface: 'bond1'",)" press enter to logout. or press s to drop to shell.
This is interesting. This error is only shown when udev is not aware of the NIC - and thats hould only happen if the nic is really (physically) not present. Form a host where this error appears, and in the state where the error appears, can someone provide the output of: $ python <<EOP from ovirt.node.utils import network as n print(n.all_ifaces()) EOP $ ip link
(In reply to Fabian Deutsch from comment #4) > This is interesting. > > This error is only shown when udev is not aware of the NIC - and thats hould > only happen if the nic is really (physically) not present. > > Form a host where this error appears, and in the state where the error > appears, can someone provide the output of: > > $ python <<EOP > from ovirt.node.utils import network as n > print(n.all_ifaces()) > EOP > $ ip link # python <<EOP > from ovirt.node.utils import network as n > print(n.all_ifaces()) > EOP ['eth0', 'eth1', 'eth2', 'eth3', 'bond1', 'lo'] [root@hp-xw4550-02 admin]# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:10:18:81:a4:a0 brd ff:ff:ff:ff:ff:ff 3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP qlen 1000 link/ether 00:10:18:81:a4:a2 brd ff:ff:ff:ff:ff:ff 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:23:7d:53:ab:75 brd ff:ff:ff:ff:ff:ff 5: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond1 state UP qlen 1000 link/ether 00:10:18:81:a4:a2 brd ff:ff:ff:ff:ff:ff 9: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether 00:10:18:81:a4:a2 brd ff:ff:ff:ff:ff:ff NOTE： The original nic IP was lost, I have to configure a public ip(eth2) for get above output . Thanks!
Robert, does this issue still exist in the regular use case of the customer with RHEV-H for 3.5.1?
I'm closing this due to no reply, please reopen if needed.
In addition to the sosreport please provide the file /etc/default/ovirt from the affected host.
Closing this bug due to no reply, please reopen if needed.