Bug 1630977

Summary:	[RFE] integrate ceph-volume in ceph-container
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Christina Meno <gmeno>
Component:	Container	Assignee:	Sébastien Han <shan>
Status:	CLOSED ERRATA	QA Contact:	Ramakrishnan Periyasamy <rperiyas>
Severity:	high	Docs Contact:	Bara Ancincova <bancinco>
Priority:	high
Version:	3.2	CC:	anharris, ceph-eng-bugs, evelu, gabrioux, hnallurv, kdreyer, pasik, rperiyas, shan
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-ansible-3.2.0-0.1.beta5.el7cp Ubuntu: ceph-ansible_3.2.0~beta5-2redhat1	Doc Type:	Bug Fix
Doc Text:	Documented with BZ#1544836	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-03 20:19:30 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 Christina Meno 2018-09-19 15:54:49 UTC

Description of problem:
the internals of ceph-container are still dependent on ceph-disk


Expected results:
ceph-container should remove all references and implementations based on ceph-disk

Additional info:

Comment 3 Sébastien Han 2018-10-12 15:22:05 UTC

Present in https://github.com/ceph/ceph-ansible/releases/tag/v3.2.0beta5

Comment 8 Sébastien Han 2018-10-25 11:09:53 UTC

Yes, we should, the notable change is tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1544836

Comment 9 Ramakrishnan Periyasamy 2018-10-26 11:36:40 UTC

Installation of ceph-volume lvm based OSD scenarios in containers working for Filestore and Bluestore.

Verified in versions:
ansible-2.6.6-1.el7ae.noarch
ceph-ansible-3.2.0-0.1.beta9.el7cp.noarch
ceph version 12.2.8-22.el7cp (400dc4070c1d0a82f9afc8e574d780136dd28b0b) luminous (stable)

Comment 10 Ramakrishnan Periyasamy 2018-11-05 10:45:08 UTC

Moving this bug to verified

Comment 16 errata-xmlrpc 2019-01-03 20:19:30 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-2019:0021