Created attachment 1502798 [details] configmap and prometheus-operator pod logs Description of problem: Deploy cluster monitoring with OCP images, "flag provided but not defined: -namespaces" error for prometheus-operator # oc -n openshift-monitoring get pod NAME READY STATUS RESTARTS AGE cluster-monitoring-operator-65c4b68b44-2wc5s 1/1 Running 0 17m prometheus-operator-5cd9c78bfb-bdbv2 0/1 CrashLoopBackOff 8 17m ********************************************************************************************** # oc -n openshift-monitoring logs prometheus-operator-5cd9c78bfb-bdbv2 flag provided but not defined: -namespaces Usage of /usr/bin/operator: ........................ ----------snipped---------- Version-Release number of selected component (if applicable): ose-cluster-monitoring-operator-v4.0.0-0.48.0.0 ose-prometheus-operator-v4.0.0-0.48.0.0 How reproducible: Always Steps to Reproduce: 1. Deploy cluster monitoring with OCP images 2. 3. Actual results: "flag provided but not defined: -namespaces" error for prometheus-operator Expected results: prometheus-operator should be healthy Additional info:
Blocks installation with OCP images
This is related to us not having bumped the prometheus-operator repository to the appropriate version, this is in progress. https://github.com/openshift/prometheus-operator/pull/10
https://github.com/openshift/prometheus-operator/pull/10 is now merged and new ose-prometheus-operator-v4.0.0-0 should be built. Can you please retest the cluster monitoring operator on OSE to verify that this problem is resolved?
Still seeing this in 4.0.0-0.75.0. # oc logs prometheus-operator-57ccd85b94-dhxdn |head -n5 flag provided but not defined: -namespaces Usage of /usr/bin/operator: -alertmanager-default-base-image string Alertmanager default base image (default "quay.io/prometheus/alertmanager") -alsologtostderr
# skopeo inspect --tls-verify=false docker://satellite.home.nicknach.net:8888/openshift/ose-prometheus-operator:v4.0 |grep release "release": "0.74.0.0",
(In reply to lserven from comment #3) > https://github.com/openshift/prometheus-operator/pull/10 is now merged and > new ose-prometheus-operator-v4.0.0-0 should be built. Can you please retest > the cluster monitoring operator on OSE to verify that this problem is > resolved? Issue is not fixed, see Comment 4 and Comment 5. Do we need to test the OCP images by using the Next-Gen installer?
Still not fixed in 0.79.0.0
@Lucas See Comment 5, Comment 7, Comment 8. Issue is not fixed. Do we need to test the OCP images by using the Next-Gen installer?
confirmed fixed in 4.0.0-0.93.0 (docker container runtime). I'll test crio here in a bit. Thanks! -Nick
Issue is fixed, see Comment 15
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758