Troubleshooting
Problem
Attempt to activate the Manage application in MAS Suite admin fails and the following error is received in the DeploymentCR after some minutes.
Message: unknown playbook failure Failed to pull image: Image with buildTag: latest was not found. Check if image was built
successfully and the corresponding buildTag exists. It can be 'latest' or an existing tag from admin or bundle imageStreams.
Symptom
During Manage activation in MAS, it is failing to pull the image from the registry. "Failed to pull image ..." error message is displayed in the DeploymentCR.
Cause
This failure occurs because the internal image repository is not configured. The actual error in the build log is:
Error starting build: an image stream cannot be used as build output because the integrated container image registry is not configured
Diagnosing The Problem
The error displayed in the MAS admin console is generic. You would need to review the MustGather logs to find the actual error
In the mas-<instance_id>-manage > Config > Status.txt file, you would see the following error indicating that build fails to pull image because the administrator did not configure the integrated container image registry:
* bc/admin-build-config is pushing to istag/mas-sandbox-masdev-admin:20231023T152043-8.6, but the administrator has not
configured the integrated container image registry.
* bc/all-build-config is pushing to istag/mas-sandbox-masdev-all:20231023T152043-8.6, but the administrator has not
configured the integrated container image registry.
* build/admin-build-config-439 has failed.
...and in the mas-<instance_id>-manage > Config > builds > 01-overview.txt file, you would see error starting build failure "...because the integrated container image registry is not configured".
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning InvalidOutput 13m build-controller Error starting build: an image stream cannot be
used as build output because the integrated container image registry is not configured
Normal BuildFailed 13m build-controller Build mas-mas-sandbox-manage/admin-build-config-439 failed
This is because there is no image-registry pod, therefore cannot get image stream during the activation. You can check by running this command:
oc get pod -n openshift-image-registry
There should be an image-registry-xxx pod running.
# oc get pods -n openshift-image-registry
NAME READY STATUS RESTARTS AGE
cluster-image-registry-operator-6f776c5f85-qkpsh 1/1 Running 0 23d
image-pruner-28303200-zkjch 0/1 Completed 0 2d17h
image-pruner-28304640-zzvtb 0/1 Completed 0 41h
image-pruner-28306080-9sqn4 0/1 Completed 0 17h
image-registry-647dc77755-q86x1 1/1 Running 0 23d
node-ca-46cx8 1/1 Running 15 23d
node-ca-6fjmw 1/1 Running 14 23d
node-ca-8kqcg 1/1 Running 14 23d
node-ca-9r7rj 1/1 Running 18 23d
node-ca-dm62x 1/1 Running 14 23d
node-ca-k9pkq 1/1 Running 14 23d
node-ca-qnns9 1/1 Running 14 23d
node-ca-rv7zr 1/1 Running 14 23d
In the operator configs.imageregistry.operator.openshift.io CRD yaml, the spec.managementState and spec.storage.managementState are set to "Removed"
oc get configs.imageregistry.operator.openshift.io/cluster -o yaml -n openshift-image-registry
If the spec.managementState is set to Removed, the operator removes the registry instance and destroys any storage that the operator provisioned.
If the spec.storatge.managementState is set to Removed, then the storage is deleted.
Resolving The Problem
1. Verify that the image registry is available.
oc get co image-registry
2. Edit the configs.imageregistry.operator.openshift.io yaml and update the value for spec.managementState and spec.storage.mamnegementState.
oc edit configs.imageregistry.operator.openshift.io
Search for "managementState" under spec (spec.mamegementState) and change the value to Managed.
Also, change the value for spec.storage.managementState from Managed.
spec:
.
.
.
managementState: Managed
proxy: {}
unsupportedConfigOverrides: null
.
.
.
storage:
managementState: Managed
pvc:
claim: image-registry-storage
3. Save the file.
4. Enable the image registry default route:
oc patch configs.imageregistry.operator.openshift.io/cluster --patch '{"spec":{"defaultRoute":true}}' --type=merge
Image pull is successful and Manage activation can proceed.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeaAAE","label":"Maximo Application Suite-\u003EMAS Applications-\u003EManage"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
05 December 2023
UID
ibm17077743