https://issues.redhat.com/browse/ACM-16278 removing KI

release_notes/known_issues_observability.adoc

@@ -27,38 +27,6 @@ For your {ocp} cluster, see link:https://docs.redhat.com/documentation/en-us/ope
 
 For more about deprecations and removals, see xref:../release_notes/acm_deprecate_remove.adoc#deprecations-removals-acm[Deprecations and removals for {acm-short}]. 
 
-[#grafana-dashboard-missing]
-== Grafana dashboard missing 
-//2.12:14639
-
-A Grafana dashboard might fail to load after you run the Grafana instance. Complete the following steps:
-
-. To verify whether a dashboard failed to load, check the logs by running the following command:
-
-+
-[source,bash]
-----
-oc logs observability-grafana-68f8489659-m79rv -c grafana-dashboard-loader -n open-cluster-management-observability
-...
-E1017 12:55:24.532493 1 dashboard_controller.go:147] dashboard: sample-dashboard could not be created after retrying 40 times
-----
-
-. To fix the dashboard failure, redeploy Grafana by scaling the number of replicas to `0`. The `multicluster-observability-operator` pod automatically scales the deployment to the desired number of replicas that is defined in the `MultiClusterObservability` resource. Run the following command:
-
-+
-[source,bash]
-----
-oc scale deployment observability-grafana -n open-cluster-management-observability --replicas=0
-----
-
-. To verify that the dashboard loads correctly after redployment, run the following command to check the logs of all Grafana pods and ensure no error message appears:
-
-+
-[source,bash]
-----
-oc logs observability-grafana-68f8489659-h6jd9 -c grafana-dashboard-loader -n open-cluster-management-observability | grep "could not be created"
-----
-
 [#retention-change]
 == Retention change causes data loss 
 //2.11:11048