.Adding a new Ceph Manager node will no longer fail when using the Ansible `limit` option
Previously, adding a new Ceph Manager to an existing storage cluster when using the `limit` option would fail the Ansible playbook. With this release, you can now use the `limit` option when adding a new Ceph Manager and the newly generated keyring to be copied successfully.
Created attachment 1404942[details]
File contains contents of ansible-playbook log
Description of problem:
After upgrading containerized cluster from 3.0 to 3.0.z1, tried to add new mgr with --limit option. ansible-playbook failed trying to copy new mgr's keyring without generating
Version-Release number of selected component (if applicable):
ceph-ansible-3.0.27-1.el7cp.noarch
How reproducible:
Always (1/1)
Steps to Reproduce:
1. Configure containerized cluster.
2. Add new mgr with limit option to limit configuration to mgrs while running playbook.
Actual results: (magna035 had existing mgr, new mgr was planned to be configured on magna036)
TASK [ceph-mgr : copy mgr key to /var/lib/ceph/mgr/ondu-magna035/keyring] *************************
"stderr": "cp: cannot stat ‘/etc/ceph/ondu.mgr.magna036.keyring’: No such file or directory", "stderr_lines": ["cp: cannot stat ‘/etc/ceph/ondu.mgr.magna036.keyring’: No such file or directory"]
Expected results:
Playbook must complete its run with successfully configuring new mgr
Additional info:
Though it was time consuming, Without using limit option, mgr could be added successfully.
Comment 3Giridhar Ramaraju
2019-08-05 13:11:35 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.
Regards,
Giri
Comment 4Giridhar Ramaraju
2019-08-05 13:12:33 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate.
Regards,
Giri
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:4353
Created attachment 1404942 [details] File contains contents of ansible-playbook log Description of problem: After upgrading containerized cluster from 3.0 to 3.0.z1, tried to add new mgr with --limit option. ansible-playbook failed trying to copy new mgr's keyring without generating Version-Release number of selected component (if applicable): ceph-ansible-3.0.27-1.el7cp.noarch How reproducible: Always (1/1) Steps to Reproduce: 1. Configure containerized cluster. 2. Add new mgr with limit option to limit configuration to mgrs while running playbook. Actual results: (magna035 had existing mgr, new mgr was planned to be configured on magna036) TASK [ceph-mgr : copy mgr key to /var/lib/ceph/mgr/ondu-magna035/keyring] ************************* "stderr": "cp: cannot stat ‘/etc/ceph/ondu.mgr.magna036.keyring’: No such file or directory", "stderr_lines": ["cp: cannot stat ‘/etc/ceph/ondu.mgr.magna036.keyring’: No such file or directory"] Expected results: Playbook must complete its run with successfully configuring new mgr Additional info: Though it was time consuming, Without using limit option, mgr could be added successfully.