Bug 1582181 - LVM lvcreate fails if the disk already has a GPT header
Summary: LVM lvcreate fails if the disk already has a GPT header
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 3.1
Assignee: Sébastien Han
QA Contact: Parikshith
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-24 12:47 UTC by Guillaume Abrioux
Modified: 2019-10-24 05:38 UTC (History)
10 users (show)

Fixed In Version: RHEL: ceph-ansible-3.1.0-0.1.rc4.el7cp Ubuntu: ceph-ansible_3.1.0~rc4-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-26 18:21:13 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 2593 0 None None None 2018-05-24 13:18:45 UTC
Github ceph ceph-ansible pull 2633 0 None None None 2018-05-24 13:19:19 UTC
Github ceph ceph-ansible pull 2634 0 None None None 2018-05-24 13:19:34 UTC
Red Hat Product Errata RHBA-2018:2819 0 None None None 2018-09-26 18:22:05 UTC

Description Guillaume Abrioux 2018-05-24 12:47:13 UTC 
Description of problem:
The LVM lvcreate fails if the disk already has a GPT header.
We create GPT header regardless of OSD scenario. 

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


How reproducible:
Deploy a cluster with at least one osd lvm scenario.


Actual results:
LVM lvcreate fails

Expected results:
It should skip header creation for lvm scenario.
Comment 8 errata-xmlrpc 2018-09-26 18:21:13 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-2018:2819
Note You need to log in before you can comment on or make changes to this bug.