Bug 1775730 - Error in updating master machines in private cluster on GCP
Summary: Error in updating master machines in private cluster on GCP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Alberto
QA Contact: Gaoyun Pei
URL:
Whiteboard:
: 1775786 (view as bug list)
Depends On: 1774388
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-22 16:47 UTC by Alberto
Modified: 2020-01-23 11:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1774388
Environment:
Last Closed: 2020-01-23 11:13:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 2713 0 'None' 'open' 'bug 1775730: Stop setting non existent public target pool when InternalPublishingStrategy on GCP master machines' 2019-11-22 21:33:44 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:14:20 UTC

Comment 1 Abhinav Dahiya 2019-11-22 19:46:34 UTC
*** Bug 1775786 has been marked as a duplicate of this bug. ***

Comment 3 Gaoyun Pei 2019-11-26 07:56:12 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

Comment 5 errata-xmlrpc 2020-01-23 11:13:48 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, 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


Note You need to log in before you can comment on or make changes to this bug.