Bug 1676758
Summary: | [cloud] "oc get machine/machineset" doesn't work | ||
---|---|---|---|
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 |
Target Milestone: | --- | Keywords: | Regression |
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:44:00 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
2019-02-13 06:06:20 UTC
This is caused by presence of CRDs for both cluster.k8s.io and machine.openshift.io groups. We plan to remove cluster.k8s.io by the end of this week. Verified. clusterversion: 4.0.0-0.nightly-2019-02-17-024922 CRDs for cluster.k8s.io group have been removed. $ oc get machine NAME INSTANCE STATE TYPE REGION ZONE AGE zhsun3-master-0 i-0a765236609bc5c5c running m4.xlarge us-east-2 us-east-2a 39m zhsun3-master-1 i-0f11753514fe829a1 running m4.xlarge us-east-2 us-east-2b 39m zhsun3-master-2 i-017f621bd7be4c38b running m4.xlarge us-east-2 us-east-2c 39m zhsun3-worker-us-east-2a-trztc i-018d9363972d254e4 running m4.large us-east-2 us-east-2a 38m zhsun3-worker-us-east-2b-pc7sg i-0d5c83fa360eaf0a2 running m4.large us-east-2 us-east-2b 38m zhsun3-worker-us-east-2c-7tsk5 i-06723a5b82a2ad7ca running m4.large us-east-2 us-east-2c 38m $ oc get machineset NAME DESIRED CURRENT READY AVAILABLE AGE zhsun3-worker-us-east-2a 1 1 1 1 39m zhsun3-worker-us-east-2b 1 1 1 1 39m zhsun3-worker-us-east-2c 1 1 1 1 39m 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 |