Bug 1668478
Summary: | Failed to Purge Cluster | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | acalhoun |
Component: | Ceph-Ansible | Assignee: | Dimitri Savineau <dsavinea> |
Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
Severity: | low | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | low | ||
Version: | 3.2 | CC: | agunn, anharris, aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, edonnell, gmeno, nthomas, sankarshan, tchandra, tserlin |
Target Milestone: | rc | ||
Target Release: | 3.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-ansible-3.2.15-1.el7cp Ubuntu: ceph-ansible_3.2.15-2redhat1 | Doc Type: | Bug Fix |
Doc Text: |
.It is now possible to use Ansible playbooks without copying them to the root `ceph-ansible` directory
Due to the missing `library` variable in the Ansible configuration, the custom Ansible modules were not detected when executed playbooks were present in the `infrastructure-playbooks` directory. Consequently, it was not possible to run the infrastructure playbooks without copying them into the root `ceph-ansible` directory. This update adds the `library` variable to the Ansible configuration. As a result, it is possible to use playbooks in the `infrastructure-playbooks` without copying them, for example:
----
# ansible-playbook infrastructure-playbooks/purge-cluster.yml -i inventory_file
----
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-21 15:10:24 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: | |||
Bug Blocks: | 1726135 |
Description
acalhoun
2019-01-22 20:33:05 UTC
Hi Dimitri, do you think this bug fix should be included in the release notes for 3.3/would the customer be interested to know about this fix? If so, could you fill in the Doc Text field of the BZ? 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/RHSA-2019:2538 |