Prometheus failing after configuring AdditionalAlertManagerConfigs in RHOCP 4

Issue

• After configuring AdditionalAlertManagerConfigs the prometheus pods are failing to start because not able to mount some secrets with the error:

  119d        Warning   FailedMount         pod/prometheus-k8s-1                       Unable to attach or mount volumes: unmounted volumes=[secret-alertmanager-bearer-token secret-alertmanager-tls], unattached volumes=[secret-prometheus-k8s-thanos-sidecar-tls config prometheus-trusted-ca-bundle prometheus-k8s-db configmap-kubelet-serving-ca-bundle secret-grpc-tls secret-hub-alertmanager-router-ca web-config config-out secret-prometheus-k8s-tls secret-observability-alertmanager-accessor kube-api-access-jvnxg secret-metrics-client-certs metrics-client-ca secret-prometheus-k8s-proxy prometheus-k8s-rulefiles-0 secret-kube-etcd-client-certs tls-assets configmap-serving-certs-ca-bundle configmap-metrics-client-ca secret-kube-rbac-proxy]: timed out waiting for the condition