Bug 1841048

Summary:

[RFE] Ability to specify REX interface upon registration

Product:

Red Hat Satellite

Reporter:

Kenny Tordeurs <ktordeur>

Component:

Registration

Assignee:

satellite6-bugs <satellite6-bugs>

Status:

CLOSED ERRATA

QA Contact:

Stephen Wadeley <swadeley>

Severity:

high

Docs Contact:

Priority:

high

Version:

6.7.0

CC:

lstejska, sokeeffe

Target Milestone:

6.9.0

Keywords:

FutureFeature, PrioBumpPM, Triaged

Target Release:

Unused

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2021-04-21 13:14:56 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:

Attachments:

Description	Flags
screenshot from 6.7	none

Description Kenny Tordeurs 2020-05-28 08:46:58 UTC

1. Proposed title of this feature request
Ability to specify REX interface upon registration

2. What is the nature and description of the request?
The possibility to set the REX interface upon registration of the host in case multiple interfaces exist to avoid the need of editing the rex interface later on.

3. Why does the customer need this? (List the business requirements
here) This allows setting the desired REX interface upon registration removing the need to modify it later on.

4. How would the customer like to achieve this? (List the functional
requirements here)
Be able to specify the rex interface (maybe some customer sub-man fact that could be picked up by Satellite)
bootstrap.py (https://bugzilla.redhat.com/show_bug.cgi?id=1663866 closed/wontfix)

5. For each functional requirement listed in question 5, specify how Red
Hat and the customer can test to confirm the requirement is successfully
implemented.
Specify the rex interface and verify it's set for the host in Satellite


6. Is there already an existing RFE upstream or in Red Hat bugzilla?
No

7. Does the customer have any specific timeline dependencies?
No

Comment 1 Sean O'Keeffe 2020-06-05 13:17:47 UTC

Could you be a little more explicit as to what extra you are looking for that we do not already offer? See my attached screenshot, you'll see you can select a Remote Execution interface when you create a host.

Comment 2 Sean O'Keeffe 2020-06-05 13:18:25 UTC

Created attachment 1695426 [details]
screenshot from 6.7

Comment 3 Kenny Tordeurs 2020-06-05 13:27:57 UTC

When I have a system that has multiple interfaces and was not provisioned by Satellite, I register the system via subscription-manager or bootstrap.py and I want to specify the REX interface upon registration.
After registration the wrong REX interface gets chosen and requires a manual edit of the REX interface to choose the desired interface.

Comment 4 Sean O'Keeffe 2020-06-05 13:33:02 UTC

Thanks, so really you are asking to re-open https://bugzilla.redhat.com/show_bug.cgi?id=1663866? Or am I missing something and there is a difference between these 2 RFEs?

Comment 5 Kenny Tordeurs 2020-06-05 13:48:46 UTC

Not a lot no,  https://bugzilla.redhat.com/show_bug.cgi?id=1663866 was focused on bootstrap while it would be nice to have it under subscription-manager but in the end it's the same result.

Comment 6 Sean O'Keeffe 2020-06-05 14:00:43 UTC

This should work off a subscription-manager fact, just like the foreman_location fact (https://access.redhat.com/discussions/1528223#comment-1004321)

Comment 7 Marek Hulan 2021-01-25 07:25:18 UTC

Does the new registration flow address this? Note the form allows to specify REX identifier. Also the curl can contain a parameter with the identifier. The REX flag is then set accordingly.

Comment 8 Kenny Tordeurs 2021-01-25 08:35:38 UTC

@mhulan

Indeed the new registration flow provides the requirements mentioned in this bz.
We can set if for that release.

Comment 9 Leos Stejskal 2021-02-05 13:16:11 UTC

> Indeed the new registration flow provides the requirements mentioned in this bz.

Moving to On_QA then.

Comment 14 errata-xmlrpc 2021-04-21 13:14:56 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 (Moderate: Satellite 6.9 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-2021:1313