Bug 1568260 – [CNS][3.7] docker registry back end storage keep pending with invalid AccessModes error when glusterfs_registry_block_storageclass as default storageclass

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.7.1
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	3.7.z
Assigned To:	Jose A. Rivera
QA Contact:	Wenkai Shi
Docs Contact:

URL:
Whiteboard:
Keywords:	TestBlocker

Depends On:	1544387 1574382
Blocks:	1541443
	Show dependency tree / graph

Reported:	2018-04-17 00:37 EDT by Wenkai Shi
Modified:	2018-05-17 23:55 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:	1544387
Environment:
Last Closed:	2018-05-17 23:54:45 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0489	None	None	None	2018-04-17 00:37 EDT
Red Hat Product Errata	RHBA-2018:1576	None	None	None	2018-05-17 23:55 EDT

Groups: None (edit)

Comment 1 Jose A. Rivera 2018-04-18 13:14:29 EDT

PR to fix this has been submitted, please test: 

https://github.com/openshift/openshift-ansible/pull/8023

Comment 3 Wenkai Shi 2018-05-08 02:17:37 EDT

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-17 23:54:45 EDT

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.