Bug 1943143 - [vsphere] hostname are changed when upgrading from 4.6 to 4.7.x causing upgrades to fail
Summary: [vsphere] hostname are changed when upgrading from 4.6 to 4.7.x causing upgra...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.7
Hardware: x86_64
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.7.z
Assignee: rvanderp
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On: 1942207
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-25 13:12 UTC by OpenShift BugZilla Robot
Modified: 2024-06-14 01:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Hostname set by the vsphere-hostname service is only applied on installation of the node. Consequence: If the hostname is not statically set prior to upgrading, the hostname may be lost. Fix: Remove condition which allowed the vsphere-hostname service to only run when a node is installed. Result:
Clone Of:
Environment:
Last Closed: 2021-04-12 23:22:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2490 0 None open [release-4.7] Fixes: Bug 1943143: [vsphere] hostnames are changed when upgrading from 4.6 to 4.7.x causing upgrades to f... 2021-03-30 21:46:22 UTC
Red Hat Product Errata RHBA-2021:1075 0 None None None 2021-04-12 23:23:10 UTC

Comment 1 W. Trevor King 2021-03-30 17:49:18 UTC 
Setting Urgent and blocker+, because [1] will block all *->4.7.4 releases on this bug series, so there's not much point in cutting additional 4.7.z until it is fixed.


[1]: https://github.com/openshift/cincinnati-graph-data/pull/731
Comment 2 W. Trevor King 2021-03-31 02:30:33 UTC 
Actually, setting blocker-, because while this is a regression vs. 4.7.3, it is not a regression since 4.7.4, and we shipped that.  We'll ship 4.7.5 without this fix to accommodate folks trying to install on vSphere, but we'll still block all edges into 4.7.5 until we have this fixed.  That makes this basically the most urgent we can possibly be without rising to blocker+.
Comment 8 errata-xmlrpc 2021-04-12 23:22:56 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 (OpenShift Container Platform 4.7.6 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1075
Note You need to log in before you can comment on or make changes to this bug.