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.
DescriptionJessica Richards
2022-11-15 00:00:57 UTC
1. Proposed title of this feature request
[RFE] Create an allow list for NIC names
3. What is the nature and description of the request?
Rather than using a deny list for NIC names, Satellite should give customers the ability to use an allow list for NIC names.
4. Why does the customer need this? (List the business requirements here)
This will give customers the ability to allow only the NIC names they use in their environment (eg eth, br, etc), while excluding automatically generated NICs with surprising names.
5. How would the customer like to achieve this? (List the functional requirements here)
Turn the option Administer > Settings > Provisioning > "Ignore interfaces with matching identifier" into a switch widget with two options:
"Ignore interfaces with matching identifier"
"Allow interfaces with matching identifier"
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- populate both the ignore and allow and deny lists
- enable "Ignore interfaces with matching identifier"
- run "foreman-rake interfaces:clean" and restart the satellite services
- update facts to satellite from a registered host
- use hammer to list the interfaces for that registered host, and verify that only the expected interfaces appear there
- enable "Allow interfaces with matching identifier"
- run "foreman-rake interfaces:clean" and restart the satellite services
- update facts to satellite from a registered host
- use hammer to list the interfaces for that registered host, and verify that only the expected interfaces appear there
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
no
8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
no
9. Is the sales team involved in this request and do they have any additional input?
no
10. List any affected packages or components.
foreman, puma, candlepin
11. Would the customer be able to assist in testing this functionality if implemented?
no
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.
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.