Description of problem: When bug 1787569 was fixed we seem to have forgotten /usr/share/ceph-ansible/infrastructure-playbooks/README.md Version-Release number of selected component (if applicable): ceph-ansible-4.0.14-1.el7cp.noarch How reproducible: always Steps to Reproduce: 1. install ceph-ansible-4.0.14-1.el7cp.noarch 2. read and follow steps in /usr/share/ceph-ansible/infrastructure-playbooks/README.md Actual results: a. cat /usr/share/ceph-ansible/infrastructure-playbooks/README.md Infrastructure playbooks ======================== This directory contains a variety of playbooks that can be used independently of the Ceph roles we have. They aim to perform infrastructure related tasks that would help use managing a Ceph cluster or performing certain operational tasks. To use them, **you must move them to ceph-ansible's root directory**, then run using `ansible-playbook <playbook>`. b. cp /usr/share/ceph-ansible/infrastructure-playbooks/rolling_update.yml /usr/share/ceph-ansible/rolling_update.yml c. cd /usr/share/ceph-ansible/ d. ansible-playbook rolling_update.yml FAILS Expected results: consistency with bug 1787569 and correct docs, some (few but they exist) of my customers are in a completely disconnected environment, so it's important to them that the docs on disk are up to date. Additional info: as per bug 1787569, change the README.md to NOT tell the user to copy those playbooks anywhere but run them as follows cd /usr/share/ceph-ansible/ ansible-playbook infrastructure-playbooks/rolling_update.yml
$ rpm -qa|grep ceph-ansible ceph-ansible-4.0.18-1.el7cp.noarch $ tail -n 1 /usr/share/ceph-ansible/infrastructure-playbooks/README.md To use them, run `ansible-playbook infrastructure-playbooks/<playbook>`. Moving to VERIFIED state. Regards, Vasishta Shastry 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/RHSA-2020:2231