-
Notifications
You must be signed in to change notification settings - Fork 33
OPSEXP-3019 Bump python to 3.11 and ansible to 2.17 #1031
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
Conversation
40468a7 to
720cdb9
Compare
bd5482b to
b43f5be
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so I got the idea to remove this since logs were getting spammed with:
WARNING Another version of 'alfresco.acs' 1.0.0 was found installed in /home/runner/.local/share/virtualenvs/alfresco-ansible-deployment-cebUtTOi/lib/python3.11/dist-packages/ansible_collections, only the first one will be used, 1.0.0 (/home/runner/.ansible/collections/ansible_collections).
WARNING Another version of 'alfresco.acs' 1.0.0 was found installed in /home/runner/.local/share/virtualenvs/alfresco-ansible-deployment-cebUtTOi/lib/python3.11/site-packages/ansible_collections, only the first one will be used, 1.0.0 (/home/runner/.ansible/collections/ansible_collections).
WARNING Another version of 'alfresco.acs' 1.0.0 was found installed in /home/runner/.local/share/virtualenvs/alfresco-ansible-deployment-cebUtTOi/lib/python3/dist-packages/ansible_collections, only the first one will be used, 1.0.0 (/home/runner/.ansible/collections/ansible_collections).
WARNING Another version of 'alfresco.acs' 1.0.0 was found installed in /home/runner/.local/share/virtualenvs/alfresco-ansible-deployment-cebUtTOi/local/lib/python3.11/dist-packages/ansible_collections, only the first one will be used, 1.0.0 (/home/runner/.ansible/collections/ansible_collections).
which was getting worse when molecule was triggering a retry like in https://github.com/Alfresco/alfresco-ansible-deployment/actions/runs/13240172999/job/36956143762#step:3:3708
once I dropped this, then all the single role galaxy metadata was starting to trigger validation issues due to missing namespace, so I decided to revamp all of them which was anyway required.
at this point I am not sure if the root galaxy.yml was just inhibiting all the role galaxy.yml and I think it's a feature (because in that case roles are part of the collection)
I am not sure what to do, but maybe given we are not currently publishing anything we can leave it as it is now.
OPSEXP-3019
to be merged after release