Bug 2156941

Summary:	Satellite operations doesn't install in an execution environment
Product:	Red Hat Satellite	Reporter:	Kevin Breit <kevin.breit>
Component:	Ansible Collection	Assignee:	Evgeni Golov <egolov>
Status:	CLOSED ERRATA	QA Contact:	Griffin Sullivan <gsulliva>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	egolov, ehelms, pcreech
Target Milestone:	6.13.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ansible-collection-redhat-satellite_operations-1.3.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:24:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin Breit 2022-12-29 18:17:46 UTC

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.

Comment 1 Evgeni Golov 2023-01-03 11:29:53 UTC

this has been fixed in https://github.com/theforeman/foreman-operations-collection/pull/105 but not pulled into a release yet

Comment 2 Kevin Breit 2023-01-03 14:37:38 UTC

Do you have guidance on when there will be a new release that includes the fix?

Comment 3 Evgeni Golov 2023-01-03 16:51:25 UTC

I can work on one in the next couple of days, it's been on the "yeah, should be done" list for a while now :)

Comment 4 Kevin Breit 2023-01-03 16:52:39 UTC

Excellent, thank you!

Comment 5 Evgeni Golov 2023-01-05 09:34:17 UTC

theforeman.operations is now updated (on galaxy)

redhat.satellite_operations is still todo

Comment 6 Evgeni Golov 2023-01-12 08:43:57 UTC

I've uploaded redhat.satellite_operations to console.redhat.com -- it's still pending review but should show up in the next couple of days.

Comment 7 Griffin Sullivan 2023-01-30 19:49:59 UTC

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.

Comment 10 errata-xmlrpc 2023-05-03 13:24:04 UTC

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