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:
A bunch of new service definitions have been added to upstream firewalld. backporting the xml files "should" be fairly non-disruptive and provide a better user experience.

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

How reproducible:
100%

Steps to Reproduce:
1. install firewalld
2. look for new services (such as prometheus-node-exporter)
3. note they exist upstream

Actual results:
services known to upstream are not present

Expected results:
This isn't exactly unexpected.  Upstream moves faster than RHEL, but it would be handy to sync these up on a somewhat regular basis beyond the feature updates.

Additional info:

The new services naturally make their way into RHEL when a firewalld package rebase occurs.

Do you have a particular service in mind to backport?

prometheus-node-exporter is the one that triggered my request.  I just happened to notice a few others were added recently to upstream.

(In reply to Pat Riehecky from comment #2)
> prometheus-node-exporter is the one that triggered my request.  I just
> happened to notice a few others were added recently to upstream.

That's in firewalld v1.2.0 and later. Bug 2125371 is to rebase firewalld to that stable stream. So this will get fixed indirectly.

$ git fixes 3a6bf7320d9d5c81c4db5afee98dc28b77874e80
Fixes: 3a6bf7320d9d ("feat(service): add prometheus node-exporter")

$ git tag --contains 3a6bf7320d9d5c81c4db5afee98dc28b77874e80
v1.2.0
v1.2.1

MR: https://gitlab.com/redhat/centos-stream/rpms/firewalld/-/merge_requests/11

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 (firewalld 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/RHBA-2023:2546