-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install some galaxy collections #14495
Comments
Same issue, was additionally effecting rebuilding an execution environment [ansible-build] with same error |
Same issue here... |
Yup, same issue as well. And we are running on We use the community collections a lot, so this breaks a lot of automations. |
Same issue on community.general with AWX-operator versions of both 22.6.0 and 21.10.1. |
Same here, version 23.0.0. Update to 23.2.0 dont have any effect. |
What ansible version is AWX or the Default Execution Environment using? Apparently there was a bug in ansible 2.13 that caused this issue, see the post on the ansible forum here: https://forum.ansible.com/t/unable-to-install-collection-from-new-galaxy/1238/4?u=alex |
I suspect the problem to be in the awx-ee:latest as it's the only component which his upgraded automatically. I'm currently running ansible 2.12.5
|
co-worker have update from ansible 2.12 to 2.13 inside EE and seems to have fixed here. |
@MatthieuLeMee yeah i kind of suspected that, i saw that the latest image was updated a few minutes ago. But i don't have time right now to try it out. I hope there will be a new release / tag soon that updates ansible in there. @lucasvivian great to hear! |
Updated the Control Plane Execution Environment to use the Still waiting for a new tag though so i can pin it to a version that fits to the AWX release. |
ansible --version[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Jun 20 2023, 11:53:23) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]. /usr/local/bin/ansible-galaxy -v collection install community.general[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version: 3.6.8 (default, Jun 20 2023, 11:53:23) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]. |
Same issues here on ansible 2.11.6: ansible-playbooks$ ansible-galaxy collection install -r ./requirements.yml Seems to be intermittent, bad server behind LoadBalancer? |
I know its been posted already but same issue: ansible [core 2.11.12] |
I was using the image as awx-ee:latest, still the problem persists for me. I even tried to pull the image every time when a job is triggered, still no luck. |
Worked for myself; ensure that you rebuild your kube's after changing your Control Plane EE to point at latest. Thanks. |
Okay after some investigating, in AWX operator version 2.5.0 (AWX version 22.6.0) there was a pod "awx-task-xxx" in a running state, this pod is in charge of the task execution. I checked this pods image an it says awx-ee:latest but I checked sha of the image and it was an older image. So I deleted this pod and it came back with the new awx-ee:latest image with sha256:19ade0cacf21. After the new awx-task pod creation, the problem is solved. (Because it used the new image).
NOTE: Because of the operator awx-task-xxx pod, the solution @al-lac mentioned didn't work because it never pulled the newer image. (Even though I configured all the execution environments to always pull) |
It has definately to do with the awx-ee version. FYI, I'm not using the awx-ee:latest anymore after there has been wrong commits in recent weeks and blocked our production platform. By default, a local AWX installation is dependent on a Customizing the EE image does work and needs this deployement config :
I will mark this issue as resolved. |
I just changed the "Pull" setting for the "Control Plane Execution Environment" from "Missing" to "Always", after which the issue went away. |
At least for me ansible-version returns: ansible [core 2.15.4] and I'm seeing the same issue. |
The Ansible team released a new Galaxy server. In case you are using an older version, there is a new url to use to get packages : https://old-galaxy.ansible.com/ Here is what to put in your ansible.cfg file :
|
upgrading was helpful, it works now ansible [core 2.12.10] |
According to [Unable to install some galaxy collections · Issue #14495 · ansible/awx · GitHub](ansible/awx#14495 (comment))
Please confirm the following
security@ansible.com
instead.)Bug Summary
I'm on minikube and AWX 21.8.0 for months without any problem. Since some hours, AWX cannot install some collections anymore from Ansible Galaxy platform.
After some investigation, it seems it has to do with a high number of publicated versions of collections. I did not change any configuration on AWX since months and i don't know why it stars to fail only today.
Some collections i tried (with versions count) :
I also tried to purge some filesystem use in minikube with
docker image prune -af
reclaiming 40GB on 82GB total to avoid filesystem being full but it doesn't seem related. VM and minikube has not been restarted since 10 months.In all my deployments, i'm using collections/requirements.yml file with :
AWX version
21.8.0
Select the relevant components
Installation method
minikube
Modifications
no
Ansible version
2.15.1
Operating system
CentOS Linux release 7.9.2009 (Core)
Web browser
No response
Steps to reproduce
Expected results
Big collections installing fine.
Actual results
Error in project update:
And full stacktrace is
Additional information
No response
The text was updated successfully, but these errors were encountered: