Running the MustGather Healthcheck
You can run the IBM Cloud Pak for AIOps MustGather tool with a healthcheck option to gather data to check whether your installation was successful or to analyze how IBM Cloud Pak for AIOps is running.
Important: Ensure that your installed version of the tool is v1.17.6 or newer. Some healthcheck data is only gathered with version v1.17.6 and newer.
To gather data for healthcheck related problems, run the following command:
waiops-mustgather.sh -O healthcheck
This option gathers the following data for checking the current health of your IBM Cloud Pak for AIOps deployment and Red Hat OpenShift Container Platform cluster:
The healthcheck gathers the following data:
- Node status, CPU utilization, and memory utilization
- Red Hat OpenShift etcd status
- Cluster service version (CSV) phase for IBM Cloud Pak for AIOps CSVs
- CustomResourceDefinitions (CRDs) phase/status and version for IBM Cloud Pak for AIOps projects
- Persistent volumes and persistent volume claims (PVC) status
- Deployments, statefulsets, pods, daemonsets, and jobs statuses
- Key missing resources
- Basic compliance check results
After the tool finishes gathering data, review the 0-README-FIRST/SUMMARY.log log file.
Node status, CPU utilization, and memory utilization
For the list of all nodes in the cluster with their respective status, CPU utilization, and memory utilization, review the HEALTH REPORT OF NODES section of the log.
This report shows the total CPU and MEMORY available in the cluster, and the CPU and memory request and limit of individual nodes. This report also indicates a warning when the CPU or memory utlization exceeds 95%.
The following log example shows a node health report for a IBM Cloud Pak for AIOps deployment:
===================================================
HEALTH REPORT OF NODES
===================================================
NODENAME CPU_COUNT CPU_USAGE MEM_SIZE MEM_USAGE AGE ROLES STATUS
master0.waiops42b.mysite.ibm.com 8 top=14% req=23% limit=0% 16015816Ki top=66% req=51% limit=5% 39d control-plane,master Ready
master1.waiops42b.mysite.ibm.com 8 top=18% req=27% limit=0% 16015816Ki top=84% req=60% limit=5% 39d control-plane,master Ready
master2.waiops42b.mysite.ibm.com 8 top=29% req=26% limit=0% 16015808Ki top=90% req=61% limit=5% 39d control-plane,master Ready
worker0.waiops42b.mysite.ibm.com 16 top=14% req=68% limit=145% 48270036Ki top=51% req=81% limit=98% 39d worker Ready
worker1.waiops42b.mysite.ibm.com 16 top=6% req=78% limit=196% 48270036Ki top=35% req=68% limit=93% 39d worker Ready
worker10.waiops42b.mysite.ibm.com 16 top=7% req=76% limit=188% 48270036Ki top=26% req=70% limit=114% 39d worker Ready
worker11.waiops42b.mysite.ibm.com 16 top=4% req=78% limit=116% 48270036Ki top=23% req=68% limit=71% 39d worker Ready
worker12.waiops42b.mysite.ibm.com 16 top=13% req=91% limit=309% 48270036Ki top=42% req=81% limit=149% 39d worker Ready
worker13.waiops42b.mysite.ibm.com 16 top=15% req=56% limit=89% 48270036Ki top=59% req=81% limit=78% 39d worker Ready
worker14.waiops42b.mysite.ibm.com 16 top=6% req=70% limit=151% 48270036Ki top=24% req=70% limit=88% 39d worker Ready
worker15.waiops42b.mysite.ibm.com 16 top=6% req=73% limit=229% 48270036Ki top=38% req=74% limit=107% 39d worker Ready
worker16.waiops42b.mysite.ibm.com 16 top=4% req=72% limit=133% 48270036Ki top=29% req=60% limit=80% 39d worker Ready
worker17.waiops42b.mysite.ibm.com 16 top=8% req=74% limit=148% 48270036Ki top=42% req=80% limit=97% 39d worker Ready
worker2.waiops42b.mysite.ibm.com 16 top=10% req=70% limit=189% 48270036Ki top=30% req=68% limit=92% 39d worker Ready
worker3.waiops42b.mysite.ibm.com 16 top=6% req=79% limit=193% 48270036Ki top=37% req=76% limit=91% 39d worker Ready
worker4.waiops42b.mysite.ibm.com 16 top=9% req=73% limit=202% 48270036Ki top=50% req=72% limit=97% 39d worker Ready
worker5.waiops42b.mysite.ibm.com 16 top=4% req=98% limit=154% 48270036Ki top=27% req=89% limit=94% 39d worker Ready
worker6.waiops42b.mysite.ibm.com 16 top=5% req=78% limit=171% 48270036Ki top=29% req=65% limit=79% 39d worker Ready
worker7.waiops42b.mysite.ibm.com 16 top=6% req=75% limit=134% 48270036Ki top=29% req=61% limit=72% 39d worker Ready
worker8.waiops42b.mysite.ibm.com 16 top=6% req=91% limit=223% 48270036Ki top=38% req=61% limit=93% 39d worker Ready
worker9.waiops42b.mysite.ibm.com 16 top=3% req=16% limit=25% 48270036Ki top=15% req=17% limit=15% 39d worker Ready
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL 312 938.91GB
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>> [TOTAL OK] Running = 21
>>> [GRAND TOTAL] Node = 21
>>> [CPU WARNING >=95%]
worker5.waiops42b.mysite.ibm.com: req=98%
[Sun Nov 12 20:53:25 PST 2023] All nodes are up and running!
Red Hat OpenShift etcd status
For the Red Hat OpenShift etcd status, review the HEALTH AND STATUS REPORT OF ETCD section of the log.
The following log example shows a health and status report of ETCD for a IBM Cloud Pak for AIOps deployment:
===================================================
HEALTH AND STATUS REPORT OF ETCD
===================================================
[HEALTH]
https://10.20.3.321:2379 is healthy: successfully committed proposal: took = 7.704087ms
https://10.20.4.136:2379 is healthy: successfully committed proposal: took = 10.624038ms
https://10.20.3.246:2379 is healthy: successfully committed proposal: took = 10.661189ms
[MEMBER]
427c4b2527db01b6, started, master1.waiops42b.mysite.ibm.com, https://10.20.3.246:2380, https://10.20.3.246:2379, false
5c7cacd390f3a1e0, started, master0.waiops42b.mysite.ibm.com, https://10.20.3.321:2380, https://10.20.3.321:2379, false
5fd7600cb4fe0ee5, started, master2.waiops42b.mysite.ibm.com, https://10.20.4.136:2380, https://10.20.4.136:2379, false
[STATUS]
+--------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+
| ENDPOINT | ID | VERSION | DB SIZE | IS LEADER | IS LEARNER | RAFT TERM | RAFT INDEX | RAFT APPLIED INDEX | ERRORS |
+--------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+
| https://10.20.3.321:2379 | 5c7cacd390f3a1e0 | 3.5.9 | 452 MB | false | false | 25 | 123057248 | 123057248 | |
| https://10.20.3.246:2379 | 427c4b2527db01b6 | 3.5.9 | 400 MB | false | false | 25 | 123057248 | 123057248 | |
| https://10.20.4.136:2379 | 5fd7600cb4fe0ee5 | 3.5.9 | 429 MB | true | false | 25 | 123057248 | 123057248 | |
+--------------------------+------------------+---------+---------+-----------+------------+-----------+------------+--------------------+--------+
Cluster service version (CSV) phase for IBM Cloud Pak for AIOps CSVs
For a report that lists the cluster service versions (CSVs) for a IBM Cloud Pak for AIOps project (namespace), including the CSV phase, review the STATUS REPORT OF CLUSTER SERVICE VERSION (namespace = <namespace>) section
of the log, where <namespace> is the project (namespace) where IBM Cloud Pak for AIOps is installed.
This report lists the version and phase for each CSV. Within the report check the PHASE column and value for each CSV. The value should be Succeeded.
The following log example shows a cluster service version status report for a IBM Cloud Pak for AIOps deployment:
===================================================
STATUS REPORT OF CLUSTER SERVICE VERSION (namespace = cp4aiops)
===================================================
NAME DISPLAY VERSION REPLACES PHASE
aimanager-operator.v4.4.0 IBM AIOps AI Manager 4.4.0 Succeeded
aiopsedge-operator.v4.4.0 IBM AIOps Edge 4.4.0 Succeeded
asm-operator.v4.4.0 IBM Netcool Agile Service Manager 4.4.0 Succeeded
cloud-native-postgresql.v1.18.7 EDB Postgres for Kubernetes 1.18.7 cloud-native-postgresql.v1.18.6 Succeeded
ibm-aiops-ir-ai.v4.4.0 IBM Watson AIOps Issue Resolution AI & Analytics 4.4.0 Succeeded
ibm-aiops-ir-core.v4.4.0 IBM Watson AIOps Issue Resolution Core 4.4.0 Succeeded
ibm-aiops-ir-lifecycle.v4.4.0 IBM Cloud Pak for Watson AIOps Lifecycle 4.4.0 Succeeded
ibm-aiops-orchestrator.v4.4.0 IBM Cloud Pak for AIOps 4.4.0 Succeeded
ibm-automation-elastic.v1.3.15 IBM Elastic 1.3.15 Succeeded
ibm-automation-flink.v1.3.15 IBM Automation Foundation Flink 1.3.15 Succeeded
ibm-cert-manager-operator.v4.2.1 IBM Cert Manager 4.2.1 Succeeded
ibm-common-service-operator.v4.3.1 IBM Cloud Pak foundational services 4.3.1 Succeeded
ibm-commonui-operator.v4.3.0 Ibm Common UI 4.3.0 Succeeded
ibm-events-operator.v4.9.0 IBM Events Operator 4.9.0 Succeeded
ibm-iam-operator.v4.3.1 IBM IM Operator 4.3.1 Succeeded
ibm-mongodb-operator.v4.2.1 IBM MongoDB Operator 4.2.1 Succeeded
ibm-redis-cp.v1.1.4 ibm-redis-cp-operator 1.1.4 Succeeded
ibm-secure-tunnel-operator.v4.4.0 IBM Secure Tunnel 4.4.0 Succeeded
ibm-watson-aiops-ui-operator.v4.4.0 IBM AIOps UI 4.4.0 Succeeded
ibm-zen-operator.v5.1.1 IBM Zen Service 5.1.1 Succeeded
operand-deployment-lifecycle-manager.v4.2.2 Operand Deployment Lifecycle Manager 4.2.2
CustomResourceDefinitions (CRDs) phase/status and version
For a report that lists all important CustomResourceDefinitions (CRDs) for a IBM Cloud Pak for AIOps project (namespace), including the CRD phase/status and version, review the STATUS REPORT OF AIOPS PRODUCT COMPONENTS section of
the log.
This report shows the version, phase/status, and any error for each key CRD. Within the report check the VERSION column for each CRD:
- The string value
<none>indicates that no version details are available. This value is not a cause for alarm. - The string value
N/Aindicates that the MustGather tool is unable to detect the CRD. The healthcheck option for the MustGather scans for a predefined list of CRDs, if a CRD is installed, but shows asN/A, further investigation is required as there might be a problem with that component.
The following log example shows a product components status report for a IBM Cloud Pak for AIOps deployment:
===================================================
STATUS REPORT OF WAIOPS PRODUCT COMPONENTS
===================================================
KIND NAME NAMESPACE VERSION PHASE/STATUS
AIManager aimanager cp4waiops 4.2.0 Completed
AIOpsAnalyticsOrchestrator aiops cp4waiops 4.2.0 Ready
AIOpsEdge aiopsedge cp4waiops <none> Healthy
AIOpsUI aiopsui-instance cp4waiops 4.2.0 Ready
ASMFormation aiops-topology cp4waiops 2.17.0 OK
ASMFormation evtmanager-topology cp4waiops-emgr <none> OK
automationbase N/A N/A N/A N/A
automationuiconfig N/A N/A N/A N/A
BaseUI baseui-instance cp4waiops 4.2.0 Ready
cartridge N/A N/A N/A N/A
cartridgerequirements N/A N/A N/A N/A
CEMFormation evtmanager cp4waiops-emgr 2.12.7 OK
eventprocessor N/A N/A N/A N/A
Installation ibm-cp-watson-aiops cp4waiops <none> Running
IssueResolutionCore aiops cp4waiops 4.2.0 Ready
LifecycleService aiops cp4waiops 4.2.0 Ready
NOI evtmanager cp4waiops-emgr 1.6.10 OK
NOIFormation evtmanager cp4waiops-emgr 1.6.10 OK
noihybrid N/A N/A N/A N/A
ZenService iaf-zen-cpdservice cp4waiops 4.8.9 Completed
Persistent volumes and Persistent volume claims (PVC) status
For node disk status (disk utilization details), Persistent volume status, and Persistent volume claims status, review the following sections of the log:
STATUS REPORT OF PERSISTENTVOLUMECLAIMS (namespace = <namespace>)PVC UTILIZATION REPORT (namespace = <namespace>)
The PVC utilization report lists all PVCs and their respective df -h output. The report also shows a warning if the disk utilization is over 95% or if the df -h output is not available for a PVC.
Note: <namespace> is the project (namespace) where IBM Cloud Pak for AIOps is installed.
The following log example shows a PERSISTENTVOLUMECLAIMS report for a IBM Cloud Pak for AIOps deployment:
===================================================
STATUS REPORT OF PERSISTENTVOLUMECLAIMS (namespace = cp4waiops)
===================================================
[Sun Nov 12 20:54:41 PST 2023] [cp4waiops] All PVCs seem to be operating fine!
>>> [TOTAL OK] [cp4waiops] Bound (pvc) = 40
>>> [TOTAL PVC] = 40
The following log example shows a PVC utilization report for a IBM Cloud Pak for AIOps deployment:
===================================================
PVC UTILIZATION REPORT (namespace = cp4waiops)
===================================================
[1] [ PVC = aiops-ir-analytics-spark-shared-state / PV = pvc-70d738c1-45ea-4654-9dba-8259c05e69cf ]
>> [ POD = aiops-ir-analytics-metric-spark-7b7cd75c85-s2sr6 | CONTAINER = metric-spark | VOLUME = shared-state-store | MOUNTPATH = /opt/spark/store ]
Filesystem Size Used Avail Use% Mounted on
172.30.19.136:6789,172.30.165.234:6789,172.30.203.51:6789:/volumes/csi/csi-vol-12ae3465-2321-4f8c-b952-15987bef9f3e/2f4c98f9-e8e0-4094-91d3-af3d198339a9 100G 0 100G 0% /opt/spark/store
>> [ POD = aiops-ir-analytics-spark-worker-0 | CONTAINER = spark-worker | VOLUME = shared-state-store | MOUNTPATH = /opt/spark/store ]
Filesystem Size Used Avail Use% Mounted on
172.30.203.51:6789,172.30.19.136:6789,172.30.165.234:6789:/volumes/csi/csi-vol-12ae3465-2321-4f8c-b952-15987bef9f3e/2f4c98f9-e8e0-4094-91d3-af3d198339a9 100G 0 100G 0% /opt/spark/store
>> [ POD = aiops-ir-analytics-spark-worker-1 | CONTAINER = spark-worker | VOLUME = shared-state-store | MOUNTPATH = /opt/spark/store ]
Filesystem Size Used Avail Use% Mounted on
172.30.19.136:6789,172.30.165.234:6789,172.30.203.51:6789:/volumes/csi/csi-vol-12ae3465-2321-4f8c-b952-15987bef9f3e/2f4c98f9-e8e0-4094-91d3-af3d198339a9 100G 0 100G 0% /opt/spark/store
---------------------------------------------------
[2] [ PVC = back-aiops-topology-cassandra-0 / PV = pvc-74c5f0a3-a845-427c-b333-e4eac70ffcab ]
>> [ POD = aiops-topology-cassandra-0 | CONTAINER = aiops-topology-cassandra | VOLUME = back | MOUNTPATH = /opt/ibm/cassandra/data/backup_tar ]
Filesystem Size Used Avail Use% Mounted on
/dev/rbd2 49G 53M 49G 1% /opt/ibm/cassandra/data/backup_tar
---------------------------------------------------
[3] [ PVC = back-aiops-topology-cassandra-1 / PV = pvc-82d323b0-56d8-4563-bce2-7d3132a883cb ]
>> [ POD = aiops-topology-cassandra-1 | CONTAINER = aiops-topology-cassandra | VOLUME = back | MOUNTPATH = /opt/ibm/cassandra/data/backup_tar ]
Filesystem Size Used Avail Use% Mounted on
/dev/rbd1 49G 53M 49G 1% /opt/ibm/cassandra/data/backup_tar
...
...
...
>> [ POD = zen-metastoredb-1 | CONTAINER = zen-metastoredb | VOLUME = user-home-mount | MOUNTPATH = /user-home ]
Filesystem Size Used Avail Use% Mounted on
172.30.19.136:6789,172.30.165.234:6789,172.30.203.51:6789:/volumes/csi/csi-vol-f81f5a47-351b-4c19-800f-338905326861/9881d7c5-6e2e-46f5-a7cb-93bf70afe200 10G 160M 9.9G 2% /user-home
>> [ POD = zen-metastoredb-2 | CONTAINER = zen-metastoredb | VOLUME = user-home-mount | MOUNTPATH = /user-home ]
Filesystem Size Used Avail Use% Mounted on
172.30.19.136:6789,172.30.165.234:6789,172.30.203.51:6789:/volumes/csi/csi-vol-f81f5a47-351b-4c19-800f-338905326861/9881d7c5-6e2e-46f5-a7cb-93bf70afe200 10G 160M 9.9G 2% /user-home
>> Pod [zen-pre-requisite-job-696hj] in namespace [cp4waiops] for PVC [user-home-pvc] is not in 'Running' state [STATUS = Bound]
>> [ POD = zen-watcher-659bcf6fc9-nzv9l | CONTAINER = zen-watcher-container | VOLUME = user-home-mount | MOUNTPATH = /user-home ]
time="2023-11-13T04:54:41Z" level=error msg="exec failed: unable to start container process: exec: \"timeout\": executable file not found in $PATH"
command terminated with exit code 255
---------------------------------------------------
Total PVC: 40
Total PVC with 'df' output: 40
Total PVC without 'df' output: 0
Deployments, statefulsets, pods, daemonsets, and jobs statuses
For deployment, statefulset, pod, daemonsets, and job statuses, review the HEALTH REPORT OF NAMESPACE = <namespace> section of the log, where <namespace> is the project (namespace) where IBM Cloud Pak for
AIOps is installed.
This resource analysis report includes a simple analysis of the total resources (deployments, statefulsets, daemonsetspods, pods, and jobs) that are running properly and not running properly. The report identifies any of these resources that are problematic. For problematic pods, the report shows the events for the pods.
The following log example shows a project (namespace) health report of namespace for a IBM Cloud Pak for AIOps deployment:
===================================================
HEALTH REPORT OF NAMESPACE = cp4waiops
===================================================
[Sun Nov 12 20:53:38 PST 2023] [analyzeOcAll] Analyzing 'oc get all -o wide -n cp4waiops' => /tmp/mg/waiops-modules-12112023-205309/PROD_NAMESPACES/cp4waiops/oc_all.out
[Sun Nov 12 20:53:38 PST 2023] [analyzeOcAll] Analyzing DEPLOYMENTS [cp4waiops]
>>> [TOTAL OK] [cp4waiops] Deployment = 84
>>> [TOTAL DEPLOYMENT] = 84
[Sun Nov 12 20:53:41 PST 2023] [analyzeOcAll] Analyzing STATEFULESETS [cp4waiops]
>>> [TOTAL OK] [cp4waiops] Statefulset = 14
>>> [TOTAL STATEFULSET] = 14
[Sun Nov 12 20:53:41 PST 2023] [analyzeOcAll] Analyzing DAEMONSET [cp4waiops]
>>> [cp4waiops] There is no 'daemonset' found!
>>> [TOTAL DAEMONSET] = 0
[Sun Nov 12 20:53:41 PST 2023] [analyzeOcAll] Analyzing PODS [cp4waiops]
>>> [TOTAL OK] [cp4waiops] Running = 166 / Completed = 20
>>> [TOTAL POD] = 186
[Sun Nov 12 20:53:46 PST 2023] [analyzeOcAll] Analyzing JOBS [cp4waiops]
COUNT JOB READY DURATION STATUS
1 aimanager-aio-curator-job-28281060 0/1 34d NOK
>>> [TOTAL OK] [cp4waiops] Job = 40
>>> [TOTAL NOK] [cp4waiops] Job = 1
>>> [TOTAL JOB] = 41
Key missing resources
For the list of missing resources, review the REPORT OF MISSING OBJECTS (PROD_VER=<version>) section of the log, where <version> is the version of IBM Cloud Pak for AIOps that is installed.
This report includes the results of a scan for the resources that are expected to exist after a successful installation. The list of resources that are scanned is configurable, and can include any resource type (deployments, statefulsets, pods, strimzipodset, and more).
When reviewing the results, review the [SCAN RESULT] and [SCAN SUMMARY] sections for details. The results list:
- Any missing resources and their expected count.
- Resources that exist, but have mismatched counts, such as when 2 are expected, but only 1 exists
For any [Objects Not Matched] section for a context in the report, the section lists resources that are found, but are not configured in the scan as needed or critical resources. These results are not cause for concern.
The following log example shows a missing objects report for a IBM Cloud Pak for AIOps deployment:
===================================================
REPORT OF MISSING OBJECTS (PROD_GROUP = cp4aiops@ibm-cp-aiops / PROD_VER = 4.4.0)
===================================================
NOTE(1): Please be as accurate as possible with the regex of OBJNAME. Otherwise, an object is considered found as long as there is at least one instance!
NOTE(2): The algorithm is based on matching 'oc get' returned object name against AWK regular expression defined by 'OBJNAME'!
NOTE(3): For missing object with label [Count condition OK], it is likely to be either optional or deleted job pod. To investigate further!
[INPUT FILE]
/tmp/waiops-mustgather/config/missingobj/4.4.0/config/missingobj.cfg
[INPUT FILE PROCESSING DETAILS]
Total config line read = 642
Total config line skipped = 344
Total config line excluded = 62
Total config line re-generated = 236
Total config line untouched = 0
Total config line (final) = 236
[SCAN RESULT]
No object is found missing!
[SCAN CONFIGURATION DETAILS]
Total configuration line = 236
Total skipped configuration = 0
[STATISTICS]
Context [cp4aiops/deployment] : Total Config = 96 / Total Config Hit = 96 / Total Config Missed = 0 / Total Objects Found = 96 / Total Objects Matched = 96 / Total Objects Not Matched = 0
Context [cp4aiops/pod] : Total Config = 112 / Total Config Hit = 112 / Total Config Missed = 0 / Total Objects Found = 242 / Total Objects Matched = 210 / Total Objects Not Matched = 0 / Total Excluded Objects Removed = 32
Context [cp4aiops/statefulset] : Total Config = 14 / Total Config Hit = 14 / Total Config Missed = 0 / Total Objects Found = 14 / Total Objects Matched = 14 / Total Objects Not Matched = 0
Context [cp4aiops/strimzipodset] : Total Config = 2 / Total Config Hit = 2 / Total Config Missed = 0 / Total Objects Found = 2 / Total Objects Matched = 2 / Total Objects Not Matched = 0
Context [ibm-cert-manager/deployment] : Total Config = 4 / Total Config Hit = 4 / Total Config Missed = 0 / Total Objects Found = 4 / Total Objects Matched = 4 / Total Objects Not Matched = 0
Context [ibm-cert-manager/pod] : Total Config = 4 / Total Config Hit = 4 / Total Config Missed = 0 / Total Objects Found = 4 / Total Objects Matched = 4 / Total Objects Not Matched = 0
Context [ibm-licensing/deployment] : Total Config = 2 / Total Config Hit = 2 / Total Config Missed = 0 / Total Objects Found = 2 / Total Objects Matched = 2 / Total Objects Not Matched = 0
Context [ibm-licensing/pod] : Total Config = 2 / Total Config Hit = 2 / Total Config Missed = 0 / Total Objects Found = 2 / Total Objects Matched = 2 / Total Objects Not Matched = 0
[SCAN SUMMARY]
Total namespace(s) scanned = [3] [cp4aiops ibm-cert-manager ibm-licensing]
Total objects matched = 334
No object is found missing!
No object with mismatched count is found!
Scan for missing objects is completed.
Basic compliance check results
For the results from a basic compliance check, review the [AIOPs <version>] COMPLIANCE REPORT section of the log, where <version> is the version of IBM Cloud Pak for AIOps that is installed.
This report indicates the results from the compliance check, which which checks for adherence to configured compliance rules
The following log example shows a complaince report for a IBM Cloud Pak for AIOps deployment:
===================================================
[PRODUCT GROUP = cp4aiops@aiops-installation / WAIOPS v4.4.0] COMPLIANCE SUMMARY REPORT
===================================================
Total PROCESSED compliance rules = [2]
Total PASSED compliance rules = [2]
>>> [ocpversion,aimgr-subs-health]
Total FAILED compliance rules = [0]
[Mon Jan 8 10:27:48 CST 2024] [printSummaryLog] Displaying COMPLIANCE_REPORT.log [/tmp/mg/COMPLIANCE_REPORT.log.56430] on screen...
===================================================
[PRODUCT GROUP = cp4aiops@aiops-installation / WAIOPS v4.4.0] COMPLIANCE REPORT
===================================================
[TAGNAME] = ocpversion
[SOURCE OBJECT] =
[TARGET OBJECT] =
[COMPLIANCE SCRIPT] = ~/waiops-mustgather/config/compliance/4.4.0/scripts/ocpversion.sh
[COMPLIANCE MESSAGE] = Openshift version [4.12.36] is supported!
[COMPLIANCE RESULT] = 0 [PASSED]
===================================================
[TAGNAME] = aimgr-subs-health
[SOURCE OBJECT] = cp4aiops/subscriptions/aimanager-operator,cp4aiops/subscriptions/aiops-ibm-common-services,cp4aiops/subscriptions/aiopsedge-operator,cp4aiops/subscriptions/asm-operator,cp4aiops/subscriptions/cloud-native-postgresql,cp4aiops/subscriptions/ibm-aiops-orchestrator,cp4aiops/subscriptions/ibm-automation-elastic,cp4aiops/subscriptions/ibm-automation-flink,cp4aiops/subscriptions/ibm-events-operator,cp4aiops/subscriptions/ibm-idp-config-ui-operator,cp4aiops/subscriptions/ibm-im-mongodb-operator,cp4aiops/subscriptions/ibm-im-operator,cp4aiops/subscriptions/ibm-platformui-operator,cp4aiops/subscriptions/ibm-redis-cp,cp4aiops/subscriptions/ibm-secure-tunnel-operator,cp4aiops/subscriptions/ibm-watson-aiops-ui-operator,cp4aiops/subscriptions/ir-ai-operator,cp4aiops/subscriptions/ir-core-operator,cp4aiops/subscriptions/ir-lifecycle-operator,cp4aiops/subscriptions/operand-deployment-lifecycle-manager-app
[TARGET OBJECT] =
[COMPLIANCE SCRIPT] = ~/waiops-mustgather/config/compliance/4.4.0/scripts/subs-health.sh
[COMPLIANCE MESSAGE] = (1) aimanager-operator = [OK]
(2) aiops-ibm-common-services = [OK]
(3) aiopsedge-operator = [OK]
(4) asm-operator = [OK]
(5) cloud-native-postgresql = [OK]
(6) ibm-aiops-orchestrator = [OK]
(7) ibm-automation-elastic = [OK]
(8) ibm-automation-flink = [OK]
(9) ibm-events-operator = [OK]
(10) ibm-idp-config-ui-operator = [OK]
(11) ibm-im-mongodb-operator = [OK]
(12) ibm-im-operator = [OK]
(14) ibm-platformui-operator = [OK]
(15) ibm-redis-cp = [OK]
(16) ibm-secure-tunnel-operator = [OK]
(17) ibm-watson-aiops-ui-operator = [OK]
(18) ir-ai-operator = [OK]
(19) ir-core-operator = [OK]
(20) ir-lifecycle-operator = [OK]
(21) operand-deployment-lifecycle-manager-app = [OK]
[COMPLIANCE RESULT] = 0 [PASSED]