Bug 1945333

Summary:	ovn-kubernetes daemon set should meet platform requirements for update strategy that have maxUnavailable update of 10 or 33 percent
Product:	OpenShift Container Platform	Reporter:	Tinashe Chipomho <tchipomh>
Component:	Networking	Assignee:	Ben Pickard <bpickard>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	low
Priority:	low	CC:	aconstan, aos-bugs, eparis, jokerman, keyoung, mfojtik
Version:	4.7	Keywords:	Reopened
Target Milestone:	---	Flags:	mfojtik: needinfo?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	LifecycleStale
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-10 17:52:01 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 Tinashe Chipomho 2021-03-31 17:14:48 UTC

Description of problem:
Running conformance tests on ocp4.7 with RAN DU profile results in Daemonsets found that do not meet platform requirements for update strategy

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

Client Version: 4.7.0-0.nightly-2021-03-14-223051
Server Version: 4.7.0-0.nightly-2021-03-14-223051
Kubernetes Version: v1.20.0+bafe72f

How reproducible:
Run origin-tests against an ipv6 only enabled cluster. 

Steps to Reproduce:
1. ./openshift-tests run openshift/conformance/parallel --junit-dir . --


Actual results:
fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Mar 29 09:16:53.945: Daemonsets found that do not meet platform requirements for update strategy:
  expected daemonset openshift-image-registry/node-ca to have maxUnavailable 10% or 33% (see comment) instead of 1
  expected daemonset openshift-network-diagnostics/network-check-target to have maxUnavailable 10% or 33% (see comment) instead of 1
  expected daemonset openshift-ovn-kubernetes/ovnkube-node to have maxUnavailable 10% or 33% (see comment) instead of 1
  expected daemonset openshift-ovn-kubernetes/ovs-node to have maxUnavailable 10% or 33% (see comment) instead of 1

Expected results:
[sig-arch] Managed cluster should only include cluster daemonsets that have maxUnavailable update of 10 or 33 percent [Suite:openshift/conformance/parallel] should pass

Additional info:

Comment 1 Michal Fojtik 2021-04-30 18:06:07 UTC

This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.

Comment 2 Stefan Schimanski 2021-05-18 08:29:24 UTC

Having this on openshift-apiserver has no value. openshift-apiserver has nothing to do with these failures. Create BZs for each of the offenders.

Comment 3 Tinashe Chipomho 2021-05-18 08:38:57 UTC

(In reply to Stefan Schimanski from comment #2)
> Having this on openshift-apiserver has no value. openshift-apiserver has
> nothing to do with these failures. Create BZs for each of the offenders.

Noted, currently doing that.

Comment 4 Ben Pickard 2021-06-04 17:57:00 UTC


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

Comment 7 Ben Pickard 2021-06-10 17:52:01 UTC

confusion about upgrade strategy / lack of activity around this bug