Bug 1789091

Summary:	[ceph-ansible] : FS to BS migration - journal argument appended while configuring bluestore
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vasishta <vashastr>
Component:	Ceph-Ansible	Assignee:	Guillaume Abrioux <gabrioux>
Status:	CLOSED ERRATA	QA Contact:	Vasishta <vashastr>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	aschoen, ceph-eng-bugs, gmeno, nthomas, tchandra, tserlin, ykaul
Target Milestone:	rc	Keywords:	TestBlocker
Target Release:	4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-ansible-4.0.7-1.el8cp, ceph-ansible-4.0.7-1.el7cp	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-31 12:48:38 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 Vasishta 2020-01-08 17:38:17 UTC

Description of problem:
While migrating from filestore to bluestore, 'journal' argument was appended with ceph-volume command during bluestore OSD creation 

Version-Release number of selected component (if applicable):
ceph-ansible-4.0.6-1

Steps to Reproduce:
1. Configure 3.x cluster with filestore OSDs (tried scenario in which usr creates lvm and sets the variables lvm_volumes
2. Upgrade cluster to 4.x
3. run fs to bs migration playbook

Actual results:
Obeserved this command in ceph-ansible log     
 ceph
- lvm
- prepare
- --bluestore
- --data
- data_vg/data_lv2
- --journal
- j_vg/j2

Expected results:
relevant command must be generated

Comment 4 Vasishta 2020-01-13 09:17:08 UTC

Working fine with ceph-ansible-4.0.8-1.el7cp.noarch

ceph
  - lvm
  - prepare
  - --bluestore
  - --data
  - data_vg/data_lv1
  - --dmcrypt

Moving to VERIFIED state.

Comment 6 errata-xmlrpc 2020-01-31 12:48:38 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-2020:0312