Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1601083

Summary: OCP 3.10 not creating registry gluster PV
Product: OpenShift Container Platform Reporter: Annette Clewett <aclewett>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED DUPLICATE QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.10.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
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: 2018-07-18 20:25:51 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 Annette Clewett 2018-07-13 20:10:37 UTC 
Description of problem:

Version-Release number of the following components:

Running from clone of openshift-ansible branch=release-3.10, commit e15de49c91d8e7cd6693470d5bc61a53fcb6c079.

$ rpm -q ansible
ansible-2.4.4.0-1.el7ae.noarch

$ ansible --version
ansible 2.4.4.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/ec2-user/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Feb 20 2018, 09:19:12) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]

The inventory file options below should create a gluster-file PV of the size=20Gi mounted to the registry POD(s) that will be on the infra node

# registry
openshift_hosted_registry_storage_kind=glusterfs
openshift_hosted_registry_storage_volume_size=10Gi
openshift_hosted_registry_selector='node-role.kubernetes.io/infra=true'

What I have found is that instead the registry PV is claimed from the default storageclass, in this case gp2 because of 'openshift_cloudprovider_kind=aws'. The PV=registry-volume does get created but it is not used.

If I make glusterfs-storage the only default storageclass and deploy the registry I will get the registry PV claimed from the glusterfs-storage SC but this is the way it worked before.

Currently to back the registry with a gluster-file PV requires that glusterfs-storage is the default SC AND there are two volumes created on gluster. The volume registry-volume is not used. For OCP 3.9 the pv and pvc below went together.

persistentvolume/registry-volume                            10Gi       RWX            Retain           Available

pvc-a34b5191-8634-11e8-a9e1-025daced8a8e   10Gi       RWX            Delete           Bound       default/registry-claim                glusterfs-storage
Comment 1 Annette Clewett 2018-07-13 20:30:31 UTC 
Error above in description. Both are PVs. Here is the associated PVC that is being used to as storage for the registry. PVC registry-claim hould go with PV registry-volume, not PV=pvc-a34b5191-8634-11e8-a9e1-025daced8a8e.

$ oc get pvc
NAME             STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS        AGE
registry-claim   Bound     pvc-a34b5191-8634-11e8-a9e1-025daced8a8e   10Gi       RWX            glusterfs-storage   19h
Comment 2 Scott Dodson 2018-07-18 20:25:51 UTC 
I believe this is a dupe of 1593612

*** This bug has been marked as a duplicate of bug 1593612 ***