Created attachment 1382318 [details] File contains contents ansible-playbook log Description of problem: Rolling update from 2.4 to 2.5 fails asking user to add mgrs Version-Release number of selected component (if applicable): ceph-ansible-3.0.16-1.el7cp.noarch How reproducible: Always Steps to Reproduce: 1. Configure RHCEPH 2.4 cluster 2. Update ceph-ansible 3. Run rolling update Actual results: TASK [fail if no mgr host is present in the inventory] fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Please add a mgr host to your inventory."} Expected results: ceph-ansible must not ask user to add mgrs while upgrading cluster to 2.5 Additional info:
Please add one of your mon as an mgr in your inventory file. The sooner you do this, the better it will be once you want to update to 3.0. Let me know how that goes. Thanks
Hi Sebastien, After adding a mgr in to the inventory, rolling update upgraded all mons and failed - TASK [ceph-mgr : install ceph-mgr package on RedHat or SUSE] task path: /usr/share/ceph-ansible/roles/ceph-mgr/tasks/pre_requisite.yml:2 fatal: [magna029]: FAILED! => {"changed": false, "failed": true, "msg": "No package matching 'ceph-mgr' found available, installed or updated", "rc": 126, "results": ["No package matching 'ceph-mgr' found available, installed or updated"]} Regards, Vasishta
Alright, I'll patch this differently then.
fixed in https://github.com/ceph/ceph-ansible/releases/tag/v3.0.18
Created attachment 1385208 [details] upgrade log
I've added a new required option to the invocation of rolling_upgrade "-e jewel_minor_update=true" please retest using this when you run the rolling_upgrade. I have added Doc text so this should get added to the upgrade guide. thank you
@Gregory, this doc change is specific to upgrades from 2.4 to 2.5 only. Right? It's better to explicitly mention it in the doc. Please let me know your thoughts.
I successfully upgraded from 2.4 to 2.5 after having fixed a couple of issues. Fixes will be in v3.0.20
Harish, I think you're right I have changed the doc text to reflect.
Hi all, sorry for that but I've released v3.0.21 which contains a patch I've forgotten to add in v3.0.20 for this BZ. Can you please take this information in consideration if you have already started your testing? Thanks!
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-2018:0340