View source for IBM Maximo: Troubleshooting Maximo Manage Workspace activation


Check manageworkspace

 oc describe manageworkspace -n mas-dev01-manage

If From the oc describe output, the critical error is in the Status.Conditions section:

 <nowiki>Name:         dev01-demo01
Namespace:    mas-dev01-manage
Labels:       mas.ibm.com/applicationId=manage
              mas.ibm.com/instanceId=dev01
...</nowiki>
 Type: BuildReady
 Status: '''False'''
 Reason: '''Failed'''
 Message: Build Failed.
 
 Type: DeploymentCR
 Status: True
 Reason: '''Failed'''
 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.


Check Build Pods:

 oc get pods -n mas-dev01-manage | grep build
 oc logs -n mas-dev01-manage <build-pod-name>

Check ImageStreams:

 oc get imagestream -n mas-dev01-manage
 oc describe imagestream -n mas-dev01-manage

Check Build Configs:

 oc get buildconfig -n mas-dev01-manage
 oc describe buildconfig -n mas-dev01-manage

Review Build Logs for the actual failure reason (disk space, network issues, resource limits, etc.)


== Build Cancellation Issue==

The problem is from the BuildConfig output. Here's what's happening:

 Critical Finding: All Builds Are Being Cancelled
 Build			Status		Duration	Creation Time
 admin-build-config-46 	cancelled 	0s 		2026-04-11 09:27:43 +0000 UTC
 admin-build-config-45 	cancelled 	0s 		2026-04-11 09:02:12 +0000 UTC

Why This Causes the Error:
No Images Built: The ImageStreams exist but have no tags (empty):

 dev01-demo01-admin   Tags: <none>
 dev01-demo01-all     Tags: <none>


=== Immediate Actions to Resolve ===

Check Cluster Resources:

 oc describe nodes | grep -A 5 "Allocated resources"
 oc get resourcequota -n mas-dev01-manage
 oc get limitrange -n mas-dev01-manage

Check for Build Pod Events:

 oc get events -n mas-dev01-manage --sort-by='.lastTimestamp' | grep -i build

Manually Trigger a Build (to see actual error):

 oc start-build admin-build-config -n mas-dev01-manage --follow

Check ManageWorkspace Operator Logs:

 oc logs -n mas-dev01-manage -l app.kubernetes.io/name=ibm-mas-manage --tail=200

Review Build Strategy Settings: The builds require significant resources:

 Ephemeral storage: 100Gi limit, 30Gi request
 Memory: 4Gi for admin, 10Gi for server bundles
 CPU: 2 cores for admin, 6 cores for server bundles


= See Also =

* [[Cloud|Articles about Cloud]]
* [[Technologies|More Articles about Cloud / Web Development / Technologies]]

[[Category:IBM Maximo]]