search

IBM / ansible-for-i

the tool is to provide several customized modules for Ansible to manage IBM i systems.
GNU General Public License v3.0
55 stars 51 forks source link

Using ibm.power_ibmi.ibmi_copy module results in a warning message #146

Closed krka01 closed 6 months ago

krka01 commented 1 year ago

Environment: ibm.power_ibmi collection version 1.9.0 runing on ansible [core 2.12.6]

Using the ibm.power_ibmi.ibmi_copy module results in the following warning:

[DEPRECATION WARNING]: The '_remote_checksum()' method is deprecated. The plugin author should update the code to use '_execute_remote_stat()' instead. This feature will be removed in version 2.16. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

krka01 commented 9 months ago

Is there any work ongoing with this issue?

The ibm.power_ibmi.ibmi_copy module are using the '_remote_checksum()' method and the method will be removed in ansible core version 2.16

ansible core version 2.16 were released 06 Nov 2023 and are considered the current version Ref: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html

I was hoping this should been fixed in the new power ibm i collection 1.9.2 that were released a few days ago.

robgjertsen1 commented 9 months ago

I'll keep this in mind with next drop after 2.0.0 and see if I can fix it there. I've had to focus on getting collection up to ansible core 2.14 and 2.15 and ansible lint production mode code clean-up for continued Redhat collection certification with release of 2.0.0. And there is still more to do with ansible lint code clean up for follow on release to 2.0.0.

hsjodin-ibm commented 8 months ago

Hi i have got a new mac and a got ansible 2.16.2 installd i cant find how to go back to 2.15... and now me ibm_script not working FAILED! => {"changed": false, "delta": "", "job_log": [], "rc": 255, "stderr": "'ActionModule' object has no attribute '_remote_checksum'", "stderr_lines": "", "stdout": "", "stdout_lines": ""}. please urgent fix needed or workaround

robgjertsen1 commented 8 months ago

You'll need to roll back to 2.15 for now. Unfortunately I don't use a mac, so can't help in that area. Easiest way around is probably to create a python virtual environment and use pip to install an older version of ansible in that environment.

hsjodin-ibm commented 8 months ago

Okay, tanks. Do you have a ETA on when it can work in 2.16

robgjertsen1 commented 8 months ago

Hopefully by March / April time frame.

robgjertsen1 commented 6 months ago

Fixed with 2.0.1 release.