Jump To Close Expand all Collapse all Table of contents Troubleshooting 1. Troubleshooting Expand section "1. Troubleshooting" Collapse section "1. Troubleshooting" 1.1. Documented troubleshooting 1.2. Running the must-gather command to troubleshoot Expand section "1.2. Running the must-gather command to troubleshoot" Collapse section "1.2. Running the must-gather command to troubleshoot" 1.2.1. Must-gather scenarios 1.2.2. Must-gather procedure 1.2.3. Must-gather in a disconnected environment 1.3. Troubleshooting installation status stuck in installing or pending Expand section "1.3. Troubleshooting installation status stuck in installing or pending" Collapse section "1.3. Troubleshooting installation status stuck in installing or pending" 1.3.1. Symptom: Stuck in Pending status 1.3.2. Resolving the problem: Adjust worker node sizing 1.4. Troubleshooting reinstallation failure Expand section "1.4. Troubleshooting reinstallation failure" Collapse section "1.4. Troubleshooting reinstallation failure" 1.4.1. Symptom: Reinstallation failure 1.4.2. Resolving the problem: Reinstallation failure 1.5. Troubleshooting an offline cluster Expand section "1.5. Troubleshooting an offline cluster" Collapse section "1.5. Troubleshooting an offline cluster" 1.5.1. Symptom: Cluster status is offline 1.5.2. Resolving the problem: Cluster status is offline 1.6. Troubleshooting a managed cluster import failure Expand section "1.6. Troubleshooting a managed cluster import failure" Collapse section "1.6. Troubleshooting a managed cluster import failure" 1.6.1. Symptom: Imported cluster not available 1.6.2. Resolving the problem: Imported cluster not available 1.7. Troubleshooting cluster with pending import status Expand section "1.7. Troubleshooting cluster with pending import status" Collapse section "1.7. Troubleshooting cluster with pending import status" 1.7.1. Symptom: Cluster with pending import status 1.7.2. Identifying the problem: Cluster with pending import status 1.7.3. Resolving the problem: Cluster with pending import status 1.8. Troubleshooting cluster with already exists error Expand section "1.8. Troubleshooting cluster with already exists error" Collapse section "1.8. Troubleshooting cluster with already exists error" 1.8.1. Symptom: Already exists error log when importing OpenShift Container Platform cluster 1.8.2. Identifying the problem: Already exists when importing OpenShift Container Platform cluster 1.8.3. Resolving the problem: Already exists when importing OpenShift Container Platform cluster 1.9. Troubleshooting cluster creation on VMware vSphere Expand section "1.9. Troubleshooting cluster creation on VMware vSphere" Collapse section "1.9. Troubleshooting cluster creation on VMware vSphere" 1.9.1. Managed cluster creation fails with certificate IP SAN error Expand section "1.9.1. Managed cluster creation fails with certificate IP SAN error" Collapse section "1.9.1. Managed cluster creation fails with certificate IP SAN error" 1.9.1.1. Symptom: Managed cluster creation fails with certificate IP SAN error 1.9.1.2. Identifying the problem: Managed cluster creation fails with certificate IP SAN error 1.9.1.3. Resolving the problem: Managed cluster creation fails with certificate IP SAN error 1.9.2. Managed cluster creation fails with unknown certificate authority Expand section "1.9.2. Managed cluster creation fails with unknown certificate authority" Collapse section "1.9.2. Managed cluster creation fails with unknown certificate authority" 1.9.2.1. Symptom: Managed cluster creation fails with unknown certificate authority 1.9.2.2. Identifying the problem: Managed cluster creation fails with unknown certificate authority 1.9.2.3. Resolving the problem: Managed cluster creation fails with unknown certificate authority 1.9.3. Managed cluster creation fails with expired certificate Expand section "1.9.3. Managed cluster creation fails with expired certificate" Collapse section "1.9.3. Managed cluster creation fails with expired certificate" 1.9.3.1. Symptom: Managed cluster creation fails with expired certificate 1.9.3.2. Identifying the problem: Managed cluster creation fails with expired certificate 1.9.3.3. Resolving the problem: Managed cluster creation fails with expired certificate 1.9.4. Managed cluster creation fails with insufficient privilege for tagging Expand section "1.9.4. Managed cluster creation fails with insufficient privilege for tagging" Collapse section "1.9.4. Managed cluster creation fails with insufficient privilege for tagging" 1.9.4.1. Symptom: Managed cluster creation fails with insufficient privilege for tagging 1.9.4.2. Identifying the problem: Managed cluster creation fails with insufficient privilege for tagging 1.9.4.3. Resolving the problem: Managed cluster creation fails with insufficient privilege for tagging 1.9.5. Managed cluster creation fails with invalid dnsVIP Expand section "1.9.5. Managed cluster creation fails with invalid dnsVIP" Collapse section "1.9.5. Managed cluster creation fails with invalid dnsVIP" 1.9.5.1. Symptom: Managed cluster creation fails with invalid dnsVIP 1.9.5.2. Identifying the problem: Managed cluster creation fails with invalid dnsVIP 1.9.5.3. Resolving the problem: Managed cluster creation fails with invalid dnsVIP 1.9.6. Managed cluster creation fails with incorrect network type Expand section "1.9.6. Managed cluster creation fails with incorrect network type" Collapse section "1.9.6. Managed cluster creation fails with incorrect network type" 1.9.6.1. Symptom: Managed cluster creation fails with incorrect network type 1.9.6.2. Identifying the problem: Managed cluster creation fails with incorrect network type 1.9.6.3. Resolving the problem: Managed cluster creation fails with incorrect network type 1.9.7. Managed cluster creation fails with an error processing disk changes Expand section "1.9.7. Managed cluster creation fails with an error processing disk changes" Collapse section "1.9.7. Managed cluster creation fails with an error processing disk changes" 1.9.7.1. Symptom: Adding the VMware vSphere managed cluster fails due to an error processing disk changes 1.9.7.2. Identifying the problem: Adding the VMware vSphere managed cluster fails due to an error processing disk changes 1.9.7.3. Resolving the problem: Adding the VMware vSphere managed cluster fails due to an error processing disk changes 1.10. Managed cluster creation fails on Red Hat OpenStack Platform with unknown authority error Expand section "1.10. Managed cluster creation fails on Red Hat OpenStack Platform with unknown authority error" Collapse section "1.10. Managed cluster creation fails on Red Hat OpenStack Platform with unknown authority error" 1.10.1. Symptom: Managed cluster creation fails with unknown authority error 1.10.2. Identifying the problem: Managed cluster creation fails with unknown authority error 1.10.3. Resolving the problem: Managed cluster creation fails with unknown authority error 1.11. Troubleshooting OpenShift Container Platform version 3.11 cluster import failure Expand section "1.11. Troubleshooting OpenShift Container Platform version 3.11 cluster import failure" Collapse section "1.11. Troubleshooting OpenShift Container Platform version 3.11 cluster import failure" 1.11.1. Symptom: OpenShift Container Platform version 3.11 cluster import failure 1.11.2. Identifying the problem: OpenShift Container Platform version 3.11 cluster import failure 1.11.3. Resolving the problem: OpenShift Container Platform version 3.11 cluster import failure 1.12. Troubleshooting imported clusters offline after certificate change Expand section "1.12. Troubleshooting imported clusters offline after certificate change" Collapse section "1.12. Troubleshooting imported clusters offline after certificate change" 1.12.1. Symptom: Clusters offline after certificate change 1.12.2. Identifying the problem: Clusters offline after certificate change 1.12.3. Resolving the problem: Clusters offline after certificate change 1.13. Namespace remains after deleting a cluster Expand section "1.13. Namespace remains after deleting a cluster" Collapse section "1.13. Namespace remains after deleting a cluster" 1.13.1. Symptom: Namespace remains after deleting a cluster 1.13.2. Resolving the problem: Namespace remains after deleting a cluster 1.14. Auto-import-secret-exists error when importing a cluster Expand section "1.14. Auto-import-secret-exists error when importing a cluster" Collapse section "1.14. Auto-import-secret-exists error when importing a cluster" 1.14.1. Symptom: Auto import secret exists error when importing a cluster 1.14.2. Resolving the problem: Auto-import-secret-exists error when importing a cluster 1.15. Troubleshooting cluster status changing from offline to available Expand section "1.15. Troubleshooting cluster status changing from offline to available" Collapse section "1.15. Troubleshooting cluster status changing from offline to available" 1.15.1. Symptom: Cluster status changing from offline to available 1.15.2. Resolving the problem: Cluster status changing from offline to available 1.16. Troubleshooting cluster in console with pending or failed status Expand section "1.16. Troubleshooting cluster in console with pending or failed status" Collapse section "1.16. Troubleshooting cluster in console with pending or failed status" 1.16.1. Symptom: Cluster in console with pending or failed status 1.16.2. Identifying the problem: Cluster in console with pending or failed status 1.16.3. Resolving the problem: Cluster in console with pending or failed status 1.17. Troubleshooting application Git server connection Expand section "1.17. Troubleshooting application Git server connection" Collapse section "1.17. Troubleshooting application Git server connection" 1.17.1. Symptom: Git server connection 1.17.2. Resolving the problem: Git server connection 1.18. Troubleshooting Grafana Expand section "1.18. Troubleshooting Grafana" Collapse section "1.18. Troubleshooting Grafana" 1.18.1. Symptom: Grafana explorer gateway timeout 1.18.2. Resolving the problem: Configure the Grafana 1.19. Troubleshooting local cluster not selected with placement rule Expand section "1.19. Troubleshooting local cluster not selected with placement rule" Collapse section "1.19. Troubleshooting local cluster not selected with placement rule" 1.19.1. Symptom: Troubleshooting local cluster not selected as a managed cluster 1.19.2. Resolving the problem: Troubleshooting local cluster not selected as a managed cluster 1.20. Troubleshooting application Kubernetes deployment version Expand section "1.20. Troubleshooting application Kubernetes deployment version" Collapse section "1.20. Troubleshooting application Kubernetes deployment version" 1.20.1. Symptom: Application deployment version 1.20.2. Resolving the problem: Application deployment version 1.21. Troubleshooting Klusterlet with degraded conditions Expand section "1.21. Troubleshooting Klusterlet with degraded conditions" Collapse section "1.21. Troubleshooting Klusterlet with degraded conditions" 1.21.1. Symptom: Klusterlet is in the degraded condition 1.21.2. Identifying the problem: Klusterlet is in the degraded condition 1.21.3. Resolving the problem: Klusterlet is in the degraded condition 1.22. Troubleshooting Object storage channel secret Expand section "1.22. Troubleshooting Object storage channel secret" Collapse section "1.22. Troubleshooting Object storage channel secret" 1.22.1. Symptom: Object storage channel secret 1.22.2. Resolving the problem: Object storage channel secret 1.23. Troubleshooting observability Expand section "1.23. Troubleshooting observability" Collapse section "1.23. Troubleshooting observability" 1.23.1. Symptom: MultiClusterObservability resource status stuck 1.23.2. Resolving the problem: MultiClusterObservability resource status stuck 1.24. Troubleshooting OpenShift monitoring service Expand section "1.24. Troubleshooting OpenShift monitoring service" Collapse section "1.24. Troubleshooting OpenShift monitoring service" 1.24.1. Symptom: OpenShift monitoring service is not ready 1.24.2. Resolving the problem: OpenShift monitoring service is not ready 1.25. Troubleshooting metrics-collector Expand section "1.25. Troubleshooting metrics-collector" Collapse section "1.25. Troubleshooting metrics-collector" 1.25.1. Symptom: metrics-collector cannot verify observability-client-ca-certificate 1.25.2. Resolving the problem: metrics-collector cannot verify observability-client-ca-certificate 1.26. Troubleshooting PostgreSQL shared memory error Expand section "1.26. Troubleshooting PostgreSQL shared memory error" Collapse section "1.26. Troubleshooting PostgreSQL shared memory error" 1.26.1. Symptom: PostgreSQL shared memory error 1.26.2. Resolving the problem: PostgreSQL shared memory error 1.27. Troubleshooting Submariner not connecting after installation Expand section "1.27. Troubleshooting Submariner not connecting after installation" Collapse section "1.27. Troubleshooting Submariner not connecting after installation" 1.27.1. Symptom: Submariner not connecting after installation 1.27.2. Identifying the problem: Submariner not connecting after installation 1.27.3. Resolving the problem: Submariner not connecting after installation 1.28. Troubleshooting Submariner add-on status is degraded Expand section "1.28. Troubleshooting Submariner add-on status is degraded" Collapse section "1.28. Troubleshooting Submariner add-on status is degraded" 1.28.1. Symptom: Submariner add-on status is degraded 1.28.2. Resolving the problem: Submariner add-on status is degraded 1.29. Troubleshooting restore status finishes with errors Expand section "1.29. Troubleshooting restore status finishes with errors" Collapse section "1.29. Troubleshooting restore status finishes with errors" 1.29.1. Symptom: Troubleshooting restore status finishes with errors 1.29.2. Resolving the problem: Troubleshooting restore status finishes with errors 1.30. Generic resources are removed when restoring a hub cluster backup Expand section "1.30. Generic resources are removed when restoring a hub cluster backup" Collapse section "1.30. Generic resources are removed when restoring a hub cluster backup" 1.30.1. Symptom: Generic resources are removed when restoring a hub cluster backup 1.30.2. Resolving the problem: Generic resources are removed when restoring a hub cluster backup 1.31. Troubleshooting OADP custom resource definitions Expand section "1.31. Troubleshooting OADP custom resource definitions" Collapse section "1.31. Troubleshooting OADP custom resource definitions" 1.31.1. Symptom: OADP custom resource definitions 1.31.2. Resolving the problem: OADP custom resource definitions 1.32. Troubleshooting multiline YAML parsing Expand section "1.32. Troubleshooting multiline YAML parsing" Collapse section "1.32. Troubleshooting multiline YAML parsing" 1.32.1. Symptom: Troubleshooting multiline YAML parsing 1.32.2. Resolving the problem: Troubleshooting multiline YAML parsing Legal Notice Settings Close Language: English 简体中文 日本語 한국어 Language: English 简体中文 日本語 한국어 Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Language and Page Formatting Options Language: English 简体中文 日本語 한국어 Language: English 简体中文 日本語 한국어 Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Troubleshooting Red Hat Advanced Cluster Management for Kubernetes 2.8TroubleshootingLegal NoticeAbstract View a list of troubleshooting topics for your cluster. You can also use the must-gather command to collect logs. Next