Closed kurokobo closed 1 year ago
This seems to be caused by this commit on vsphere-automation-sdk-python
: https://github.com/vmware/vsphere-automation-sdk-python/commit/4b49fbbcf3169020966b9c4c44d8a5454cca7bec
This commit updated whl
s in the repository, and updated whl
s have updated dependencies.
My guess is:
awx-ee
tries to install community.vmware
community.vmware
has requirements.txt
that refer upstream https://github.com/vmware/vsphere-automation-sdk-python
requirements.txt
from all Collections and user-defined onehttps://github.com/vmware/vsphere-automation-sdk-python
and whl
s in the repository that updated few days ago by above commitOf course the latest vsphere-automation-sdk-python
should be supported, but as a temporary (and super dirty) workaround, we can pin the version of vsphere-automation-sdk-python
by following patch.
@kurokobo Removing community-vmware fixes the issue for me. So within there, the problem seems to be.
Instead of using temporary workaround, to support updated vsphere-automation-sdk-python
, there seems to be additional considerations:
vsphere-automation-sdk-python
requires pyopenssl==22.0.0
, but it is not compatible with ansible-runner
(that requires pyopenssl<20.0.0
). This should be fixed in ansible-runner.vsphere-automation-sdk-python
requires cryptography==36.0.0
, but awx-ee
requires cryptography==37.0.4
. This should be fixed in this awx-ee
repository.Can you please let me know how to apply the patch?
@mumohamm
@kurokobo FYI, cryptography
was fixed to this Version due to issue https://github.com/ansible/awx-ee/issues/134
@shanemcd will be happy to help whoever picks this issue up.
Fixed by #141
@shanemcd @relrod Thanks for working on this :)
Just to inform, daily builds seem to be failing since Sep. 29.
I have not looked into it in detail, but it seems to be taking an extremely long time to resolve dependencies by pip and is facing a 6 hour timeout.
https://github.com/ansible/awx-ee/actions
EDIT AFTER CASE CLOSED: The upstream
ansible-runner
image still needs to be fixed, but at this time as @shanemcd did in #141 addingansible-runner>=2.2.1
torequirements.txt
for Ansible Builder is the simplest workaround.