Bug 1856597
| Summary: | [gcp] Termination Pod in CrashLoopBackOff | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | sunzhaohua <zhsun> |
| Component: | Cloud Compute | Assignee: | Alexander Demicev <ademicev> |
| Cloud Compute sub component: | Other Providers | QA Contact: | sunzhaohua <zhsun> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | agarcial |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 16:14:10 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
sunzhaohua
2020-07-14 03:23:54 UTC
this should have been fixed by https://github.com/openshift/cluster-api-provider-gcp/pull/100/commits/f023886d466c3493c0557c5109f3a2ace3c9c639. DOes this build contains that commit? Sunzhaohua can you please also share the clusterOperator status for machine-api? $ oc image info quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:6339413d2db5ade826ae908c23f64f373255262f596d83c10d1e4a9264d42420
io.openshift.build.commit.id=245b58110669b3ae2859fe55b884c7d9d7d74379
So this build contains that commit. I will test this with the latest nightly build.
$ oc get co machine-api -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterOperator
metadata:
annotations:
exclude.release.openshift.io/internal-openshift-hosted: "true"
creationTimestamp: "2020-07-13T09:12:16Z"
generation: 1
managedFields:
- apiVersion: config.openshift.io/v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:exclude.release.openshift.io/internal-openshift-hosted: {}
f:spec: {}
f:status:
.: {}
f:extension: {}
manager: cluster-version-operator
operation: Update
time: "2020-07-13T09:12:16Z"
- apiVersion: config.openshift.io/v1
fieldsType: FieldsV1
fieldsV1:
f:status:
f:conditions: {}
f:relatedObjects: {}
f:versions: {}
manager: machine-api-operator
operation: Update
time: "2020-07-14T10:02:33Z"
name: machine-api
resourceVersion: "899798"
selfLink: /apis/config.openshift.io/v1/clusteroperators/machine-api
uid: d95ba359-c091-42c5-b614-cc734f9995cc
spec: {}
status:
conditions:
- lastTransitionTime: "2020-07-13T09:32:01Z"
reason: AsExpected
status: "False"
type: Progressing
- lastTransitionTime: "2020-07-13T09:28:29Z"
reason: AsExpected
status: "False"
type: Degraded
- lastTransitionTime: "2020-07-13T09:32:01Z"
message: 'Cluster Machine API Operator is available at operator: 4.6.0-0.nightly-2020-07-13-051854'
reason: AsExpected
status: "True"
type: Available
- lastTransitionTime: "2020-07-13T09:28:29Z"
status: "True"
type: Upgradeable
extension: null
relatedObjects:
- group: ""
name: openshift-machine-api
resource: namespaces
- group: machine.openshift.io
name: ""
namespace: openshift-machine-api
resource: machines
- group: machine.openshift.io
name: ""
namespace: openshift-machine-api
resource: machinesets
- group: machine.openshift.io
name: ""
namespace: openshift-machine-api
resource: machinehealthchecks
- group: rbac.authorization.k8s.io
name: ""
namespace: openshift-machine-api
resource: roles
- group: rbac.authorization.k8s.io
name: machine-api-operator
resource: clusterroles
- group: rbac.authorization.k8s.io
name: machine-api-controllers
resource: clusterroles
- group: metal3.io
name: ""
namespace: openshift-machine-api
resource: baremetalhosts
versions:
- name: operator
version: 4.6.0-0.nightly-2020-07-13-051854
@sunzhaohua please hold of re-verifying this for now, there is a new PR that is needed to fix this issue as the original fix did not resolve the issue Verified clusterversion: 4.6.0-0.nightly-2020-07-19-093912 $ oc get po NAME READY STATUS RESTARTS AGE cluster-autoscaler-operator-5f7f65668f-4lmz4 2/2 Running 0 56m machine-api-controllers-8d59c9c6f-q29kw 7/7 Running 0 55m machine-api-operator-f799f5dc5-lfnjh 2/2 Running 0 56m machine-api-termination-handler-nmg8z 1/1 Running 0 12m $ oc get ds NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE machine-api-termination-handler 1 1 1 1 1 machine.openshift.io/interruptible-instance= 51m 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.6 GA Images), 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:4196 |