BMYPC6013

The DNS resolution for image registry failed.

Severity

Error

Problem description

It indicates that the hostname resolution specified for the image registry failed for one or more cluster nodes. It blocks the upgrade because of image pull failure. It can also cause other issues outside of the upgrade because the newly scheduled or rescheduled pods cannot access the images.

The registries can have a non-empty auth specified in the pull-secret of the openshift-config namespace. Check the connectivity for successful image pulls of IBM Fusion components and the OpenShift® Container Platform. Failure to address the registry access can result in an ImagePullbackOff error of the pod.

Recommended actions

Do the following steps to resolve the issue:
  1. Check the DNS settings for the image registry.
  2. A firewall can prevent the access to the registry
  3. After the DNS resolution 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 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 Fusion is installed.
    oc create configmap precheck-acks -n $FUSION_NS
  3. In the precheck-acks configmap, add the key DNSResolution and set the value to true.
    oc patch configmap precheck-acks -n $FUSION_NS --type merge -p '{"data": {"DNSResolution": "true"}}'