Bug 2100420 - [RFE] Support Satellite registration in ovirt.repositories role with username/password
Summary: [RFE] Support Satellite registration in ovirt.repositories role with username...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-ansible-collection
Classification: oVirt
Component: repositories
Version: 2.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.5.2
: 2.2.0
Assignee: Martin Necas
QA Contact: Petr Kubica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-23 10:17 UTC by Petr Kubica
Modified: 2022-08-30 08:47 UTC (History)
2 users (show)

Fixed In Version: ovirt-ansible-collection-2.2.0
Clone Of:
Environment:
Last Closed: 2022-08-30 08:47:42 UTC
oVirt Team: Infra
Embargoed:
mperina: ovirt-4.5+
pm-rhel: planning_ack?
pm-rhel: devel_ack?
gdeolive: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-ansible-collection pull 483 0 None Merged role: repositories: Add rhsm_environment and FIPS fix 2022-06-23 13:46:31 UTC
Red Hat Issue Tracker RHV-46491 0 None None None 2022-06-23 10:24:02 UTC

Description Petr Kubica 2022-06-23 10:17:39 UTC 
Description of problem:
Currently ovirt.repositories role supports only registering a host with an activation key and org_id.
It should be also possible to just use ca_rpm of the Satellite with credentials and specifying pool ids for the registration as in standard subscription-manager registration to cdn.

It is also necessary to allow specifying environment during the registration process because if Satellite has more than one subscription-manager will interactively ask for it.
Comment 1 Petr Kubica 2022-08-11 09:19:13 UTC 
Verified in ovirt-ansible-collection-2.2.1-1.el8ev.noarch
Comment 2 Sandro Bonazzola 2022-08-30 08:47:42 UTC 
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.