Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1827706

Summary: release-openshift-ocp-installer-e2e-gcp-4.2 failing with no worker nodes
Product: OpenShift Container Platform Reporter: Miciah Dashiel Butler Masters <mmasters>
Component: Cloud ComputeAssignee: Alberto <agarcial>
Cloud Compute sub component: Other Providers QA Contact: Milind Yadav <miyadav>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: aos-bugs, bparees, jokerman, jupierce, mifiedle, wking, xtian
Version: 4.2.zKeywords: Reopened, TestBlocker
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1827779 (view as bug list) Environment:
Last Closed: 2020-04-29 12:32:52 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:
Bug Depends On:    
Bug Blocks: 1827779    

Description Miciah Dashiel Butler Masters 2020-04-24 15:21:51 UTC
Description of problem:

Multiple runs of the release-openshift-ocp-installer-e2e-gcp-4.2 job have failed on initialization with the common symptom that there are no worker nodes:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.2/620
...
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.2/628
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.2/629
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.2/630

I checked in nodes.json for the above listed jobs and saw no worker nodes.  The job has failed all of the most recent 11 runs.

Comment 2 Abhinav Dahiya 2020-04-24 15:27:24 UTC
Seeing this failure in machine api controller logs


panic: semver: Parse(doozer-failure-5ed92c18-055634): No Major.Minor.Patch elements found

goroutine 1 [running]:
github.com/blang/semver.MustParse(0x19a9890, 0x1e, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/go/src/github.com/openshift/cluster-api-provider-gcp/vendor/github.com/blang/semver/semver.go:356 +0x1c1
github.com/openshift/cluster-api-provider-gcp/pkg/version.init.ializers()
	/go/src/github.com/openshift/cluster-api-provider-gcp/pkg/version/version.go:16 +0x78


Moving to art

Comment 3 W. Trevor King 2020-04-24 18:32:40 UTC
ART tried to revert that earlier; maybe they missed a rebuild?

Comment 4 W. Trevor King 2020-04-24 18:34:28 UTC
E.g. see [1] about the ART reversion.  Also bug 1824943 about machine-api operator setting conditions when the operand is crashlooping.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1826265#c3

Comment 5 Ben Parees 2020-04-24 19:01:41 UTC
moving to 4.5 to get off the blocker list and will clone back to 4.2.z.  (need the 4.5 bz to keep eparis' bot happy)

Comment 6 Luke Meyer 2020-04-24 19:34:18 UTC
ART's semver issue never applied below 4.4.

Sorry I'm not adept at reading these tests and I can't tell from this report what exactly is showing up without a semver version. Is it the thing running the test, a component in a 4.2 ci build, ...? Where do the above logs come from?

Pass it back if this looks like a problem with an OCP build (brew NVR would be appreciated).

Comment 7 Abhinav Dahiya 2020-04-24 20:05:04 UTC
The installer team can't fix the controllers for machine-api

moving it to cloud team to figure out how to work with ART to fix it.

Comment 12 W. Trevor King 2020-04-29 00:07:56 UTC
*** Bug 1829028 has been marked as a duplicate of this bug. ***

Comment 13 Mike Fiedler 2020-04-29 00:28:00 UTC
This is not resolved.  4.2.30 installs fail on GCP.   We need the fix in 4.2.30

Comment 16 Scott Dodson 2020-04-29 12:08:04 UTC
*** Bug 1827779 has been marked as a duplicate of this bug. ***

Comment 18 Scott Dodson 2020-04-29 12:32:52 UTC
Since Bug 1829028 actually has supporting data I'm inverting the duplicate bug relationship

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