Bug 1588085

Summary: Unable to use docker container with nvme when it is partitioned
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: ContainerAssignee: Sébastien Han <shan>
Status: CLOSED DUPLICATE QA Contact: Harish NV Rao <hnallurv>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.0CC: amarango, ceph-eng-bugs, evelu, gabrioux
Target Milestone: rc   
Target Release: 3.*   
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: 2018-06-18 14:15:43 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:
Bug Depends On:    
Bug Blocks: 1572368    

Description Mike Hackett 2018-06-06 15:34:47 UTC 
Description of problem:
When using an nvme for both a journal device for an OSD and an OSD for backing the index pool an issue is encountered when creating a docker container with ceph+nvme partitions, the bash scripts doing the OSD prepare inside the container fails because it expects a full drive to be provided and not a partition. Because it's code inside the container, there's no workaround, we need to fix the image and build another one. 

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

How reproducible:
Constant

Steps to Reproduce:
1. Use nvme device as journal for a ceph OSD
2. Use same nvme device as data/journal partition for an OSD. This forces us to not be able to specify the entire block device and we must create the partitions for the data and journal.
3. Deploy the container with partitons instead of the full block device. The docker image during the osd prepare phase fails because it expect a partition in a partition (nvme0n1p14 is the partition we use, it expects nvme0n1p14p1).

Actual results:
Unable to deploy the container as we expect to see full block device path

Expected results:
Should creater the container on the partitioned device.
Comment 3 Sébastien Han 2018-06-07 06:22:50 UTC 
Unfortunately, this is somewhat expected. However, if you pass the full device, ceph-disk (inside the container) will find the next available partition and will create it with the proper size (if enough space).

Can you try this?
Also, can we get the log from the container prepare sequence?

Thanks.
Comment 4 Mike Hackett 2018-06-18 14:15:43 UTC 
Closing this BZ as duplicate to: https://bugzilla.redhat.com/show_bug.cgi?id=1541415

*** This bug has been marked as a duplicate of bug 1541415 ***