Bug 1987914 - Missing part-of label on prometheus-operator deployment
Summary: Missing part-of label on prometheus-operator deployment
Status: CLOSED DUPLICATE of bug 1956308
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Jayapriya Pai
QA Contact: Junqi Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2021-07-29 16:53 UTC by Robert Bost
Modified: 2021-09-27 01:37 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-30 08:51:13 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Robert Bost 2021-07-29 16:53:52 UTC
Description of problem: During upgrade from 4.7.21 -> 4.8.2, CVO is spinning on prometheus operator webhook:

E0729 16:48:21.339429       1 task.go:112] error running apply for prometheusrule "openshift-marketplace/marketplace-alert-rules" (523 of 676): Internal error occurred: failed calling webhook "prometheusrules.openshift.io": Post "https://prometheus-operator.openshift-monitoring.svc:8080/admission-prometheusrules/validate?timeout=5s": no endpoints available for service "prometheus-operator"

Upon further inspection, the prometheus-operator service's labels do not match the running pod or deployment:

$ oc get pod -n openshift-monitoring -l app.kubernetes.io/component=controller,app.kubernetes.io/name=prometheus-operator,app.kubernetes.io/part-of=openshift-monitoring
No resources found in openshift-monitoring namespace.

Version-Release number of selected component (if applicable): 4.7.21 -> 4.8.2

How reproducible: Unsure

Steps to Reproduce:
1. Initiated upgrade to 4.8.2 via fast channel

Actual results: Stalling upgrade, potentially held up on monitoring cluster operator.

Additional info: This currently impacts the vSphere (VMC) OpenShift CI cluster.

Comment 3 Vadim Rutkovsky 2021-07-30 08:51:13 UTC
CMO updated the service with a new selector, but deployment could not be updated. Closing as duplicate of #1956308

*** This bug has been marked as a duplicate of bug 1956308 ***

Note You need to log in before you can comment on or make changes to this bug.