Bug 1568260

Summary:	[CNS][3.7] 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.7.1	CC:	aos-bugs, jarrpa, jokerman, mmccomas, wmeng
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	3.7.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-18 03:54:45 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, 1574382
Bug Blocks:	1541443

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