Bug 1773489
Summary: | [ceph-ansible] - configuration of cephFS is failing when '--limit mdss' is used with site-docker.yml | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vasishta <vashastr> |
Component: | Ceph-Ansible | Assignee: | Guillaume Abrioux <gabrioux> |
Status: | CLOSED ERRATA | QA Contact: | Ameena Suhani S H <amsyedha> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0 | CC: | amsyedha, aschoen, ceph-eng-bugs, gabrioux, gmeno, nthomas, tserlin, ykaul |
Target Milestone: | rc | ||
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-ansible-4.0.6-1.el8cp, ceph-ansible-4.0.6-1.el7cp | Doc Type: | Known Issue |
Doc Text: |
Cause:
ceph-ansible skips certain steps when '--limit' is used and tries to execute 'ceph' commands on host instead of inside a container
Consequence:
ceph-ansible fails to configure cephfs when you try to configure cephfs with an already existing cluster with 'limit mdss' while running site-docker.yml
Workaround (if any):
Run site-docker.yml without using ''--limit mdss''
Result:
ceph-ansible will run ceph commands inside the container, thus cephfs gets configured without any failure.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-01-31 12:48:10 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
2019-11-18 09:45:38 UTC
Hi, [1] has fixes, verified regression for configuration from scratch also It would be nice if we can backport to stable-4.0, need to release-note otherwise. https://github.com/ceph/ceph-ansible/pull/4747 Regards, Vasishta QE, Ceph 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 |