Bug 1809265
Summary: | ROKS: add IBMCloud status to platform status API | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Cesar Wong <cewong> |
Component: | openshift-apiserver | Assignee: | ayma <ayma> |
Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.4 | CC: | aos-bugs, cewong, deads, mfojtik |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | IBMROKS | ||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:17:25 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
Cesar Wong
2020-03-02 18:07:30 UTC
Ah, also there was bug 1800507 :) Verified on 4.5.0-0.nightly-2020-03-30-203132 Running `oc explain infrastructure.status.platformStatus.ibmcloud` returns the expected structure Checked in 4.5.0-0.nightly-2020-03-31-225120 env: $ oc explain infrastructure.status.platformStatus # shows field ibmcloud is included ... gcp <Object> GCP contains settings specific to the Google Cloud Platform infrastructure provider. ibmcloud <Object> IBMCloud contains settings specific to the IBMCloud infrastructure provider. openstack <Object> OpenStack contains settings specific to the OpenStack infrastructure provider. ... Could move to Verified. If there is IBMCloud env, it's better if could verify `oc get infrastructure -o yaml` whether including status.platformStatus.ibmcloud correctly. 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:2409 |