Red Hat Bugzilla – Bug 1261565
docker-storage-setup service fails after initial successful run if DEVS is defined in /etc/sysconfig/docker-storage-setup
Last modified: 2016-05-12 11:16:09 EDT
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
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):
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
service enters a failed state
service should not enter a failed state.
John Any update on this?
PR created and being reviewed.
Fixed in https://github.com/projectatomic/docker-storage-setup/pull/85
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 $?
# service docker-storage-setup restart
Redirecting to /bin/systemctl restart docker-storage-setup.service
# echo $?
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.