Jump To Close Expand all Collapse all Table of contents Troubleshooting 1. Troubleshooting Expand section "1. Troubleshooting" Collapse section "1. Troubleshooting" 1.1. Must-gather 1.2. Running must-gather in a disconnected environment 1.3. Documented troubleshooting 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 failed uninstallation because resources exist Expand section "1.5. Troubleshooting failed uninstallation because resources exist" Collapse section "1.5. Troubleshooting failed uninstallation because resources exist" 1.5.1. Symptom: Failed uninstallation because resources exist 1.5.2. Resolving the problem: Failed uninstallation because resources exist 1.6. Troubleshooting an offline cluster Expand section "1.6. Troubleshooting an offline cluster" Collapse section "1.6. Troubleshooting an offline cluster" 1.6.1. Symptom: Cluster status is offline 1.6.2. Resolving the problem: Cluster status is offline 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 creation on VMware vSphere Expand section "1.8. Troubleshooting cluster creation on VMware vSphere" Collapse section "1.8. Troubleshooting cluster creation on VMware vSphere" 1.8.1. Managed cluster creation fails with certificate IP SAN error Expand section "1.8.1. Managed cluster creation fails with certificate IP SAN error" Collapse section "1.8.1. Managed cluster creation fails with certificate IP SAN error" 1.8.1.1. Symptom: Managed cluster creation fails with certificate IP SAN error 1.8.1.2. Identifying the problem: Managed cluster creation fails with certificate IP SAN error 1.8.1.3. Resolving the problem: Managed cluster creation fails with certificate IP SAN error 1.8.2. Managed cluster creation fails with unknown certificate authority Expand section "1.8.2. Managed cluster creation fails with unknown certificate authority" Collapse section "1.8.2. Managed cluster creation fails with unknown certificate authority" 1.8.2.1. Symptom: Managed cluster creation fails with unknown certificate authority 1.8.2.2. Identifying the problem: Managed cluster creation fails with unknown certificate authority 1.8.2.3. Resolving the problem: Managed cluster creation fails with unknown certificate authority 1.8.3. Managed cluster creation fails with expired certificate Expand section "1.8.3. Managed cluster creation fails with expired certificate" Collapse section "1.8.3. Managed cluster creation fails with expired certificate" 1.8.3.1. Symptom: Managed cluster creation fails with expired certificate 1.8.3.2. Identifying the problem: Managed cluster creation fails with expired certificate 1.8.3.3. Resolving the problem: Managed cluster creation fails with expired certificate 1.8.4. Managed cluster creation fails with insufficient privilege for tagging Expand section "1.8.4. Managed cluster creation fails with insufficient privilege for tagging" Collapse section "1.8.4. Managed cluster creation fails with insufficient privilege for tagging" 1.8.4.1. Symptom: Managed cluster creation fails with insufficient privilege for tagging 1.8.4.2. Identifying the problem: Managed cluster creation fails with insufficient privilege for tagging 1.8.4.3. Resolving the problem: Managed cluster creation fails with insufficient privilege for tagging 1.8.5. Managed cluster creation fails with invalid dnsVIP Expand section "1.8.5. Managed cluster creation fails with invalid dnsVIP" Collapse section "1.8.5. Managed cluster creation fails with invalid dnsVIP" 1.8.5.1. Symptom: Managed cluster creation fails with invalid dnsVIP 1.8.5.2. Identifying the problem: Managed cluster creation fails with invalid dnsVIP 1.8.5.3. Resolving the problem: Managed cluster creation fails with invalid dnsVIP 1.8.6. Managed cluster creation fails with incorrect network type Expand section "1.8.6. Managed cluster creation fails with incorrect network type" Collapse section "1.8.6. Managed cluster creation fails with incorrect network type" 1.8.6.1. Symptom: Managed cluster creation fails with incorrect network type 1.8.6.2. Identifying the problem: Managed cluster creation fails with incorrect network type 1.8.6.3. Resolving the problem: Managed cluster creation fails with incorrect network type 1.8.7. Managed cluster creation fails with an error processing disk changes Expand section "1.8.7. Managed cluster creation fails with an error processing disk changes" Collapse section "1.8.7. Managed cluster creation fails with an error processing disk changes" 1.8.7.1. Symptom: Adding the VMware vSphere managed cluster fails due to an error processing disk changes 1.8.7.2. Identifying the problem: Adding the VMware vSphere managed cluster fails due to an error processing disk changes 1.8.7.3. Resolving the problem: Adding the VMware vSphere managed cluster fails due to an error processing disk changes 1.9. Troubleshooting OpenShift Container Platform version 3.11 cluster import failure Expand section "1.9. Troubleshooting OpenShift Container Platform version 3.11 cluster import failure" Collapse section "1.9. Troubleshooting OpenShift Container Platform version 3.11 cluster import failure" 1.9.1. Symptom: OpenShift Container Platform version 3.11 cluster import failure 1.9.2. Identifying the problem: OpenShift Container Platform version 3.11 cluster import failure 1.9.3. Resolving the problem: OpenShift Container Platform version 3.11 cluster import failure 1.10. Troubleshooting imported clusters offline after certificate change Expand section "1.10. Troubleshooting imported clusters offline after certificate change" Collapse section "1.10. Troubleshooting imported clusters offline after certificate change" 1.10.1. Symptom: Clusters offline after certificate change 1.10.2. Identifying the problem: Clusters offline after certificate change 1.10.3. Resolving the problem: Clusters offline after certificate change 1.11. Namespace remains after deleting a cluster Expand section "1.11. Namespace remains after deleting a cluster" Collapse section "1.11. Namespace remains after deleting a cluster" 1.11.1. Symptom: Namespace remains after deleting a cluster 1.11.2. Resolving the problem: Namespace remains after deleting a cluster 1.12. Troubleshooting cluster status changing from offline to available Expand section "1.12. Troubleshooting cluster status changing from offline to available" Collapse section "1.12. Troubleshooting cluster status changing from offline to available" 1.12.1. Symptom: Cluster status changing from offline to available 1.12.2. Resolving the problem: Cluster status changing from offline to available 1.13. Troubleshooting cluster in console with pending or failed status Expand section "1.13. Troubleshooting cluster in console with pending or failed status" Collapse section "1.13. Troubleshooting cluster in console with pending or failed status" 1.13.1. Symptom: Cluster in console with pending or failed status 1.13.2. Identifying the problem: Cluster in console with pending or failed status 1.13.3. Resolving the problem: Cluster in console with pending or failed status 1.14. Troubleshooting application Git server connection Expand section "1.14. Troubleshooting application Git server connection" Collapse section "1.14. Troubleshooting application Git server connection" 1.14.1. Symptom: Git server connection 1.14.2. Resolving the problem: Git server connection 1.15. Troubleshooting local cluster not selected with placement rule Expand section "1.15. Troubleshooting local cluster not selected with placement rule" Collapse section "1.15. Troubleshooting local cluster not selected with placement rule" 1.15.1. Symptom: Troubleshooting local cluster not selected 1.15.2. Resolving the problem: Troubleshooting local cluster not selected 1.16. Troubleshooting application Kubernetes deployment version Expand section "1.16. Troubleshooting application Kubernetes deployment version" Collapse section "1.16. Troubleshooting application Kubernetes deployment version" 1.16.1. Symptom: Application deployment version 1.16.2. Resolving the problem: Application deployment version 1.17. Troubleshooting standalone subscription memory Expand section "1.17. Troubleshooting standalone subscription memory" Collapse section "1.17. Troubleshooting standalone subscription memory" 1.17.1. Symptom: Standalone subscription memory 1.17.2. Resolving the problem: Standalone subscription memory 1.18. Troubleshooting Klusterlet with degraded conditions Expand section "1.18. Troubleshooting Klusterlet with degraded conditions" Collapse section "1.18. Troubleshooting Klusterlet with degraded conditions" 1.18.1. Symptom: Klusterlet is in the degraded condition 1.18.2. Identifying the problem: Klusterlet is in the degraded condition 1.18.3. Resolving the problem: Klusterlet is in the degraded condition 1.19. Troubleshooting Klusterlet application manager on managed clusters Expand section "1.19. Troubleshooting Klusterlet application manager on managed clusters" Collapse section "1.19. Troubleshooting Klusterlet application manager on managed clusters" 1.19.1. Symptom: Klusterlet application manager on managed cluster 1.19.2. Resolving the problem: Klusterlet application manager on managed cluster 1.20. Troubleshooting observability Expand section "1.20. Troubleshooting observability" Collapse section "1.20. Troubleshooting observability" 1.20.1. Symptom: MultiClusterObservability resource status stuck 1.20.2. Resolving the problem: MultiClusterObservability resource status stuck 1.21. Troubleshooting OpenShift monitoring service Expand section "1.21. Troubleshooting OpenShift monitoring service" Collapse section "1.21. Troubleshooting OpenShift monitoring service" 1.21.1. Symptom: OpenShift monitoring service is not ready 1.21.2. Resolving the problem: OpenShift monitoring service is not ready 1.22. Undesired label value in managedcluster resource Expand section "1.22. Undesired label value in managedcluster resource" Collapse section "1.22. Undesired label value in managedcluster resource" 1.22.1. Symptom: Undesired label value in managedcluster resource 1.22.2. Resolving the problem: Undesired label value in managedcluster resource 1.23. Troubleshooting the metrics-collector Expand section "1.23. Troubleshooting the metrics-collector" Collapse section "1.23. Troubleshooting the metrics-collector" 1.23.1. Symptom 1: Certification is invalid 1.23.2. Resolving the problem: Certification is invalid 1.23.3. Symptom 2: Storage in mounted persistent volume is used up 1.23.4. Resolving the problem: Storage in mounted persistent volume is used up 1.24. Current data on the Grafana dashboard disappears Expand section "1.24. Current data on the Grafana dashboard disappears" Collapse section "1.24. Current data on the Grafana dashboard disappears" 1.24.1. Symptom 1: Current data on the Grafana dashboard disappears 1.24.2. Symptom 2: PVC does not change after editing statefulSetSize 1.24.3. Resolving the problem: Expand the PVC size 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.1TroubleshootingRed Hat Advanced Cluster Management for Kubernetes TeamLegal NoticeAbstract Troubleshooting in Red Hat Advanced Cluster Management for Kubernetes Next