Bug 1574382
Summary: | [CNS][3.6] docker registry back end storage keep pending with invalid AccessModes error when glusterfs_registry_block_storageclass as default storageclass | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenkai Shi <weshi> |
Component: | Installer | Assignee: | Jose A. Rivera <jarrpa> |
Status: | CLOSED ERRATA | QA Contact: | Wenkai Shi <weshi> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.1 | CC: | aos-bugs, jarrpa, jokerman, mmccomas, wmeng |
Target Milestone: | --- | Keywords: | TestBlocker |
Target Release: | 3.6.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | 1544387 | Environment: | |
Last Closed: | 2018-05-17 07:58:35 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: | |||
Bug Depends On: | 1544387 | ||
Bug Blocks: | 1568260 |
Comment 1
Wenkai Shi
2018-05-03 07:38:23 UTC
PR is upstream: https://github.com/openshift/openshift-ansible/pull/8252 Verified with version openshift-ansible-3.6.173.0.117-1.git.0.8c22c43.el7, AccessModes is good now. # oc get pvc NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE registry-claim Bound registry-volume 5Gi RWX 14m # oc export pvc registry-claim apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" pv.kubernetes.io/bound-by-controller: "yes" creationTimestamp: null name: registry-claim spec: accessModes: - ReadWriteMany resources: requests: storage: 5Gi storageClassName: "" volumeName: registry-volume status: {} 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-2018:1579 |