Troubleshooting
Problem
IBM Maximo Application Suite 8.3 - Maximo Visual Inspection deployment error fails with error message:
This application is being deployed (Last updated: April 5, 2021 3:43:31 PM)
Symptom
IBM Maximo Application Suite 8.3 - Maximo Visual Inspection application deployment stays in "This application is being deployed" state and never changes
Cause
The cause of the issue is the type of the used storage class.
According to IBM Cloud Docs, https://cloud.ibm.com/docs/containers?topic=containers-block_storage#add_block:
Block storage comes with a ReadWriteOnce access mode.You can mount it to only one pod on one worker node in the cluster at a time.
Please use *ibmc-file-gold* for the PVC configuration. At this point, you should be able to delete the current deployment of the application and, redeploy, this time specifying *ibmc-file-gold* as the storage class.
Diagnosing The Problem
Inspect the status of the pods in Openshift console:
[root@mas ~]# oc get pods
NAME READY STATUS RESTARTS AGE
masr-task-pvc-mvi-data-pvc 0/1 Pending 0 3d
mas-trackdeploy-deploy-pending-xxx 0/2 Completed 0 3d
visualinspection-operator-xxxx 1/1 Running 0 3d
The masr-task-pvc-mvi-data-pvc pod is in Pending status because of storage type.
Resolving The Problem
Under a user that has admin privileges in OpenShift cluster, apply the below procedure:
1) Update the storage class to the right one
Via UI (OpenShift console):
Navigate to: Administration -> Custom Resource Definitions -> VisualInspectionApp -> Instances -> (choose instance, i.e., "masroks")
Select "YAML" to edit the config, look for:
Navigate to: Administration -> Custom Resource Definitions -> VisualInspectionApp -> Instances -> (choose instance, i.e., "masroks")
Select "YAML" to edit the config, look for:
spec:
...
storage:
name: vision-data-pvc
size: 40Gi
storageClassName: ibmc-block-gold
Change the storageClassName to "ibmc-file-gold" and click "Save"
Via CLI
Run:
Run:
oc get visualispection masroks -o yaml > mvi-cfg.yaml
Edit "mvi-cfg.yaml" and update storageClassName
Run:
oc apply -f mvi-cfg.yaml
2) Delete the masr-task-pvc-mvi-data-pvc pod in order for the changes to be picked up.
Document Location
Worldwide
[{"Type":"SW","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":"a8m3p000000hAeUAAU","label":"Maximo Application Suite->Visual Inspection"}],"ARM Case Number":"TS005387212","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.3.0"}]
Was this topic helpful?
Document Information
Modified date:
07 June 2021
UID
ibm16455181