Bug 1387815

Summary:

Missing documentation to remove docker-pool when setting up new docker storage

Product:

Red Hat Enterprise Linux 7

Reporter:

Sean V. Thompson <seant>

Component:

doc-RHEL-Atomic

Assignee:

Maxim Svistunov <msvistun>

Status:

CLOSED NOTABUG

QA Contact:

Chris Negus <cnegus>

Severity:

unspecified

Docs Contact:

Vikram Goyal <vigoyal>

Priority:

unspecified

Version:

7.2

CC:

cnegus, seant, vgoyal, yruseva, zdover

Target Milestone:

Keywords:

Documentation, Extras

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2017-04-10 17:43:42 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:

Attachments:

Description	Flags
terminal output of what happens when you run the command before and after deletion	none

Description Sean V. Thompson 2016-10-22 01:41:16 UTC

Created attachment 1212991 [details]
terminal output of what happens when you run the command before and after deletion

Description of problem:
Post-install, in order for me to get this to work, I had to remove the pool[2] that already existed then rerun docker-storage-setup[3].

Version-Release number of selected component (if applicable):
7.2.1. LVM thin pool in the volume group containing the root volume [1]

How reproducible:


Steps to Reproduce:
1. add more space to the volume group 
2. run sudo docker-storage-setup
3. 

Actual results:                         

7.2.1. LVM thin pool in the volume group containing the root volume
By default, docker-storage-setup looks for free space in the root volume group and creates an LVM thin pool. Hence you can leave free space during system installation in the root volume group and starting docker will automatically set up a thin pool and use it.

Expected results:
I would expect the documentation would have a note to remove the docker-pool that already existed before running docker-storage-setup. I presumed that dockerstoragesetup would just extend the docker-pool that was already created. I actually had to delete it.

Additional info:
[1] https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#lvm_thin_pool_in_the_volume_group_containing_the_root_volume
[2]sudo lvremove /dev/atomicos/docker-pool
[3]sudo docker-storage-setup

Comment 4 Vivek Goyal 2017-03-31 15:14:05 UTC

Why did you have to remove existing thin pool?

Comment 5 Vivek Goyal 2017-03-31 15:14:49 UTC

Also, In original RHEL guide, we had put information to remove thin pool as well. So did we lose it while moving to new one?

Comment 8 Sean V. Thompson 2017-04-05 17:15:42 UTC

(In reply to Vivek Goyal from comment #4)
> Why did you have to remove existing thin pool?

According to "1.4.2.2. How to Add Additional Storage to the Host and Extend the Root Partition" @ https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/#using_docker_storage_setup

# systemctl stop docker docker-storage-setup
# rm -rf /var/lib/docker/*
# lvremove atomicos/docker-pool
# lvextend -L +3GB /dev/atomicos/root
# systemctl start docker-storage-setup
# systemctl start docker

It tells me to run these steps which required me to "# lvremove atomicos/docker-pool"

Comment 10 Vivek Goyal 2017-04-10 13:09:03 UTC

(In reply to Sean V. Thompson from comment #8)
> (In reply to Vivek Goyal from comment #4)
> > Why did you have to remove existing thin pool?
> 
> According to "1.4.2.2. How to Add Additional Storage to the Host and Extend
> the Root Partition" @
> https://access.redhat.com/documentation/en-us/
> red_hat_enterprise_linux_atomic_host/7/html-single/managing_containers/
> #using_docker_storage_setup
> 
> # systemctl stop docker docker-storage-setup
> # rm -rf /var/lib/docker/*
> # lvremove atomicos/docker-pool
> # lvextend -L +3GB /dev/atomicos/root
> # systemctl start docker-storage-setup
> # systemctl start docker
> 
> It tells me to run these steps which required me to "# lvremove
> atomicos/docker-pool"

Ok. Yes, this is required if volume group is already full and docker thin pool has already consumed all the free space. In that case we need to first remove docker thin pool, extend root logical volume and then re-create docker thin pool.

So all the steps are listed. So what's the bug about?

Are you saying that we should have a separate section for explaining how to remove thin pool? 

We prefer that user use either "atomic storage reset" to reset storage or follow process described in "Changing Storage Configuration" (section 1.5). Don't want people to be just removing thin pool directly.