Bug 1568260 - [CNS][3.7] docker registry back end storage keep pending with invalid AccessModes error when glusterfs_registry_block_storageclass as default storageclass
Summary: [CNS][3.7] docker registry back end storage keep pending with invalid AccessM...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.7.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.7.z
Assignee: Jose A. Rivera
QA Contact: Wenkai Shi
URL:
Whiteboard:
Depends On: 1544387 1574382
Blocks: 1541443
TreeView+ depends on / blocked
 
Reported: 2018-04-17 04:37 UTC by Wenkai Shi
Modified: 2018-05-18 03:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1544387
Environment:
Last Closed: 2018-05-18 03:54:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-04-17 04:37:01 UTC
Red Hat Product Errata RHBA-2018:1576 0 None None None 2018-05-18 03:55:08 UTC

Comment 1 Jose A. Rivera 2018-04-18 17:14:29 UTC 
PR to fix this has been submitted, please test: 

https://github.com/openshift/openshift-ansible/pull/8023
Comment 3 Wenkai Shi 2018-05-08 06:17:37 UTC 
Verified with version openshift-ansible-3.7.46-1.git.0.37f607e.el7, AccessModes is good now.

# oc get pvc 
NAME             STATUS    VOLUME            CAPACITY   ACCESSMODES   STORAGECLASS   AGE
registry-claim   Bound     registry-volume   5Gi        RWX                          5m

# 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: {}
Comment 6 errata-xmlrpc 2018-05-18 03:54:45 UTC 
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:1576
Note You need to log in before you can comment on or make changes to this bug.