QRadar Suite Software deployment fails

Symptoms

QRadar Suite Software deployment failed.

Diagnosing the problem

If the QRadar Suite Software deployment failed or stopped progressing, you can check the status of QRadar Suite Software threat management custom resource by typing the following command.
```
oc get cp4sthreatmanagement threatmgmt -n <cp4s_namespace> -o yaml | grep -A 10 ^status:
```
Check the logs of the QRadar Suite Software operator to get further details of why the deployment stopped progressing by typing the following command.
```
oc logs -n <cp4s_namespace> -lname=ibm-cp-security-operator --tail 100
```
Check the QRadar Suite Software foundations operator custom resource to get further details of why the deployment failed or stopped progressing by typing the following command.
```
oc get cp4sfoundations foundations -n <cp4s_namespace> -o yaml | grep -A 10 ^status:
```
Check the logs of the QRadar Suite Software foundations operator to get further details of why the deployment stopped progressing by typing the following command.
```
oc logs -n <cp4s_namespace> -lname=cp4s-foundations-operator --tail 100
```
Check the status of the QRadar Suite Software components by following the steps in Checking the deployment.
Check the overall health of the cluster by following steps in Checking QRadar Suite Software deployment status.

Resolving the problem

If the diagnosis identifies issues, for example ImagePullBackOff or failures in provisioning persistent volume claims, correct the parameters that are set in <working_directory>/ibm-cp-security/inventory/ibmSecurityOperatorSetup/files/values.conf, the cp4sThreatManagement.yaml file, or the Red Hat® OpenShift® web console. Then, rerun the installation or upgrade, by following the appropriate instructions.

When installation or upgrading is complete, rerun the diagnosis checks.

If the remediation steps do not resolve the problem, run the MustGather script. For more information, see Collecting MustGather data.