Bug 1807716
| Summary: | Enable fips-mode-setup --enable in AWS Rhel8 EC2 stuck | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | dpk <deepak.rajaling> |
| Component: | crypto-policies | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | leiwang, linl, nmavrogi, ribarry, vkuznets, xiliang, ymao |
| Target Milestone: | rc | ||
| Target Release: | 8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-27 09:59:35 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
dpk
2020-02-27 03:22:00 UTC
Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
Please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
https://www.redhat.com/support/process/production/#howto
AWS provides readonly console and you can get console output via command line or web console while booting failed: $ aws ec2 get-console-output --instance-id $your_instance_id tips: the console output is not update in time, please wait longer time if it is empty. Which instance type did you try? Did you try RHEL8.1 or RHEL8.2 beta AMIs? It is may not stuck and just takes longer time than before. Could you try to wait longer time(like 6 mins). |