Hide Forgot
Description of problem: The installer creates pv and pvc according to the volume name. If the volume name is not "registry",the docker-registry pod can't be started. Version-Release number of selected component (if applicable): openshift-ansible/master How reproducible: always Steps to Reproduce: 1. Enable NFS on inventory file 2. set volume name to a customlized name. For example: openshift_hosted_registry_storage_volume_name=registry123 3. ansible-playbook -i config/aepnfs31 /usr/share/ansible/openshift-ansible/playbooks/byo/config.yml 4. check the pv, pvc and dc Actual results: #oc get pv NAME LABELS CAPACITY ACCESSMODES STATUS CLAIM REASON AGE registry123-volume <none> 5Gi RWX Bound default/registry123-claim 11m # oc get pvc NAME LABELS STATUS VOLUME CAPACITY ACCESSMODES AGE registry123-claim <none> Bound registry123-volume 5Gi RWX 11m # oc get dc docker-registry -o yaml |grep claim claimName: registry-claim Expected results: The pv/pvc name is the fix value registry. or the dc are updated according to the volume name. Additional info:
Proposed fix: https://github.com/openshift/openshift-ansible/pull/1486
The docker-registry can be started now. so move to verified. # oc get dc docker-registry -o json |grep claim "claimName": "registry124-claim"
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-2016:1065