Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1663866

Summary: [RFE] Add an option --rex-interface in bootstrap.py
Product: Red Hat Satellite Reporter: Neha Samant <nsamant>
Component: BootstrapAssignee: Rich Jerrido <rjerrido>
Status: CLOSED WONTFIX QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: alolivei, bkearney, ehelms, inecas, lorand-frigyes.kelemen, nsamant, nshaik, smane, sshtein
Target Milestone: UnspecifiedKeywords: FutureFeature, 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: 2020-02-03 16:30:34 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 Neha Samant 2019-01-07 09:02:02 UTC
Description of problem:
If we are trying to register a new system to satellite using bootstrap.py script, When the system is getting registered the network interface is not getting reported correctly.

We have created a bond interface and wants to get it reported during the registration of client.
Below is network configuration

Bond0 with 2 slaves eth0 and eth1, Also there is VLAN.

We to use Bond0 as primary remote execution interface.

We provided the --ip as the option, but with this the eth1 interface is taken as primary interface.
This always defaults to eth0 (probably interfaces are sorted before the Host is created). We need to add an option --rex-interface in bootstrap.py to allow configuring the interface of choice for REX.


Version-Release number of selected component (if applicable):
Red Hat Satellite 6.3

How reproducible:

A workaround is to do another API call again to change the REX option to the interface of choice after the Host is created.


Actual results:
When provided the --ip as the option, but with this the eth1 interface is taken as primary interface.

Expected results:


Additional info:

Comment 6 Bryan Kearney 2020-01-15 21:01:13 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 7 lokeleme 2020-01-27 11:06:47 UTC
Dear Red Hat Support,

Our env contains ~1000 machines registered to Satellite. We can reach the machines via a secondary management interface, which needs to be the REX interface.
We used a custom script to adjust all machines with 2 interfaces to set the secondary interface as REX interface.

However now we have a number of machines where where the primary interface should be the rex interface. So we need to manually "revert back" these machines after we run the workaround script.
This process needs to be done after every batch machine registration of course.

We are really awaiting this feature, as we could set the REX interface during registration.

Please keep working on the bug!

Comment 8 Bryan Kearney 2020-02-03 16:30:34 UTC
Thank you for your interest in Satellite 6. 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, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.