Andrew Klychkov

@jnm27 ^ could you please do this?

@fourstepper thanks!

@fourstepper if it doesn't help, we could in addition add `serial: 1` to the playbook

@fourstepper thanks for the feedback!

yeah, as we can see in the provided traceback, everything seems to happen on the target machine: ``` The full traceback is: File "/tmp/ansible_community.mysql.mysql_user_payload_cquoa0hv/ansible_community.mysql.mysql_user_payload.zip/ansible_collections/community/mysql/plugins/modules/mysql_user.py", line 1066, in main File "/tmp/ansible_community.mysql.mysql_user_payload_cquoa0hv/ansible_community.mysql.mysql_user_payload.zip/ansible_collections/community/mysql/plugins/module_utils/mysql.py",...

@jnm27 I ran out of my ideas. The folks in IRC didn't have any ideas too. Anyway it doesn't seem to be problem of the code in this collection. Our...

@beckjkl hi, thanks for the information! And sorry for the late response, was busy with the `mysql_role` new module. (BTW if someone is interesting to see it, please review https://github.com/ansible-collections/community.mysql/pull/189)....

@beckjkl thanks for the feedback! > * ansible is not installed on these hosts and I won't install it. Ah, of course... I woke up feeling a bit underslept today:)...

@beckjkl so nothing has changed after the purging, right? looks like absolute magic to me as both the systems use same software... I have no ideas then why this happens....

> :( > > I am afraid it won't work as there is no protocol parameters in pymysql : > > https://github.com/PyMySQL/PyMySQL/blob/main/pymysql/connections.py#L167 > > I was also scratching my head...