Description of problem: After approving the host on "oVirt", the "NICs" are disordered. Only eth0 is OK... eth0 -> eth0 (NICE) eth1 -> eth5 eth2 -> eth6 eth3 -> eth4 /etc/udev/rules.d/70-persistent-net.rules duplicate info Version-Release number of selected component (if applicable): ovirt-node-iso-3.0.4-1.0.201401291204.vdsm.el6.iso How reproducible: Steps to Reproduce: 1. Install oVirt Node 2. Config network / hostname / DNS 3. Enable SSH password authentication 4. Enter Management Server / Port / Password and Save & Register 5. Aprove in oVirt Manager Actual results: eth0 eth4 eth5 eth6 Expected results: eth0 eth1 eth2 eth3 Additional info: [root@ptihost-vdsm-dev04 admin]# cd /etc/udev/rules.d/ [root@ptihost-vdsm-dev04 rules.d]# ls 12-ovirt-iosched.rules 60-raw.rules 70-persistent-cd.rules 70-persistent-net.rules 71-persistent-node-net.rules 80-kvm.rules 90-hal.rules 98-kexec.rules 99-fuse.rules [root@ptihost-vdsm-dev04 rules.d]# cat 70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:cb", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x8086:0x1096 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:c8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x1096 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:c9", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:ca", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:cb", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4" # PCI device 0x8086:0x1096 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:c9", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5" # PCI device 0x8086:0x1096 (e1000e) (custom name provided by external tool) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:c8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x105e (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:4a:10:ca", ATTR{type}=="1", KERNEL=="eth*", NAME="eth6" [root@ptihost-vdsm-dev04 rules.d]# [root@ptihost-vdsm-dev04 rules.d]# dmesg | grep rename udev: renamed network interface eth3 to eth4 udev: renamed network interface eth1 to eth5 udev: renamed network interface eth2 to eth6
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.4.2 as it has priority high, please retarget if needed. If this is a blocker please add it to the tracker Bug #1095370
This is an automated message: oVirt 3.4.2 has been released. This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.
dougland: any ideas? This looks like it's interaction with vdsm after approval.
Moving this to Douglas, as he might be closer to the cause.
Hello Laercio, (In reply to Laercio Motta from comment #0) > Description of problem: > After approving the host on "oVirt", the "NICs" are disordered. > Only eth0 is OK... > > eth0 -> eth0 (NICE) > eth1 -> eth5 > eth2 -> eth6 > eth3 -> eth4 > > /etc/udev/rules.d/70-persistent-net.rules duplicate info > > Version-Release number of selected component (if applicable): > ovirt-node-iso-3.0.4-1.0.201401291204.vdsm.el6.iso > > How reproducible: > > > Steps to Reproduce: > 1. Install oVirt Node > 2. Config network / hostname / DNS > 3. Enable SSH password authentication > 4. Enter Management Server / Port / Password and Save & Register > 5. Aprove in oVirt Manager > > Actual results: > eth0 > eth4 > eth5 > eth6 > I have tried with the below isos and it worked, I can't see the interfaces in the wrong order in TUI or oVirt Engine. BTW, where do you see this wrong order in TUI or oVirt Engine? oVirt Node: http://resources.ovirt.org/releases/3.3/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm34.el6.iso http://resources.ovirt.org/releases/3.3/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm33.el6.iso Thanks!
In version: oVirt Node - 3.0.4 - 1.0.201401291204.el6 Not mentioned problem exists Works OK!