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: NEW
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: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-05 13:32 UTC by Luka Bac
Modified: 2021-06-07 12:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


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:


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