Hide Forgot
Description of problem: RHEV-H shouldn't up more than one nics in vlan ENV. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.2-20111215.0.el6_2 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H to vlan ENV machine (This machine have more than two nics ). 2. Configure first nic with correct vlan ID (e.g. 20). 3. Configure Second nic with correct vlan ID (e.g. 20). Actual results: All vlan nics can be configured and up. Expected results: RHEV-H shouldn't up more than one nics in vlan ENV. Additional info: ======================================================================= # ifconfig breth1 Link encap:Ethernet HWaddr 00:10:18:81:A4:A2 inet addr:192.168.20.48 Bcast:192.168.20.255 Mask:255.255.255.0 inet6 addr: 3ffe:501:ffff:100:210:18ff:fe81:a4a2/64 Scope:Global inet6 addr: fe80::210:18ff:fe81:a4a2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2936 errors:0 dropped:0 overruns:0 frame:0 TX packets:963 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:235202 (229.6 KiB) TX bytes:226113 (220.8 KiB) eth0 Link encap:Ethernet HWaddr 00:10:18:81:A4:A0 inet6 addr: fe80::210:18ff:fe81:a4a0/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:20129 errors:0 dropped:0 overruns:0 frame:0 TX packets:136 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1451691 (1.3 MiB) TX bytes:12724 (12.4 KiB) Interrupt:18 Memory:da000000-da012800 eth0.20 Link encap:Ethernet HWaddr 00:10:18:81:A4:A0 inet6 addr: fe80::210:18ff:fe81:a4a0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1930 errors:0 dropped:0 overruns:0 frame:0 TX packets:130 errors:0 dropped:9 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:97764 (95.4 KiB) TX bytes:10632 (10.3 KiB) eth1 Link encap:Ethernet HWaddr 00:10:18:81:A4:A2 inet6 addr: fe80::210:18ff:fe81:a4a2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21744 errors:0 dropped:0 overruns:0 frame:0 TX packets:1043 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1656260 (1.5 MiB) TX bytes:240215 (234.5 KiB) Interrupt:19 Memory:dc000000-dc012800 eth1.20 Link encap:Ethernet HWaddr 00:10:18:81:A4:A2 inet6 addr: fe80::210:18ff:fe81:a4a2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2982 errors:0 dropped:0 overruns:0 frame:0 TX packets:1009 errors:0 dropped:3 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:239056 (233.4 KiB) TX bytes:230205 (224.8 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:734 errors:0 dropped:0 overruns:0 frame:0 TX packets:734 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:111384 (108.7 KiB) TX bytes:111384 (108.7 KiB) rhevm Link encap:Ethernet HWaddr 00:10:18:81:A4:A0 inet addr:192.168.20.50 Bcast:192.168.20.255 Mask:255.255.255.0 inet6 addr: 3ffe:501:ffff:100:210:18ff:fe81:a4a0/64 Scope:Global inet6 addr: fe80::210:18ff:fe81:a4a0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1905 errors:0 dropped:0 overruns:0 frame:0 TX packets:91 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:95982 (93.7 KiB) TX bytes:8390 (8.1 KiB)
Created attachment 548517 [details] ovirt.log
Isn't in generally the case that we shall just allow to bring configure one interface using the TUI and that all other interfaces shall be configured by Engine as pointed out in bug #798646?
(In reply to comment #3) > Isn't in generally the case that we shall just allow to bring configure one > interface using the TUI and that all other interfaces shall be configured by > Engine as pointed out in bug #798646? Yes, we configure a single nic in rhev-h/ovirt-node and the management server is responsible for config of any other nics. This appears similar to bug 781929. While a warning that re-configuring will remove all existing configuration is good, we need to ensure that we actually clean up all the config. In the above situation, when the user configures eth0 with a vlan, then configures eth1 with a vlan, only eth1 and the bridge on eth1 should be up
(In reply to comment #4) > This appears similar to bug 781929. While a warning that re-configuring will > remove all existing configuration is good, we need to ensure that we actually > clean up all the config. In the above situation, when the user configures eth0 > with a vlan, then configures eth1 with a vlan, only eth1 and the bridge on eth1 > should be up The patch provided in bug #781929 actually removes all config files when a NIC get's configured. This includes the removal of VLANs. I just tested it as follows: - Install node with the patch given in bug #781929 - Configure the first NIC using DHCP and set the VLAN ID 20 - Configure the second NIC using DHCP and set the VLAN ID 20 This leads to the up interfaces: breth1 eth1 eth1.20 lo AFAIU this is what this bug requires, right? If so fixing bug #781929 is the next step.
If it really removes all files, then we should be good. I'd double check that no vlan files are kept around. IIRC, there are some that are stored in a different location.
Good point about that different location. It just removes all persisted ifcfg-* files in network-scripts.
I couldn't find any other persisted file after setting a VLAN ID, therefore I assume that it is just kept in the corresponding ifcfg file. That's also what I remember how it worked back in the Fedora 10 or so days. It seems to be fixed by bug #781929 and a user feedback given by bug #798646 should we also get this in Mike?).
Tech note for this is covered adequetely in Bug # 781929.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0741.html