Created attachment 1012583 [details] vlan-nic-info.png Description of problem: vlan network status show as "unknown" after upgrade from 6.5 to 6.6 via TUI. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20150115.0 rhev-hypervisor6-6.6-20150402.0 ovirt-node-3.2.2-3.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.5-20150115.0 to vlan host which have 2 nic(one vlan nic & one public nic). 2. Configure network with vlan ID (e.g. 20). 3. TUI upgrade to rhev-hypervisor6-6.6-20150402.0 4. Check network status. 5. Enter network menu, try to config another public nic. 6. Press F2 key to drop to shell mode, run ifconfig command. Actual results: 1. Step4, vlan network status show as "unknown" after upgrade from 6.5 to 6.6 via TUI. 2. Step5, It will drop to shell directly. 3. Step6, vlan IP can show correctly in shell. Expected results: 1. Vlan network still can obtain IP after upgrade from 6.5 to 6.6 via TUI. 2. User can config another nic after upgrade. Additional info: No such issue when upgrade via RHEVM.
Created attachment 1012585 [details] vlan.tag.gz
Hi shaochen, > Step4, vlan network status show as "unknown" after upgrade from 6.5 to 6.6 via > TUI. Could you please provide the steps to upgrade the node via TUI? Thanks!
(In reply to Douglas Schilling Landgraf from comment #2) > Hi shaochen, > > > Step4, vlan network status show as "unknown" after upgrade from 6.5 to 6.6 via > > TUI. > > Could you please provide the steps to upgrade the node via TUI? > > Thanks! 1. After finished rhev-hypervisor6-6.5-20150115.0 install and vlan(p3p1 nic) configure, reboot the host. 2. Enter pxe, choose the latest rhev-hypervisor6-6.6-20150402.0 profile, without doing anything append, and then press enter key directly. 3. It will jump to upgrading process, goes on press enter key, and input password. 4. reoot. In pxe profile the default BOOTIF=xxx always use the first nic(em1), but the vlan nic is p3p1, maybe the issue is there.
I'll also see if I can reproduce this on a system with multiple NICs
Maybe this is also related to bug 1209486
This bug is not a duplicate of bug 1209486 or bug 1209401 , because the upgrade in the description goes from 3.4.z to 3.5.1, and that upgrade path is _not_ affected by (at least) bug 1209401. Also the descirption says that the VLAN device got an ipea, which means that the ip was brought up an d vdsm is there (vdsm is not there in bug 1209401).
Hi shaochen, I have tried to reproduce your report: #1 - Installed rhev-hypervisor6-6.5-20150115.0 with two nics (eth0 and eth1) #2 - Network tab in TUI -> Setup Static IP Address 192.168.1.34 -> Vlan ID: 100 #3 - Upgraded to rhev-hypervisor6-6.6-20150402.0 #4 - Network tab in TUI -> Try to configure eth1 TUI display: "Confirm Network Settings" "Network Configuration detected an already configured NIC. The configuration for that NIC is going to be removed if changes are made. Proceed?" I have selected "Yes", later in TUI it shows eth0 as unconfigured as TUI shared previously. Could you please confirm if this is your report? Thanks!
Hi, I have reproduced the report: #1 - Installed rhev-hypervisor6-6.5-20150115.0 with two nics (eth0 and eth1) #2 - Network tab in TUI -> Setup eth1 as static IP Address 192.168.1.34 -> Vlan ID: 100 #3 - Boot rhev-hypervisor6-6.6-20150402.0 for upgrade adding BOOTIF=eth0 in the grub argument, execute the upgrade normally. #4 - After the upgrade, go to network tab in TUI and eth0 and eth1 will be as "unconfigured". However, the vlan settings still persist (eth0.100), only TUI display is affected.
I recall something along the lines that the /etc/default/ovirt file was incorrect after the upgrade. Douglas/Chen, when you reproduce, can you please attach /etc/default/ovirt, I see that it is missing in the sosreport and logs in comment 1.
(In reply to Fabian Deutsch from comment #12) > I recall something along the lines that the /etc/default/ovirt file was > incorrect after the upgrade. > > Douglas/Chen, when you reproduce, can you please attach /etc/default/ovirt, > I see that it is missing in the sosreport and logs in comment 1. Hi Fabian, I will update the output of file soon but I recall from my last try (last week) that if BOOTIF flag is set to eth0 in the GRUB the /etc/default/ovirt will be update the flag to BOOTIF=eth0 and will show all nics to unconfigured, included the configured nic eth1. However, if I put back BOOTIF=eth1 in /etc/default/ovirt and reboot (or restart the TUI) it shows again eth1 as configured.
Created attachment 1024454 [details] etc-default-ovirt.png /etc/default/ovirt
Still can reproduce this bug on latest 7.2 for RHEV3.5 build. Test version: rhev-hypervisor-7-7.2-20150913.0 ovirt-node-3.2.3-20.el7.noarch Hi dougsland, Do we need back-port this bug to RHEV-H 7.2 for RHEV 3.5 build after fix this issue? Thanks!
I can reproduce this issue with below scenario. 1. TUI upgrade from 7.0 GA(rhev-hypervisor7-7.0-20150127) to 7.1 -20150917.0. 2. TUI upgrade from rhev-hypervisor-7-7.2-20150913.0 to itself.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
This has been open for a while, and we did not see bugs coming in around this. Thus I am closing this bug for now, please re-open if necessary.