Bug 1814332
| Summary: | Cluster needs to backfill infrastructure.status.infraPlatform | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> |
| Component: | Installer | Assignee: | Abhinav Dahiya <adahiya> |
| Installer sub component: | openshift-installer | QA Contact: | Etienne Simard <esimard> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | adahiya, bleanhar, cblecker, esimard, juzhao, lseelye, mfojtik, nmalik, travi, wking, yanyang |
| Version: | 4.4 | Keywords: | ServiceDeliveryImpact |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Addition of new field for clusters installed after 4.1
Consequence: The operators have to check and use old fields for clusters that were installed as 4.1 creating error during upgrades
Fix: Migration controller sets the new fields for all clusters during upgrade using the information already available in the cluster
Result: All the clients can depend on new fields reducing bugs.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-08-04 18:05:55 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
Clayton Coleman
2020-03-17 16:48:02 UTC
I am trying to reproduce it. The cluster installed with 4.1 does not have platformStatus filled. After cluster upgrade to 4.4, it still does not have platformStatus filled. Install an AWS cluster with 4.1 and check the infrastructure: # oc get clusterversions NAME VERSION version 4.1.38 # oc get infrastructure.config.openshift.io -o yaml apiVersion: v1 items: - apiVersion: config.openshift.io/v1 kind: Infrastructure metadata: creationTimestamp: "2020-04-22T08:10:38Z" generation: 1 name: cluster resourceVersion: "404" selfLink: /apis/config.openshift.io/v1/infrastructures/cluster uid: c0279e9d-8470-11ea-a8ed-02eb38e8de4a spec: cloudConfig: name: "" status: apiServerInternalURI: https://api-int.yanyang-4-1.qe.devcluster.openshift.com:6443 apiServerURL: https://api.yanyang-4-1.qe.devcluster.openshift.com:6443 etcdDiscoveryDomain: yanyang-4-1.qe.devcluster.openshift.com infrastructureName: yanyang-4-1-m7wtn platform: AWS <------ there is no platformStatus kind: List metadata: resourceVersion: "" selfLink: "" Upgrade the cluster to 4.4 and check the infrastructure. # oc get clusterversion NAME VERSION version 4.4.0-rc.9 # oc get infrastructures.config.openshift.io -o yaml apiVersion: v1 items: - apiVersion: config.openshift.io/v1 kind: Infrastructure metadata: creationTimestamp: "2020-04-22T08:10:38Z" generation: 1 name: cluster resourceVersion: "404" selfLink: /apis/config.openshift.io/v1/infrastructures/cluster uid: c0279e9d-8470-11ea-a8ed-02eb38e8de4a spec: cloudConfig: name: "" status: apiServerInternalURI: https://api-int.yanyang-4-1.qe.devcluster.openshift.com:6443 apiServerURL: https://api.yanyang-4-1.qe.devcluster.openshift.com:6443 etcdDiscoveryDomain: yanyang-4-1.qe.devcluster.openshift.com infrastructureName: yanyang-4-1-m7wtn platform: AWS <------ There is still no platformStatus configuration kind: List metadata: resourceVersion: "" selfLink: "" > After cluster upgrade to 4.4...
This bug targets 4.5, so you have to update all the way to a 4.5 nightly that includes the patches config operator.
Verified with: 4.5.0-0.nightly-2020-05-04-113741
Upgrade path: 4.1.38 -> 4.2.29 -> 4.3.18 -> 4.4.3 -> 4.5.0-0.nightly-2020-05-04-113741
Before upgrade to 4.5 (platformStatus is not present)
~~~
$ oc get infrastructure.config.openshift.io -o yaml
apiVersion: v1
items:
- apiVersion: config.openshift.io/v1
kind: Infrastructure
metadata:
creationTimestamp: "2020-05-04T23:26:09Z"
generation: 1
name: cluster
resourceVersion: "402"
selfLink: /apis/config.openshift.io/v1/infrastructures/cluster
uid: a2bd0777-8e5e-11ea-945f-026a593e29d4
spec:
cloudConfig:
name: ""
status:
apiServerInternalURI: https://api-int.cluster.qe.devcluster.openshift.com:6443
apiServerURL: https://api.cluster.qe.openshift.com:6443
etcdDiscoveryDomain: cluster.qe.openshift.com
infrastructureName: cluster-azj38
platform: AWS
kind: List
metadata:
resourceVersion: ""
selfLink: ""
~~~
After upgrade to 4.5 (platformStatus is present)
~~~
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.5.0-0.nightly-2020-05-04-113741 True False 77s Cluster version is 4.5.0-0.nightly-2020-05-04-113741
$ oc get infrastructure.config.openshift.io -o yaml
apiVersion: v1
items:
- apiVersion: config.openshift.io/v1
kind: Infrastructure
metadata:
creationTimestamp: "2020-05-04T23:26:09Z"
generation: 1
name: cluster
resourceVersion: "140951"
selfLink: /apis/config.openshift.io/v1/infrastructures/cluster
uid: a2bd0777-8e5e-11ea-945f-026a593e29d4
spec:
cloudConfig:
name: ""
status:
apiServerInternalURI: https://api-int.cluster.qe.devcluster.openshift.com:6443
apiServerURL: https://api.cluster.qe.openshift.com:6443
etcdDiscoveryDomain: cluster.qe.openshift.com
infrastructureName: cluster-azj38
platform: AWS
platformStatus:
aws:
region: us-east-2
type: AWS
kind: List
metadata:
resourceVersion: ""
selfLink: ""
~~~
*** Bug 1788437 has been marked as a duplicate of this bug. *** 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 (OpenShift Container Platform 4.5 image release 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 |