Bug 1804032 - vm can not boot up with rhcos-44.81.202002071430-0
Summary: vm can not boot up with rhcos-44.81.202002071430-0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RHCOS
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.4.0
Assignee: Micah Abbott
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-18 04:39 UTC by liujia
Modified: 2020-04-07 03:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-24 04:05:18 UTC
Target Upstream Version:
Embargoed:
jiajliu: needinfo-

Attachments (Terms of Use)

Description liujia 2020-02-18 04:39:38 UTC 
Description of problem:
When trigger upi/vsphere installation with the latest rhcos ami rhcos-44.81.202002071430-0, vm hosts can not boot up. Following error info shows in vm console.

PXE-E53:NO boot filename received
PXE-M0F exiting intel PXE ROM
operating system not found

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

How reproducible:
always

Steps to Reproduce:
1. upload the latest rhcos image from https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202002071430-0/x86_64/rhcos-44.81.202002071430-0-vmware.x86_64.ova
2. Trigger upi/vsphere installation with rhcos-44.81.202002071430-0
3.

Actual results:
vm hosts can not boot up

Expected results:
vm hosts can boot up successfully to continue installation. 

Additional info:
The old rhcos image rhcos-44.81.202001241431.0 works well.
Comment 1 Micah Abbott 2020-02-19 02:59:51 UTC 
This might be a duplicate or related to the missing OVF file reported here - https://bugzilla.redhat.com/show_bug.cgi?id=1804413

Do you get any errors trying to import the OVA via `ovftool`?

cc: @bgilbert
Comment 2 liujia 2020-02-19 03:08:58 UTC 
(In reply to Micah Abbott from comment #1)

> Do you get any errors trying to import the OVA via `ovftool`?
No, I don't use ovftool. But I hit a failure when import it through console [deploy ovf template] when use this url[1] directly. So I downloaded the ova from [1] to a http server, and import it through http:server_ip/rhcos-44.81.202002071430-0-vmware.x86_64.ova through the console successfully.

[1]https://releases-art-rhcos.svc.ci.openshift.org/art/storage/releases/rhcos-4.4/44.81.202002071430-0/x86_64/rhcos-44.81.202002071430-0-vmware.x86_64.ova
Comment 3 Johnny Liu 2020-02-19 09:07:24 UTC 
Consider openshift QE can not apply the latest rhcos image as boot image to run our testing, raise this bug as testblocker.
Comment 4 Michael Nguyen 2020-02-19 15:24:20 UTC 
I received this message trying to import rhcos-44.81.202002071430-0-vmware.x86_64.ova into vsphere:  "Transfer failed: The OVF descriptor is not available"
Comment 5 Benjamin Gilbert 2020-02-22 05:03:28 UTC 
Could you try again with RHCOS 44.81.202002211631-0 or later?  It has several OVA-related fixes.
Comment 6 liujia 2020-02-24 03:08:57 UTC 
rhcos-44.81.202002211631-0 work well.
Comment 7 Benjamin Gilbert 2020-02-24 04:05:18 UTC 
Great!  Closing.
Note You need to log in before you can comment on or make changes to this bug.