.Adding a new Ceph Manager node will fail when using the Ansible `limit` option
Adding a new Ceph Manager to an existing storage cluster using the Ansible `limit` option, tries to copy the Ceph Manager's keyring without generating it first. This causes the Ansible playbook to fail and the new Ceph Manager node will not be configured properly. To workaround this issue, do not use the `limit` option while running the Ansible playbook. This will result in a 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):
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"]
Playbook must complete its run with successfully configuring new mgr
Though it was time consuming, Without using limit option, mgr could be added successfully.