Bug 1700056
Summary: | Cannot boot an p3.2xlarge instance with RHCOS (g3.4xlarge is working) on AWS | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zvonko Kosic <zkosic> |
Component: | RHCOS | Assignee: | Steve Milner <smilner> |
Status: | CLOSED ERRATA | QA Contact: | Micah Abbott <miabbott> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.0 | CC: | bbreard, dustymabe, imcleod, jligon, miabbott, nstielau, walters |
Target Milestone: | --- | ||
Target Release: | 4.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-04 10:47:37 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: |
Description
Zvonko Kosic
2019-04-15 17:12:07 UTC
What additional info do you need? Primarily if the current version of RHCOS has this same result and/or does the same version of general purpose ootpa have the same result. The current version of RHCOS has the same result. Do we have a general purpose ootpa AMI on AWS available to test it? I am only seeing the OpenShift 4 Beta ones. Can we have a build of RHCOS AMI (asap) to test with this new changes? AFAIU the changes will only apply for ec2 aka AWS RHEL8 AMIs right? I just checked the RHEL7.6 AMI from Amazon and the nouveau driver is not loaded and this AMI works on a p3 instance. I have created an own RHCOS AMI image with the changes above to disable the nouveau driver and I can successfully boot my updated RHCOS AMI. I have created my own RHCOS AMI image with the changes stated above and I can boot the AMI successfully. Awesome, thanks for doing that Zvonko!! I spoke with Zvonko mid last month and he noted the changes worked for his use case. Deferring to QE to decide if any extra verification is needed. Successfully booted 410.8.20190506.0 (ami-014fa719b11b03142/us-east-1) on p4.2xlarge 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, 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-2019:0758 |