Bug 1885230 - Satellite Ansible Collection - Cannot use image name when creating an image with the image module
Summary: Satellite Ansible Collection - Cannot use image name when creating an image w...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Griffin Sullivan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-05 13:32 UTC by Luka Bac
Modified: 2022-10-28 18:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-28 18:01:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Luka Bac 2020-10-05 13:32:22 UTC
Description of problem:
In order to create images on compute_resources in Satellite with the redhat.satellite.image module, we require the UUID of the image to create.

Unfortunately, the UUID is not static, and changes any time the image is updated - however, the image name stays the same.

We would like to consume the image name instead of the UUID - failing that, we would require a facility to retreive the available images for a specific compute_resource.

Satellite provides a foreman API endpoint (that is also usable via `hammer compute_resource images`) https://satellite.server.com/api/compute_resources/:id/available_images that can get the mapping from a name to image uuid.

Example output from hammer:
-------------------------------------|--------------------------
UUID                                 | NAME                     
-------------------------------------|--------------------------
562117ed-927e-413a-9d8f-17733095c52a | RHEL8-cloudinit
562117ed-927e-413a-9d8f-fece6ca614be | RHEL7-cloudinit
[...]

Version-Release number of selected component (if applicable): 1.3.0


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Brad Buckingham 2022-09-02 20:25:18 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 2 Brad Buckingham 2022-09-02 20:31:26 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 3 Brad Buckingham 2022-10-28 18:01:59 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


Note You need to log in before you can comment on or make changes to this bug.