Bug 2101607

Summary: forward_port should accept list of string or list of dict
Product: Red Hat Enterprise Linux 8 Reporter: Rich Megginson <rmeggins>
Component: rhel-system-rolesAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: David Jež <djez>
Severity: unspecified Docs Contact: Gabi Fialová <gfialova>
Priority: unspecified    
Version: 8.7CC: djez, elpereir, gfialova, nhosoi, rhel-cs-system-management-subsystem-qe, spetrosi
Target Milestone: rcKeywords: Triaged
Target Release: 8.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: role:firewall
Fixed In Version: rhel-system-roles-1.20.0-1.el8 Doc Type: Bug Fix
Doc Text:
.The `forward_port` parameter now accepts both the `string` and `dict` option Previously, in the `firewall` RHEL System role, the `forward_port` parameter only accepted the `string` option. However, the role documentation claimed that both `string` *and* `dict` options were supported. Consequently, the users reading and following the documentation were getting an error. This bug has been fixed by making `forward_port` accept both options. As a result, the users can safely follow the documentation to configure port forwarding.
Story Points: ---
Clone Of: 2100605 Environment:
Last Closed: 2022-11-08 09:41:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2100605    
Bug Blocks:    

Description Rich Megginson 2022-06-27 22:28:47 UTC
+++ This bug was initially created as a clone of Bug #2100605 +++

forward_port only accepts the string form at https://github.com/linux-system-roles/firewall#forward_port - it should accept the dict form too

Comment 13 errata-xmlrpc 2022-11-08 09:41:52 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.