Bug 1761887 - Cluster upgrade fails due to UpdatingPrometheusOperatorFailed problem
Summary: Cluster upgrade fails due to UpdatingPrometheusOperatorFailed problem
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.2.z
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
Depends On: 1761721
TreeView+ depends on / blocked
Reported: 2019-10-15 13:56 UTC by Frederic Branczyk
Modified: 2019-11-13 18:56 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-13 18:55:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 507 0 'None' closed Bug 1761887: tasks/prometheusoperator: Change deployment selector migration strategy 2020-06-17 13:09:02 UTC
Red Hat Product Errata RHBA-2019:3303 0 None None None 2019-11-13 18:56:02 UTC

Description Frederic Branczyk 2019-10-15 13:56:55 UTC
This bug was initially created as a copy of Bug #1761721

I am copying this bug because: 

Description of problem:
Upgrading 4.1 cluster to 4.2 fails as it cannot reconcile Prometheus Operator Deployment due to invalid value in spec.selector field:

Oct 14 18:32:25.357 E clusteroperator/monitoring changed Degraded to True: UpdatingPrometheusOperatorFailed: Failed to rollout the stack. Error: running task Updating Prometheus Operator failed: reconciling Prometheus Operator Deployment failed: updating deployment object failed: Deployment.apps "prometheus-operator" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/component":"controller", "app.kubernetes.io/name":"prometheus-operator"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

More in:

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

How reproducible:
Upgrade cluster from 4.1 to 4.2

Steps to Reproduce:
1. Create a 4.1 cluster
2. Do the upgrade

Actual results:
Cluster is not upgraded due to problems with CMO

Expected results:
Cluster is upgraded or CMO is not degraded.

Additional info:

Comment 8 errata-xmlrpc 2019-11-13 18:55:51 UTC
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.


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