Created attachment 1500263 [details] ansible-playbook full log Description of problem: When upgrade from ceph 3.1 to 3.2, rolling_update.yml failed when using ansible 2.6. TASK [ceph-config : generate ceph configuration file: ceph.conf] *************************************************************************************** Thursday 01 November 2018 16:47:26 +0000 (0:00:00.264) 0:06:20.515 ***** fatal: [c05-h33-6018r]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (copy) module: original_basename Supported parameters include: _original_basename, attributes, backup, checksum, content, delimiter, dest, directory_mode, follow, force, group, local_follow, mode, owner, regexp, remote_src, selevel, serole, setype, seuser, src, unsafe_writes, validate"} Version-Release number of selected component (if applicable): 1. Ceph version 3.1 (12.2.5-42.el7cp) 2. Ansible: 2.6.6-1.el7ae 3. Ceph-ansible: 3.2.0-0.1.rc1.el7cp How to reproduce: Deploy cluster with ceph version 3.1 running, then perform upgrade to ceph 3.2 Steps to Reproduce: 1. Cluster running ceph-ansible 3.1(3.1.5-1.el7cp) and ansible 2.4 (2.4.2.0-2.el7) 2. Upgrade ceph-asible to 3.2 (3.2.0-0.1.rc1.el7cp) and ansible 2.6 (2.6.6-1.el7ae) 3. Perform upgrade to ceph 3.1 using ansible-playbook: # ansible-playbook rolling_update.yml Actual results: Failed with error below: TASK [ceph-config : generate ceph configuration file: ceph.conf] *************************************************************************************** Thursday 01 November 2018 16:47:26 +0000 (0:00:00.264) 0:06:20.515 ***** fatal: [c05-h33-6018r]: FAILED! => {"changed": false, "msg": "Unsupported parameters for (copy) module: original_basename Supported parameters include: _original_basename, attributes, backup, checksum, content, delimiter, dest, directory_mode, follow, force, group, local_follow, mode, owner, regexp, remote_src, selevel, serole, setype, seuser, src, unsafe_writes, validate"} Expected results: Upgrade should work without any issue.
This is a blocker for upgrade test
You shouldn't have this issue if you use ansible 2.6. Can we access the env to further debug? THanks
Tiffany, you are not running the right ceph-ansible version. You have 2 versions on your system, one in /root/ceph-ansible which is incorrect (looks like a 3.1.X) and one in /usr/share/ceph-ansible which is definitely 3.2, the later is the one you should use. I'm closing this as not a bug.