Troubleshooting Red Hat® OpenShift® Container Platform

Use the following workarounds to troubleshoot problems that you might encounter with Red Hat® OpenShift® Container Platform.

oc mirror command takes a long time to run

This issue occurs when you try to mirror images from the intermediate registry server to the final registry server.

Symptom

Based on the number and size of images to be mirrored, the oc mirror command takes a long time to run.

Workaround

If you are issuing the command on a remote machine, it is recommended that you run the command in the background with a nohup. That way, even if the network connection to your remote machine is lost or you close the terminal, the mirroring continues. For example, the following command starts the mirroring process in the background and writes the log to my-mirror-progress.txt: 
nohup oc mirror 
--config /root/.ibm-pak/data/mirror/ibm-process-mining/$CASE_VERSION/image-set-config.yaml 
docker://$TARGET_REGISTRY 
--dest-skip-tls 
--continue-on-error=true > my-mirror-progress.txt 2>&1 &

Catalog source and installation error

This issue occurs when you try to install catalog source and IBM Process Mining.

Symptom

Creating the catalog source and installing IBM Process Mining does not work.

Workaround

The following command is an alternative to install the catalog source and IBM Process Mining:
oc ibm-pak launch \
$CASE_NAME \
  --version $CASE_VERSION \
  --action install-catalog \
  --inventory $CASE_INVENTORY_SETUP \
  --namespace $NAMESPACE \
  --args "--registry $TARGET_REGISTRY --recursive \
  --inputDir ~/.ibm-pak/data/cases/$CASE_NAME/$CASE_VERSION"