Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1212714

Summary: [6.6_3.5.1]The assigned logical network setup via rhevm portal is missed in Backup rhevh after rhevh upgrade.
Product: Red Hat Enterprise Virtualization Manager Reporter: haiyang,dong <hadong>
Component: vdsmAssignee: Lior Vernia <lvernia>
Status: CLOSED DUPLICATE QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.1CC: bazulay, cshao, ecohen, gklein, gouyang, hadong, huiwa, leiwang, lpeer, lsurette, ycui, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-26 13:21:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
attached var logs for rhev-hypervisor6-6.6-20150128.0
none
attached sosreport logs for rhev-hypervisor6-6.6-20150128.0
none
attached engine logs from rhevm portal none

Description haiyang,dong 2015-04-17 07:50:38 UTC
Created attachment 1015459 [details]
attached var logs for rhev-hypervisor6-6.6-20150128.0

Description of problem:
The network was missed which was configured by "the Setup Host Networks window" of rhevm webui portal .

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.6-20150128.0.iso
rhev-hypervisor6-6.6-20150402.0.el6ev

How reproducible:
100%

Steps to Reproduce:
1) Clean install rhev-hypervisor6-6.6-20150128.0.iso and configure network
2) add rhevh into RHEV-M (14.3)  
3) Editing Host Network Interfaces in rhevm webui and Assigning Logical Networks to rhevh
4) Put rhevh in maintenance 
5) Upgraded rhevh to rhev-hypervisor6-6.6-20150402.0.iso via RHEV-M
6) Server installed successfully and rebooted.
7) login the new version "6.6-20150402" and check the notwork status
8) Reboot the new version "6.6-20150402" and enter into backup "6.6-20150128" version and check the notwork status

Actual results:
After 7, Could found the network configuration files and it's status is up.
After 8, check that the network was missed that was configured via step3. host's status is "NonOperational":        
2015-Apr-16, 12:45        
Status of host localhost1 was set to NonOperational.        
2015-Apr-16, 12:45
Host localhost1 does not comply with the cluster hadong2_clu networks, the following networks are missing on host: 'redhat'

Expected results:
Could found all network configuration files and host's status is up for step7 and step8

Additional info:

Comment 1 haiyang,dong 2015-04-17 07:53:22 UTC
Created attachment 1015460 [details]
attached sosreport logs for rhev-hypervisor6-6.6-20150128.0

Comment 2 haiyang,dong 2015-04-17 08:05:19 UTC
Created attachment 1015461 [details]
attached engine logs from rhevm portal

Comment 3 Fabian Deutsch 2015-04-23 11:06:42 UTC
(In reply to haiyang,dong from comment #0)
…
> Version-Release number of selected component (if applicable):
> rhev-hypervisor6-6.6-20150128.0.iso
^^ RHEV 3.5.0

> rhev-hypervisor6-6.6-20150402.0.el6ev
^^ RHEV 3.5.1 (pre-release)


> Steps to Reproduce:
> 1) Clean install rhev-hypervisor6-6.6-20150128.0.iso and configure network
> 2) add rhevh into RHEV-M (14.3)  
> 3) Editing Host Network Interfaces in rhevm webui and Assigning Logical
> Networks to rhevh
> 4) Put rhevh in maintenance 
> 5) Upgraded rhevh to rhev-hypervisor6-6.6-20150402.0.iso via RHEV-M
> 6) Server installed successfully and rebooted.
> 7) login the new version "6.6-20150402" and check the notwork status
> 8) Reboot the new version "6.6-20150402" and enter into backup
> "6.6-20150128" version and check the notwork status
> 
> Actual results:
> After 7, Could found the network configuration files and it's status is up.
> After 8, check that the network was missed that was configured via step3.

It is known that 3.5.0 is problematic with networks.

I tend to close this WONTFIX, at least it's a vdsm issue.

Comment 4 Lior Vernia 2015-04-26 13:21:49 UTC

*** This bug has been marked as a duplicate of bug 1208376 ***