Description of problem: Add "IBMCloud" in `oc explain infrastructure.status.platformStatus` output Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-02-07-012035 How reproducible: Always Steps to Reproduce: 1. oc explain infrastructure.status.platformStatus ... FIELDS: ... ovirt <Object> Ovirt contains settings specific to the oVirt infrastructure provider. type <string> type is the underlying infrastructure provider for the cluster. This value controls whether infrastructure automation such as service load balancers, dynamic volume provisioning, machine creation and deletion, and other integrations are enabled. If None, no infrastructure automation is enabled. Allowed values are "AWS", "Azure", "BareMetal", "GCP", "Libvirt", "OpenStack", "VSphere", "oVirt", and "None"... Actual results: 1. Does not include "IBMCloud" Expected results: 1. Include "IBMCloud", since https://bugzilla.redhat.com/show_bug.cgi?id=1796161#c4 shows to enable IBM cloud. Checked the PR https://github.com/openshift/api/pull/557/files , in config/v1/types_infrastructure.go, the part `type PlatformStatus struct {` missed to add it. Additional info:
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
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