Bug 1957498

Summary:	cluster-etcd-operator: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21
Product:	OpenShift Container Platform	Reporter:	Sam Batschelet <sbatsche>
Component:	Etcd	Assignee:	Sam Batschelet <sbatsche>
Status:	CLOSED ERRATA	QA Contact:	Sandeep <skundu>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.8	CC:	geliu, lcosic, obulatov, skundu, wking
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 17:30:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sam Batschelet 2021-05-05 21:07:40 UTC

Description of problem: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21, move to v1.

ref: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-etcd-operator/586/pull-ci-openshift-cluster-etcd-operator-master-e2e-aws-disruptive/1390034764819337216/artifacts/e2e-aws-disruptive/gather-extra/artifacts/pods/openshift-etcd-operator_etcd-operator-567787fcc9-7b96w_etcd-operator.log

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


How reproducible: 100%


Steps to Reproduce:
1.
2.
3.

Actual results: deprecated message spams logs


Expected results: no scary logs


Additional info:

Comment 2 W. Trevor King 2021-05-10 13:12:07 UTC

Seems to be causing trouble with 4.7->4.8 update CI [1]:

  Cluster did not complete upgrade: timed out waiting for the condition: Cluster operator etcd is degraded

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-aws-upgrade/1391669539493646336

Comment 3 Suresh Kolichala 2021-05-11 14:32:10 UTC

Since the original PR is reverted, putting the BZ back to ASSIGNED state.

Comment 6 Sam Batschelet 2021-06-01 19:53:02 UTC

*** Bug 1966441 has been marked as a duplicate of this bug. ***

Comment 9 Sandeep 2021-08-24 15:25:10 UTC

The original PR is reverted. So it's expected to be in assigned state.

Comment 10 Lili Cosic 2021-09-09 07:43:23 UTC

Actually this has been merged as we are using the only policyv1.PodDisruptionBudget -> https://github.com/openshift/cluster-etcd-operator/pull/631

Comment 13 Sandeep 2021-10-05 07:24:41 UTC


Below steps followed to verify : 


[skundu@skundu ~]$ oc get po -n openshift-etcd-operator
NAME                           READY   STATUS    RESTARTS       AGE
etcd-operator-dd7fd669-c4xq4   1/1     Running   1 (138m ago)   141m
[skundu@skundu ~]$ oc logs -n openshift-etcd-operator etcd-operator-dd7fd669-c4xq4 : // No error found.
[skundu@skundu ~]$ oc logs -n openshift-etcd-operator etcd-operator-dd7fd669-c4xq4 | grep "PodDisruptionBudget" 
No occurrence of any error related to "PodDisruptionBudget" was found.

Comment 15 errata-xmlrpc 2021-10-18 17:30:57 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759