Bug 1870345

Summary:	[sig-cluster-lifecycle][Feature:Machines][Early] Managed cluster should have same number of Machines and Nodes
Product:	OpenShift Container Platform	Reporter:	David Eads <deads>
Component:	Node	Assignee:	Seth Jennings <sjenning>
Status:	CLOSED ERRATA	QA Contact:	MinLi <minmli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	aos-bugs, jokerman
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	[sig-cluster-lifecycle][Feature:Machines][Early] Managed cluster should have same number of Machines and Nodes
Last Closed:	2020-10-27 16:29:46 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 David Eads 2020-08-19 20:27:09 UTC

test:
[sig-cluster-lifecycle][Feature:Machines][Early] Managed cluster should have same number of Machines and Nodes 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D%5C%5BFeature%3AMachines%5C%5D%5C%5BEarly%5C%5D+Managed+cluster+should+have+same+number+of+Machines+and+Nodes


need to exclude the text on metal.  It appears to have perma-failed https://testgrid.k8s.io/redhat-openshift-ocp-release-4.6-informing#release-openshift-ocp-installer-e2e-metal-compact-4.6

Comment 3 MinLi 2020-08-27 10:24:05 UTC

Hi, @David Eads, @Seth Jennings

I see current CI result, it failed with "Expected":
# [sig-cluster-lifecycle][Feature:Machines][Early] Managed cluster should have same number of Machines and Nodes [Suite:openshift/conformance/parallel]
fail [github.com/openshift/origin@/test/extended/machines/cluster.go:52]: Expected

(https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D%5C%5BFeature%3AMachines%5C%5D%5C%5BEarly%5C%5D+Managed+cluster+should+have+same+number+of+Machines+and+Nodes)

Should we think it is fixed?

Comment 4 Seth Jennings 2020-08-27 13:17:12 UTC

Note, https://github.com/openshift/origin/pull/25428 merged on top of the https://github.com/openshift/origin/pull/25425 yesterday.  This is better check for the platform use of machine API.

And we do expect failures in the test results for clusters that fail to join all their nodes.

Typically "[sig-apps] Deployment should not disrupt a cloud load-balancer's connectivity during rollout [Suite:openshift/conformance/parallel] [Suite:k8s]" also fails in conjunction with the failure of this test.  But the failure is expected.

Comment 5 MinLi 2020-08-28 03:53:48 UTC

according to  Comment 4, verified!

Comment 7 errata-xmlrpc 2020-10-27 16:29:46 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196