Bug 1329220

Summary: docker-latest-storage-setup error
Product: Red Hat Enterprise Linux 7 Reporter: Jeremy Eder <jeder>
Component: docker-latestAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: lsu, vgoyal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: docker-latest-1.10.3-20.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-23 16:19:54 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:

Comment 2 Vivek Goyal 2016-04-21 14:38:22 UTC 
Above patch is wrong. How can you check for value of variable without initializing it. (docker-latest_devmapper_meta_dir)

We have following

DOCKER_METADATA_DIR="/var/lib/docker"

We have to make sure that for docker-latest package it is changed to.

DOCKER_METADATA_DIR="/var/lib/docker-latest"
Comment 4 Luwen Su 2016-06-12 14:49:38 UTC 
In docker-latest-1.10.3-40.el7.x86_64

#cat /etc/sysconfig/docker-latest-storage-setup

DEVS=/dev/vdb
VG=docker-latest-test
WIPE_SIGNATURES=true

# docker-latest-storage-setup 
INFO: Volume group backing root filesystem could not be determined
INFO: Device /dev/vdb is already partitioned and is part of volume group docker-latest-test
  Rounding up size to full physical extent 12.00 MiB
  Logical volume "docker-latest-poolmeta" created.
  Logical volume "docker-latest-pool" created.
  WARNING: Converting logical volume docker-latest-test/docker-latest-pool and docker-latest-test/docker-latest-poolmeta to pool's data and metadata volumes.
  THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.)
  Converted docker-latest-test/docker-latest-pool to thin pool.
  Logical volume "docker-latest-pool" changed.
Comment 6 errata-xmlrpc 2016-06-23 16:19:54 UTC 
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:1275