Bug 1775730
| Summary: | Error in updating master machines in private cluster on GCP | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Alberto <agarcial> |
| Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
| Status: | CLOSED ERRATA | QA Contact: | Gaoyun Pei <gpei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.3.0 | CC: | adahiya, gpei |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1774388 | Environment: | |
| Last Closed: | 2020-01-23 11:13:48 UTC | Type: | --- |
| 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: | 1774388 | ||
| Bug Blocks: | |||
|
Comment 1
Abhinav Dahiya
2019-11-22 19:46:34 UTC
Verify this bug on payload 4.3.0-0.nightly-2019-11-26-034010. After spinning up a private cluster on GCP, check the master machines, no "Target Pools" being used in machines.Spec. And the master machines' status show correctly. # oc get machines -n openshift-machine-api NAME PHASE TYPE REGION ZONE AGE gpei-5-drkmm-m-0 Running n1-standard-4 us-central1 us-central1-a 22m gpei-5-drkmm-m-1 Running n1-standard-4 us-central1 us-central1-b 22m gpei-5-drkmm-m-2 Running n1-standard-4 us-central1 us-central1-c 22m gpei-5-drkmm-w-a-jzn6j Running n1-standard-4 us-central1 us-central1-a 19m gpei-5-drkmm-w-b-ck74b Running n1-standard-4 us-central1 us-central1-b 19m 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. https://access.redhat.com/errata/RHBA-2020:0062 |