-
Notifications
You must be signed in to change notification settings - Fork 144
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
Offline usage - ERROR! 'collections' is not a valid attribute for a RoleMetadata #459
Comments
Hey @hearts1137, The gist is in late 2.9 they introduced the concept of collections and I think around 2.10 they forced collections. So we had to adjust to make our roles into collection supported roles. There were some other changes along the way with how Ansible handles linting and other things that caused us to make additional changes as well that don't work with older versions. Which is why the minimum supported version for the roles is 2.12. |
The ansible version 2.4.2.0 is the only one in our internal repo. How do you want me to check the Ansible CLI and Core version numbers? Sorry for the noob questions and thank you for the fast response. `(base) [root@server1 ~]# yum info ansible.noarch This system is not registered with an entitlement server. You can use subscription-manager to register. Installed Packages
I would have to spin up a RHEL 7.9 connected to the internet and download ansible 2.12 and all the related dependencies and upload to my offline server. I have a RedHat developer account for personal use and can add a subscription to a VOM on my local laptop. |
I'm reading that ansible 2.10 and later is not supported in RHEL7. I do have a rhel8 on my local network with redhat subscription access. Seems like RHEL8 has 2.15.3 in the repo `[root@server2 ~]# yum info ansible.noarch [root@server2 ~]# yum info ansible-core.x86_64 Is it possible to get these playbooks running on RHEL7 or do I need RHEL8? Our systems that are air-gapped are all RHEL7.9. |
hi @hearts1137 Ideally, it would be good to have a rhel8 (9 preferably) control node for ansible within your airgapped environment, this will future proof you for some time and make life alot easier. The playbooks should run on ansible 2.10, you will also need the jmespath library installed in order for the playbook to run. I hope that helps, please let us know if you have any further questions. uk-bolly |
hi @hearts1137 Just to follow up on this, we have removed the jmespath dependancy now. The rate ansible is changing it maybe more advisable to move to rhel9 system unless you are able to setup and install virtual environments with the relevant python version. Kindest regards uk-bolly |
Question
Pose question here.
Environment (please complete the following information):
ansible --version
ansible 2.4.2.0
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/user1/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /bin/ansible
python version = 2.7.5 (default, Oct 6 2023, 09:53:10) [GCC 4.8.5 20150623 (Red Hat 4.8.5-44)]
Looking to add this to our offline network. Kind of an ansible newbie but have run and modified existing playbooks previously. We have a plain RHEL 7.9 server with 'some STIGS's applied. Would like to give these playbooks a go but off to a bad start. Pretty sure I'm missing a ton of dependencies.
Error is: ERROR! 'collections' is not a valid attribute for a RoleMetadata
Any help would be appreciated
The text was updated successfully, but these errors were encountered: