Question & Answer
Question
We have a private container registry server with self-signed certificate for air gap install of Cloud Pak for Business Automation(CP4BA)21.0.3. We found when trying to pull the container images from private container registry server in OpenShift Container Platform 4.10.x Cluster, we always encounter the following error events:
Generated from kubelet on worker0.<OCP_Cluster>
4 times in the last 58 minutes
Failed to pull image "<private_container_registry_server>:5001/cpopen/ibm-automation-foundation-core-catalog@sha256:f3501e6689043c4f9125cf6b1e830d1f31437e8cd135e27ca78aa2ea7ce700ea": rpc error: code = Unknown desc = pinging container registry "<private_container_registry_server>:5001: Get "https://"<private_container_registry_server>:5001/v2/": x509: certificate relies on legacy Common Name field, use SANs instead.
4 times in the last 58 minutes
Failed to pull image "<private_container_registry_server>:5001/cpopen/ibm-automation-foundation-core-catalog@sha256:f3501e6689043c4f9125cf6b1e830d1f31437e8cd135e27ca78aa2ea7ce700ea": rpc error: code = Unknown desc = pinging container registry "<private_container_registry_server>:5001: Get "https://"<private_container_registry_server>:5001/v2/": x509: certificate relies on legacy Common Name field, use SANs instead.
We previously tried the install the same version of CP4BA in OpenShift Container Platform 4.8.x and 4.9.x and never encounter above issue.
Please help us to fix the issue.
[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001iUZAAY","label":"Operate-\u003EFNCM Install\\Upgrade\\Setup"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
28 September 2022
UID
ibm16824781