Bug 2100942

Summary: RFE: firewall-system-role: add ability to add interface to zone by PCI device ID
Product: Red Hat Enterprise Linux 9 Reporter: Brennan Paciorek <bpaciore>
Component: rhel-system-rolesAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Jakub Haruda <jharuda>
Severity: unspecified Docs Contact: Mayur Patil <maypatil>
Priority: unspecified    
Version: 9.1CC: gfialova, jharuda, nhosoi, rhel-cs-system-management-subsystem-qe, rmeggins, spetrosi, vpunj
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 9.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: role:firewall
Fixed In Version: rhel-system-roles-1.20.0-1.el9 Doc Type: Enhancement
Doc Text:
.The `firewall` system role can add or remove an interface to the zone using PCI device ID Using the PCI device ID, the `firewall` system role can now assign or remove a network interface to or from a zone. Previously, if only the PCI device ID was known instead of the interface name, users had to first identify the corresponding interface name to use the `firewall` system role. With this update, the `firewall` system role can now use the PCI device ID to manage a network interface in a zone.
Story Points: ---
Clone Of: 2100939 Environment:
Last Closed: 2022-11-15 10:24:00 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brennan Paciorek 2022-06-24 18:20:14 UTC
+++ This bug was initially created as a clone of Bug #2100939 +++

Need the ability to add/remove an interface by PCI device ID to a zone.

Comment 13 errata-xmlrpc 2022-11-15 10:24:00 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 (rhel-system-roles bug fix and enhancement update), 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/RHEA-2022:8117