Bug 1792227 - [ceph-ansible] : FS to to BS migration - conversion of lvm OSDs failing saying physical volume not initialised
Summary: [ceph-ansible] : FS to to BS migration - conversion of lvm OSDs failing sayin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 4.0
Assignee: Dimitri Savineau
QA Contact: Ameena Suhani S H
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-17 10:33 UTC by Vasishta
Modified: 2020-01-31 12:49 UTC (History)
9 users (show)

Fixed In Version: ceph-ansible-4.0.11-1.el8cp, ceph-ansible-4.0.11-1.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-31 12:48:44 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 4966 0 None closed filestore-to-bluestore: --destroy with raw devices 2020-09-28 15:01:50 UTC
Red Hat Product Errata RHBA-2020:0312 0 None None None 2020-01-31 12:48:59 UTC

Description Vasishta 2020-01-17 10:33:52 UTC
Description of problem:
Filestore to bluestore migration failing saying  physical volume not initialized when filestore OSDs were created in lvm scenario

Version-Release number of selected component (if applicable):
ceph-ansible-4.0.10-1.el7cp.noarch

How reproducible:
Always (2/2)

Steps to Reproduce:
1. Configure 3.x cluster with filestore lvm based OSDs
2. Upgrade cluster to 4.x 
3. Run filestore_to_bluestore.yml

Actual results:
 Running command: /usr/sbin/vgcreate -s 1G --force --yes ceph-bdc67a84-894a-4687-b43f-bcd76317580a /dev/sdd
     stderr: Physical volume '/dev/sdd' is already in volume group 'ceph-b7801d50-e827-4857-95ec-3291ad6f0151'
      Unable to add physical volume '/dev/sdd' to volume group 'ceph-b7801d50-e827-4857-95ec-3291ad6f0151'
      /dev/sdd: physical volume not initialized.


Expected results:
Bluestore OSDs must be configured without any error

Additional info:

Comment 10 errata-xmlrpc 2020-01-31 12:48:44 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


Note You need to log in before you can comment on or make changes to this bug.