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 823737 - rhevm gui upgrades should convert ethX devices to biosdevnames during update
Summary: rhevm gui upgrades should convert ethX devices to biosdevnames during update
Keywords:
Status: CLOSED DUPLICATE of bug 822848
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Haim
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-22 03:04 UTC by Joey Boggs
Modified: 2014-01-13 00:52 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-22 22:11:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Dan Kenigsberg 2012-05-22 06:59:30 UTC 
May I get a pointer to convert_to_biosdevname()? ovirt-node's git-grep gives me nothing.

If the suggested patch is sufficient, I think we can make it to 6.3's 0day.
Comment 5 Douglas Schilling Landgraf 2012-05-22 22:05:01 UTC 
Talked with jboggs and mburns the ovirt-node guys will implement the upgrade as a service (ovirt-early), no changes are required in vdsm at this moment.
Comment 6 Douglas Schilling Landgraf 2012-05-22 22:11:02 UTC 

*** This bug has been marked as a duplicate of bug 822848 ***
Comment 7 Dan Kenigsberg 2012-05-24 07:54:17 UTC 
Folks, wouldn't we (and the rest of the world) have the same problem on a `yum upgrade` of a plain RHEL-6.2 to RHEL-6.3?
Comment 8 Mike Burns 2012-05-24 12:08:33 UTC 
(In reply to comment #7)
> Folks, wouldn't we (and the rest of the world) have the same problem on a
> `yum upgrade` of a plain RHEL-6.2 to RHEL-6.3?

Only if you install biosdevnames as well, which shouldn't happen automatically.
Comment 9 Dan Kenigsberg 2012-05-29 22:29:34 UTC 
I think we have another serious upgrade issue due to this. bug 822953 reminded me that Vdsm (foolishly! doh!) generates the host uuid based on the mac address of alphabetically-first host nic. With biosdevnames installed, nic names and order may change, leading to the node changing its uuid after upgrade. Maybe that's even a cause for bug 822925.

As a solution, we could hack the upgrade script to persist the pre-upgrade uuid on disk, and hack vdsm-reg to report the persisted copy.

Or we could ditch biosdevnames.
Comment 10 Dan Kenigsberg 2012-05-29 22:40:31 UTC 
Sorry for being hysterical. Host macs are sorted by their address, not by their nic name (pun unintended). So installing biosdevnames is not expected to change the node id.
Note You need to log in before you can comment on or make changes to this bug.