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:
This is about the satellite-operations collection so the component may need to be reassigned, but this was the closest match I saw. When I build an execution environment and the operations collection is included, I am receiving this error:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/ansible/collections/ansible_collections/redhat/satellite_operations/../requirements.txt'
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/ansible/collections/ansible_collections/redhat/satellite_operations/../requirements.txt'
Expected results:
It should find the requirements.txt file.
Additional info:
I believe this is due to https://github.com/RedHatSatellite/satellite-operations-collection/blob/b120a2fa5c5f540f0774ec5a391ed5adde4e9a47/meta/execution-environment.yml#L8 referencing `../` instead of just `requirements.txt`. However, this change is old and probably would have been a problem before now.
Verified in 6.13 snap 8
The changes to satellite_operations collection are present in Satellite and I am able to create an execution environment with the redhat.satellite_operations collection included.
1. Set up VM with podman and ansible-builder
2. Create a requirements.yml that includes the redhat.satellite_collection (also need to specify an ansible.cfg that is able to access automation hub)
3. Create an execution-environment.yml that references the requirements file from step 2
4. # ansible-builder build
Results:
Execution environment is created successfully.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.13 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:2097