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