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.

Description of problem:
Pull image failed with x509 error when enable fips on rhcos node server

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-18-235010

Red Hat Enterprise Linux CoreOS 420.8.20190718.1 (Ootpa)

How reproducible:
always

Steps to Reproduce:
1.enable fips mode on rhcos node server

2.pull image from quay, such as:
# crictl pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:15481cb3cc1993b5e4d02ee5a7848690bf48373606590dc543eb671589b544b5


Actual results:
# crictl pull quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:15481cb3cc1993b5e4d02ee5a7848690bf48373606590dc543eb671589b544b5
FATA[0000] pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://quay.io/v2/: x509: certificate specifies an incompatible key usage 

Expected results:
pull successful with no error

Additional info:
image pull successful when disable fips on rhcos node

This looks like another `cri-o` BZ similar to BZ#1731393; re-assigning to Node team

Let us know if there is something RHCOS can do for this BZ.

This is something golang compiler needs to address

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

Re-open it as track the OCP feature testing, will verify it when https://bugzilla.redhat.com/show_bug.cgi?id=1731550 on qa.

Also this is test blocker for our fips feature testing.

Sending to Quay as they will have to change the cert on their side to be FIPS compliant.

FIPS support is smoke test for 4.2 (trying to find the issues) and something we might support in 4.3.  We do want to address this for 4.3.

This is a test blocker for 4.2, even to the smoke test, it should be fixed ASAP to unblock the 4.2 testing.