Closed adpavlov closed 1 year ago
There is an issue in the community.vmware collection.
I can confirm by removing that one collection from requirements.yml, the build completes successfully.
Try pinning a specific version of that collection.
I've tried pinning the last 10 versions of community.vmware. I can't build an EE with community.vmware.
I notice it pulls the current vsphere-automation-sdk when it builds. Maybe there is a breaking change there.
Cloning https://github.com/vmware/vsphere-automation-sdk-python.git to /tmp/pip-req-build-tj5f8k69
Running command git clone --filter=blob:none --quiet https://github.com/vmware/vsphere-automation-sdk-python.git /tmp/pip-req-build-tj5f8k69
Resolved https://github.com/vmware/vsphere-automation-sdk-python.git to commit a5ef74d9d91d0bc292a07ae1bb8460361b2d67e0
Indeed the issue is because of recent changes in vsphere-automation-sdk
. There is an issue opened https://github.com/vmware/vsphere-automation-sdk-python/issues/339
I think this seems to not be an issue anymore (the ee is building fine lately, for me locally and on the daily builds). I think the issue might have worked itself out?
@adpavlov Can this be closed now?
Closing.
I am building single image for both control plane EE and actual worker EE based on
quay.io/ansible/awx-ee:latest
.Since some recent time build is not able to finish at all because of same issue that described in this question
Both requirements.txt and requirements.yml wasn't changed. Also it's not quite clear based on what
quay.io/ansible/awx-ee:latest
is built, because it's updated quite frequently and not following this awx-ee project commits.