BMYPC6008

Inaccessible registry.

Severity

Error

Problem description

It indicates that the specified image registry is not accessible from one or more cluster nodes. It blocks the upgrade because image pulls might fail. It also causes other issues outside of upgrades as newly scheduled or rescheduled pods are unable to access their images.

For the registries that have non-empty auth specified in the pull-secret in the openshift-config namespace, check for the connectivity to make sure that the images are pulled successfully for IBM Storage Fusion components and the OpenShift® Container Platform. If you fail to address the registry access might result in pods can get into an ImagePullbackOff error.

Recommended actions

Do the following steps to resolve the issue:
  1. Check the network connectivity between the OpenShift cluster and the image registry.
  2. A firewall can prevent the access to the registry.
  3. After the connectivity issue is resolved, the upgrade precheck detects the fix and resumes upgrade automatically.

If you want to override the prechecks that are blocking the upgrade, do the following steps:

It converts the Error prechecks to Warning prechecks and triggers the upgrade.
Note: Before using the precheck-acks configmap to override the pre-checks, ensure that the unhealthy resource does not affect the upgrade.
  1. Run the following command and export IBM Storage Fusion namespace as an environmental variable.
    export FUSION_NS="namespace-where-fusion-is-installed"
  2. Run the following command to create a precheck-acks configmap in the namespace where the IBM Storage Fusion is installed.
    oc create configmap precheck-acks -n $FUSION_NS
  3. In the precheck-acks config map, add the key RegistryAccessibility and set the value to true.
    oc patch configmap precheck-acks -n $FUSION_NS --type merge -p '{"data": {"RegistryAccessibility": "true"}}'