Bug 1653626
| Summary: | [cloud] controller-manager logs output nil when update machineset replicas | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | sunzhaohua <zhsun> |
| Component: | Cloud Compute | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED ERRATA | QA Contact: | sunzhaohua <zhsun> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | jhou, zhsun |
| Target Milestone: | --- | ||
| Target Release: | 4.1.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: | 2019-06-04 10:41:04 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
2018-11-27 10:17:36 UTC
Merged upstream, next step is to sync cluster-api dep. We have recently merged PR [1] that carries the upstream PR [2] (mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1653626#c1). See [3] for details. [1] https://github.com/openshift/cluster-api-provider-aws/pull/127 [2] https://github.com/kubernetes-sigs/cluster-api/pull/626 [3] https://github.com/openshift/cluster-api-provider-aws/pull/127/commits/44661f6ee1eec5ecb7b3e079cce05c7097ae2b86#diff-f9f7cdf568e7ecf8fda70cb304e31ad8R339 Verified. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-01-11-000044 True False 1h Cluster version is 4.0.0-0.nightly-2019-01-11-000044 $ oc edit machineset zhsun-worker-us-east-2a machineset.cluster.k8s.io/zhsun-worker-us-east-2a edited controller-manager logs no nil info. 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-2019:0758 |