Bug 1990012 - ControllerConfig Infrastructure does not match cluster Infrastructure resource
Summary: ControllerConfig Infrastructure does not match cluster Infrastructure resource
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: MCO Team
QA Contact: Rio Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-04 14:53 UTC by Joel Speed
Modified: 2021-11-01 01:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-29 15:21:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2702 0 None Merged Bug 1990012: Update controller config openapi schema 2021-11-02 22:43:15 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-11-01 01:38:14 UTC

Description Joel Speed 2021-08-04 14:53:29 UTC
Description of problem:

The MCO collates information from various sources into a `ControllerConfig` resource. It is responsible for keeping these sources synced into the spec of the `ControllerConfig` so that the MCC can load the information from this config to render MachineConfigs.

It is expected therefore, that there should be no difference between the `ControllerConfig` spec.infra and the `Infrastructure` resource in the cluster.

Currently, some fields are not being propagated due to missing fields in the CRD open api definition. When fields are missing in the openAPI schema, they are dropped silently by the API server when being copied across. This leads to the input to the MCC being incorrect and the wrong output being generated.

An example is the field `status.platformStatus.azure.cloudName` which is required to determine if a cluster is running on Azure or Azure Stack Hub to determine whether the cluster should consider itself in-tree or out of tree.

Version-Release number of selected component (if applicable):

4.9

How reproducible:

100%

Steps to Reproduce:
1. Deploy a cluster on Azure
2. Observe the difference between the infrastructure status and the controllerconfig copy of the infrasructure status

Actual results:
Fields are missing

Expected results:
They should be identical

Additional info:

Comment 4 errata-xmlrpc 2021-11-01 01:38:13 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759


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