Bug 1943143

Summary:	[vsphere] hostname are changed when upgrading from 4.6 to 4.7.x causing upgrades to fail
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Machine Config Operator	Assignee:	rvanderp
Machine Config Operator sub component:	platform-vsphere	QA Contact:	Michael Nguyen <mnguyen>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	aos-bugs, bjarolim, bleanhar, jima, mkrejci, openshift-bugs-escalate, rvanderp, vuberti, wking
Version:	4.7	Keywords:	Upgrades
Target Milestone:	---
Target Release:	4.7.z
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
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:	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-12 23:22:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1942207
Bug Blocks:

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