Bug 1507943
Summary: | [Ansible]: lvm osd cluster installation fails when using custom cluster name | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Ramakrishnan Periyasamy <rperiyas> |
Component: | Ceph-Ansible | Assignee: | Sébastien Han <shan> |
Status: | CLOSED WONTFIX | QA Contact: | Ramakrishnan Periyasamy <rperiyas> |
Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | high | ||
Version: | 3.0 | CC: | adeza, anharris, aschoen, ceph-eng-bugs, flucifre, gmeno, hnallurv, kdreyer, nthomas, sankarshan, shan |
Target Milestone: | rc | ||
Target Release: | 3.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
.Adding LVM-based OSDs fail on clusters with other names than "ceph"
An attempt to install a new Ceph cluster or add OSDs by using the `osd_scenario: lvm` parameter fails on clusters that use other names than the default "ceph". To work around this problem on new clusters, use the default cluster name ("ceph").
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 23:06:15 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: | 1266828, 1459861, 1635924 | ||
Bug Blocks: | 1494421 |
Description
Ramakrishnan Periyasamy
2017-10-31 14:19:05 UTC
Not sure why this is a 3.0 bug? This is no longer a problem in ceph-ansible master which requires the latest tip of luminous, that has this PR https://github.com/ceph/ceph/pull/18593 https://marc.info/?l=ceph-devel&m=149702444111127&w=2 says that we will be heading in a direction that custom cluster names won't be included in upstream deployment tools, this thread includes some directions on how existing cluster might migrate away from such a setup. This work that has been done doesn't cherry-pick cleanly. I'm going to recommend that we include a release note that ceph-volume isn't supported for clusters that aren't named ceph and push this out to 3.1 as not a blocker (In reply to Gregory Meno from comment #4) > https://marc.info/?l=ceph-devel&m=149702444111127&w=2 says that we will be > heading in a direction that custom cluster names won't be included in > upstream deployment tools, this thread includes some directions on how > existing cluster might migrate away from such a setup. > > This work that has been done doesn't cherry-pick cleanly. I'm going to > recommend that we include a release note that ceph-volume isn't supported > for clusters that aren't named ceph and push this out to 3.1 as not a blocker @Federico, please let us know the product's decision on this. Not fixing this bug in 3.0 will impact the use case of adding an lvm based osd to an existing cluster with custom cluster name. such users will not be able to use lvm feature. As per comment https://bugzilla.redhat.com/show_bug.cgi?id=1507943#c3 it seems that the issue is solved in 3.1, also this https://bugzilla.redhat.com/show_bug.cgi?id=1507943#c4 suggests no fix should be attempted on 3.0. So nothing to do for ceph-ansible. custom cluster names -> wontfix |