Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 859873

Summary: The IPv4 Settings changed from 'DHCP' to 'Disabled' and Protocol display none, when update rhevh on rhevm
Product: Red Hat Enterprise Linux 6 Reporter: Meng Liang <mliang>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: acathrow, bsarathy, chchen, cshao, gouyang, hadong, jbiddle, jboggs, leiwang, mburns, ovirt-maint, thildred, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.5.0-5.el6 Doc Type: Bug Fix
Doc Text:
Previously, a display issue caused the DHCP and Protocol settings to appear disabled after a hypervisor upgrade using the Red Hat Enterprise Virtualization Manager. This did not affect actual network connectivity. The display issue has now been corrected, so that DHCP and Protocol settings are retained in the display after upgrading.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 16:40:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ifcfg-* files before update
none
ifcfg-* files after update none

Description Meng Liang 2012-09-24 09:06:03 UTC
Description of problem:The IPv4 Settings changed from 'DHCP' to 'Disabled' and Protocol display none, when update rhevh on rhevm


Version-Release number of selected component (if applicable):
update rhev-hypervisor6-6.3-20120605.0.el6_3 to rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on local machine
update rhev-hypervisor6-6.3-20120913.0.el6_3 to rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on local machine
update rhev-hypervisor6-6.3-20120605.0.el6_3 to rhev-hypervisor6-6.3-20120913.0.el6_3 on FC machine


How reproducible:


Steps to Reproduce:
1. rhev-hypervisor6-6.3-20120605.0.el6_3
2. Configure the network by DHCP successfully. At this moment
   Protocol:dhcp
   IPv4 settings is:
   [ ]Disabled [*] DHCP [ ]Static
3. Register RHEVH to RHEVM
4. Update rhevh to rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on rhevm
5. On updated rhevh, go to network detail page, check the value of protocol and IPv4 Settings displayed on the screen.
  
Actual results:
Protocol:none
IPv4 Settings
[*]Disabled [ ] DHCP [ ]Static

Expected results:
IP settings should not be changed during update process.

Additional info:

Comment 2 Lei Wang 2012-09-26 01:39:53 UTC
Meng, is this just a display issue or will affect the network functionality as well?

Comment 3 Meng Liang 2012-09-26 01:45:18 UTC
(In reply to comment #2)
> Meng, is this just a display issue or will affect the network functionality
> as well?

It's a display issue.

Comment 4 Meng Liang 2012-09-26 01:59:56 UTC
Sorry guys, the Version-Release number of selected component should be:
update rhev-hypervisor6-6.2-20120605.0.el6_2 to rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on local machine
update rhev-hypervisor6-6.3-20120913.0.el6_3 to rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on local machine
update rhev-hypervisor6-6.2-20120605.0.el6_2 to rhev-hypervisor6-6.3-20120913.1.el6_3 on FC machine

Comment 5 Lei Wang 2012-09-26 02:07:07 UTC
(In reply to comment #4)
> Sorry guys, the Version-Release number of selected component should be:
> update rhev-hypervisor6-6.2-20120605.0.el6_2 to
> rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on local machine
> update rhev-hypervisor6-6.3-20120913.0.el6_3 to
> rhev-hypervisor6-6.3-20120920.0.rhev31.el6_3 on local machine
> update rhev-hypervisor6-6.2-20120605.0.el6_2 to
> rhev-hypervisor6-6.3-20120913.1.el6_3 on FC machine

That means:
6.2.z->6.3.z rhev31
6.3.z->6.3.z rhev31
6.2.z->6.3.z

Comment 7 Meng Liang 2012-10-10 02:20:37 UTC
Created attachment 624438 [details]
ifcfg-* files before update

Comment 8 Meng Liang 2012-10-10 02:21:04 UTC
Created attachment 624447 [details]
ifcfg-* files after update

Comment 16 errata-xmlrpc 2013-02-28 16:40:00 UTC
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-2013-0556.html