Bug 1843081

Summary:	RHCOS doesn't boot on RHV 4.4beta
Product:	OpenShift Container Platform	Reporter:	Gajanan <gchakkar>
Component:	RHCOS	Assignee:	Luca BRUNO <lucab>
Status:	CLOSED DUPLICATE	QA Contact:	Michael Nguyen <mnguyen>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.4	CC:	bbreard, dornelas, dougsland, imcleod, jligon, nstielau, rgolan
Target Milestone:	---
Target Release:	4.6.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-05 12:46:07 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:
Bug Depends On:
Bug Blocks:	1186913

Description Gajanan 2020-06-02 17:31:03 UTC

Description of problem:

Customer is facing issues while installing RHCOS on RHV 4.4 beta

Version-Release number of selected component (if applicable):

OCP 4.4 on RHV 4.4 Beta

Comment 3 Micah Abbott 2020-06-02 21:36:39 UTC

As stated in this article - https://access.redhat.com/articles/4763741

...RHCOS is not currently supported on RHV 4.4 Beta

The screen recording attached to the customer case of the boot process appeared to be of poor quality when viewed on my workstation, so it was hard to determine exactly what failed.  It looked like the VM was successfully assigned an IP address via DHCP, but it looks like it is unable to connect to the OpenStack metadata service at 169.254.169.254 with "no route to host" (trying to reach http://169.254.169.254/openstack/latest/user_data)

To properly triage the issue, we would need a more complete console log from the RHCOS VM.  Additionally, information about the networking configuration being used and what the initial Ignition config file looks like would be useful.

Setting to low priority and targeting 4.6

Comment 5 Luca BRUNO 2020-06-04 13:17:10 UTC

After several attempts at fetching the first-boot configuration, the machine in the recording displays the following:

> Ignition: neither config drive nor metadata service were available in time. Continuing without a config...

Which means that it didn't manage to reach neither a config-drive nor the link-local metadata endpoint to fetch its configuration.

It sounds like the underlying (unsupported) environment may be mis-configured.

It would be helpful to have a RHV knowledgeable person to verify/document how such environment should be configured in order for OCP nodes to get their configuration.

Comment 6 Sandro Bonazzola 2020-06-05 08:54:14 UTC

Roy, can you please review this report?

Comment 7 Roy Golan 2020-06-05 09:20:02 UTC

Please check what is the guest OS type for your created VMs. You are most probably hitting this Bug 1821638 and this will land in 4.4.7

Comment 8 Luca BRUNO 2020-06-05 12:46:07 UTC

Tentatively closing this one, as the OS side seems fine. Let's keep tracking the RHV side in a single place in https://bugzilla.redhat.com/show_bug.cgi?id=1821638.

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