RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:

Need ability to insert comments/description in firewalld rules like we do in iptables using --comments option.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Want to see comment/description in front of the firewalld rules like it is shown in iptables.

Additional info:

> Need ability to insert comments/description in firewalld rules like we do in
> iptables using --comments option.

Can you be more specific about what you want to see? Firewalld already has abstraction types (e.g. services) to make things more user friendly. You can create your own services to give your own meaning. i.e. create a "lamp" service for linux/apache/mysql/php.

Do you want to see this for rich rule? ports?

See also bug 1563629.

Hello,

Customer has a specific requirement for adding a comment/description for each rich rule added, this is a requirement from customer because they need to add their change ticket number(this is the ticket number they would raise to add rich rule) as description or comment against the rich rule they have created.

BZ 1563629 is more specific to port, but if you can merge this request to BZ 1563629 then we are happy to attach customer case to other BZ and close this one out.

Thanks
Sangam