Bug 1229374

Summary:	docker-storage-setup: Check if metadata volume already exist and use it
Product:	Red Hat Enterprise Linux 7	Reporter:	Vivek Goyal <vgoyal>
Component:	docker	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED ERRATA	QA Contact:	Luwen Su <lsu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	lsm5, mjenner, sghosh, walters
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	docker-1.6.2-9.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-23 09:30:20 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:
Embargoed:

Description Vivek Goyal 2015-06-08 14:49:20 UTC

Description of problem:

On rhel, anaconda uses whole of the volume group. But there might be little
space left which is enough for docker-storage-setup to create metadata
volume. And then there is not enough space to create data volume and docker-storage-setup fails leaving metadata volume behind.

Later if user re-runs the script (After adding space to volume group), script
fails complaining that metadata volume already exists.

"Logical volume "docker-poolmeta" already exists in volume group "rhel"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vivek Goyal 2015-06-08 14:50:34 UTC

Created a pull request upstream to address this.

https://github.com/projectatomic/docker-storage-setup/pull/40

Comment 3 Vivek Goyal 2015-06-09 19:33:26 UTC

This patch is merged upstream now. Lokesh can you please pull it in next build of docker.

Comment 5 Luwen Su 2015-06-15 09:13:39 UTC

In docker-1.6.2-10.el7.x86_64,
#docker-storage-setup
Metadata volume docker-poolmeta already exists. Not creating a new one.

Move to verified

Comment 7 errata-xmlrpc 2015-06-23 09:30:20 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://rhn.redhat.com/errata/RHBA-2015-1167.html