-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.16
-
None
-
No
-
Rejected
-
False
-
Description of problem:
Version-Release number of selected component (if applicable):
4.16
How reproducible:
100%
Steps to Reproduce:
1: enable UWM and set external alertmanager for prometheus ******************** apiVersion: v1 kind: ConfigMap metadata: name: cluster-monitoring-config namespace: openshift-monitoring data: config.yaml: | enableUserWorkload: true prometheusK8s: additionalAlertmanagerConfigs: - scheme: http apiVersion: v1 staticConfigs: - alertmanager-operated.openshift-user-workload-monitoring.svc:9093 2: create Alertmanager under openshift-user-workload-monitoring ******************** apiVersion: monitoring.coreos.com/v1 kind: Alertmanager metadata: name: test-am namespace: openshift-user-workload-monitoring spec: replicas: 1 3: check alertmanager pod is created
Actual results:
% oc -n openshift-user-workload-monitoring get pod NAME READY STATUS RESTARTS AGE prometheus-operator-c95b98b57-k25xb 2/2 Running 0 58m prometheus-user-workload-0 6/6 Running 0 37m prometheus-user-workload-1 6/6 Running 0 38m thanos-ruler-user-workload-0 4/4 Running 0 33m thanos-ruler-user-workload-1 4/4 Running 0 33m
Expected results:
oc -n openshift-user-workload-monitoring get pod NAME READY STATUS RESTARTS AGE alertmanager-test-am-0 2/2 Running 0 26s prometheus-operator-7b6cbb587-qw8j7 2/2 Running 0 3h2m prometheus-user-workload-0 5/5 Running 0 8m34s prometheus-user-workload-1 5/5 Running 0 8m40s thanos-ruler-user-workload-0 3/3 Running 0 31m thanos-ruler-user-workload-1 3/3 Running 0 31m
Additional info:
% oc version Client Version: 4.16.0-0.nightly-2024-02-26-013420 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: 4.16.0-0.nightly-2024-04-23-032717 Kubernetes Version: v1.29.4+d9d4530