Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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-policiesAssignee: Tomas Mraz <tmraz>
Status: CLOSED INSUFFICIENT_DATA QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0CC: 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 
I have enabled fips-mode-setup --enable in the AWS RHEL8 EC2, after reboot the system doesn't come up. I have tried 2 to 3 times with different RHEL8 EC2 and different location, it is same. EC2 doesn't startup. Since AWS doesn't have console option I couldn't see the boot menu and error. Does any one come across and fixed this?
Comment 1 Tomas Mraz 2020-02-27 09:59:35 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
Comment 2 Frank Liang 2020-03-16 09:10:34 UTC 
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).