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

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Documentation for Openshift, docker, etc. suggest that if you have a blank disk you can add a configuration like so:

# cat <<EOF > /etc/sysconfig/docker-storage-setup
DEVS=/dev/vdc
VG=docker-vg
EOF

See https://docs.openshift.com/enterprise/3.0/admin_guide/install/prerequisites.html as an example where this configuration is described.

The problem is that after the initial run where the thin pool is created the script docker-storage-setup script sees that there are partitions on the disk, exits 1, and causes the service to report a failed state. 

This configuration is only ever good for one run. You can remove the DEVS line after the initial setup and it will start normally, but it seems this should be documented or handled better.


Version-Release number of selected component (if applicable):
docker-1.7.1-108.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install docker
2. Use a DEVS= entry in /etc/sysconfig/docker-storage-setup
3. Start and then restart the docker-storage-setup service

Actual results:
service enters a failed state

Expected results:
service should not enter a failed state.

Additional info:

John Any update on this?

PR created and being reviewed.

Fixed in https://github.com/projectatomic/docker-storage-setup/pull/85

In docker-1.9.1-38.el7.x86_64

#docker-storage-setup 
....
Converted docker-vg/docker-pool to thin pool.
  Logical volume "docker-pool" changed.
# service docker start
# service docker-storage-setup start
Redirecting to /bin/systemctl start  docker-storage-setup.service
# echo $?
0
# service docker-storage-setup restart
Redirecting to /bin/systemctl restart  docker-storage-setup.service
# echo $?
0

Move to verified

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://rhn.redhat.com/errata/RHSA-2016-1034.html