Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1488366 - Installation fails with the following problem -> The PersistentVolume "BS31369_ocp_registry-volume" is invalid: metadata.name: Invalid value: "XX11111_ocp_registry-volume": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '. [NEEDINFO]
Installation fails with the following problem -> The PersistentVolume "BS3136...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.6.0
Unspecified Unspecified
low Severity high
: ---
: 3.7.0
Assigned To: Scott Dodson
Gaoyun Pei
3.7-release-plan
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-05 04:29 EDT by Miheer Salunke
Modified: 2017-11-28 17:09 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The example inventories have been updated to clearly indicate that the nfs export directory must only consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:09:17 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
tmorriso: needinfo? (vigoyal)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Comment 4 Scott Dodson 2017-09-06 10:18:05 EDT
Kubernetes requires that the volume name conform to naming standards. The workaround is to set openshift_hosted_registry_storage_volume_name to a value that conforms to DNS-1123 standards.

The volume name is also used to create a directory in the nfs exports directory.
Comment 9 Traci Morrison 2017-09-21 15:12:20 EDT
Hi Scott, can you please confirm where this update should be made? I checked the Installation Guide, but not sure which section. Thanks.
Comment 10 Traci Morrison 2017-10-02 15:12:38 EDT
Hi Scott, can you please confirm where this update should be made? I checked the Installation Guide, but not sure which section. Thanks.
Comment 11 Scott Dodson 2017-10-03 10:33:06 EDT
This set of options doesn't appear to be documented in openshift-docs. So I'm going to move this back to the installer and update the sample inventory files.
Comment 12 Traci Morrison 2017-10-03 14:19:28 EDT
Hi Vikram, please see Scott's comment above. Should we defer this issue for now? Thanks.
Comment 14 Gaoyun Pei 2017-10-11 04:39:40 EDT
QE could reproduce such issue when using an invalid nfs directory name. And in openshift-ansible-3.7.0-0.143.2.git.0.39404c5.el7.noarch, we already have related content added in the sample inventory file, move this bug as verified.

[root@gpei-test-ansible openshift-ansible-auto]# grep openshift_hosted_registry_storage_nfs_directory -B 2 /usr/share/doc/openshift-ansible-docs-3.7.0/docs/example-inventories/hosts.example
# nfs_directory must conform to DNS-1123 subdomain must consist of lower case
# alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character
#openshift_hosted_registry_storage_nfs_directory=/exports
--
# nfs_directory must conform to DNS-1123 subdomain must consist of lower case
# alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character
#openshift_hosted_registry_storage_nfs_directory=/exports
Comment 18 errata-xmlrpc 2017-11-28 17:09:17 EST
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/RHSA-2017:3188

Note You need to log in before you can comment on or make changes to this bug.