Collection fails with python 3.8 about azure

[Fred-sun]

Yes, I am sorry to cause you trouble, I will advance the problem resolution as soon as possible, thank you！

[jschwanz]

+1 We've hit this with the Azure DevOps Ubuntu 20.04 agent

ansible 2.9.6
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/vsts/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.8.2 (default, Jul 16 2020, 14:00:26) [GCC 9.3.0]

[fghamsary]

Same problem :'(

[Fred-sun]

@uda Yes, I ignored this, I will update the ansible_collection dependency package as soon as possible to close this issue! Thank you!

[uda]

How is this still a medium_priority issue? Python 3.6 is already in security-fixes phase, 3.7 breaks on this as well.

@Fred-sun, this has already been solved, the solution is upgrading azure API dependencies, not rewrite all ansible modules.

[Fred-sun]

@UnwashedMeme This is because the time module in python3.8 does not have a clock attribute. I will report this problem to the development team due to incompatible versions. You can use python3.6 for the time being. Thank you!

[pkoziol]

Using python 3.6 is problematic for Mac users using homebrew (or simply impossible? I haven't figured out it yet). homebrew has packages for ansible 2.9.9 and ansible 2.8.12. Both of them have explicit dependency on [email protected] 😞

[Fred-sun]

@uda Because it is not caused by ansible-collection, but other reasons, so mark it as medium_priority. Which dependency package needs to be upgraded? Can you list them? Thank you!。

[uda]

@Fred-sun from the original issuer's words:

This was fixed 6 months ago in Azure/azure-cli#11239 in azure-cli-core = ">=2.0.77" but this collection wants azure-cli-core = "==2.0.35"

And I mentioned it in ansible's issue: ansible/ansible#67473 (comment)
And you commented on that issue in June, requesting to close it due to this issue having been reported ansible/ansible#67473 (comment)