Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem
# ansible-lint ends in
ERROR No module named 'ansible'
FATAL: ansible-lint requires a version of Ansible package >= 2.9, but none was found. Please install a compatible version using the same python interpreter. See https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-with-pip
I am not sure that installing anything with pip on satellite6 is a good idea
Version-Release number of selected component (if applicable):
Satellite 6.13.1
rhel 8.8
How reproducible:
100%
Steps to Reproduce:
1.run ansible-lint satellite6 6.13.1/rhel8
2.
3.
Actual results:
[root@snemeth-satellite6 ~]# ansible-lint
ERROR No module named 'ansible'
FATAL: ansible-lint requires a version of Ansible package >= 2.9, but none was found. Please install a compatible version using the same python interpreter. See https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#installing-ansible-with-pip
Expected results:
ansible-lint works and runs
Additional info:
installed packages
[root@snemeth-satellite6 ~]# dnf list installed | grep ansible
ansible-collection-redhat-satellite.noarch 3.9.0-2.el8sat @satellite-6.13-for-rhel-8-x86_64-rpms
ansible-collection-redhat-satellite_operations.noarch 1.3.0-2.el8sat @satellite-6.13-for-rhel-8-x86_64-rpms
ansible-core.x86_64 2.14.2-4.el8_8 @rhel-8-for-x86_64-appstream-rpms
ansible-lint.noarch 5.0.8-4.el8pc @satellite-6.12-for-rhel-8-x86_64-rpms
ansible-runner.noarch 2.2.1-3.el8sat @satellite-6.12-for-rhel-8-x86_64-rpms
ansible-test.x86_64 2.14.2-4.el8_8 @rhel-8-for-x86_64-appstream-rpms
ansiblerole-foreman_scap_client.noarch 0.2.0-2.el8sat @satellite-6.12-for-rhel-8-x86_64-rpms
ansiblerole-insights-client.noarch 1.7.1-2.el8sat @satellite-6.12-for-rhel-8-x86_64-rpms
python39-ansible-builder.noarch 1.0.1-4.el8pc @satellite-6.12-for-rhel-8-x86_64-rpms
python39-ansible-runner.noarch 2.2.1-3.el8sat @satellite-6.12-for-rhel-8-x86_64-rpms
python39-pulp-ansible.noarch 1:0.15.0-1.el8pc @satellite-6.13-for-rhel-8-x86_64-rpms
rubygem-foreman_ansible.noarch 10.4.0-1.el8sat @satellite-6.13-for-rhel-8-x86_64-rpms
rubygem-hammer_cli_foreman_ansible.noarch 0.4.0-2.el8sat @satellite-6.13-for-rhel-8-x86_64-rpms
rubygem-pulp_ansible_client.noarch 0.15.0-1.el8sat @satellite-6.13-for-rhel-8-x86_64-rpms
rubygem-smart_proxy_ansible.noarch 3.5.4-1.el8sat @satellite-6.12-for-rhel-8-x86_64-rpms
The ansible-lint that is shipped in Satellite is there as a requirement of the Ansible content type in Pulp and is not intended to be used directly.
Can you describe your use case for wanting to use ansible-lint on the Satellite?
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.