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:
RHEL 7.3 is getting new subpackage of corosync called corosync-qnetd. Corosync qnetd is used as quorum arbiter for corosync and communication is going on tcp port 5403. Current high-availability.xml doesn't contain this port.

How reproducible:
100%

Steps to Reproduce:
1. Allow high-availability service
2. Execute corosync, corosync-qdevice and corosync-qnetd

Actual results:
It's not possible to connect to tcp port 5403.

Expected results:
It's possible to connect to tcp port 5403.


Additional info:
Proposed PR is https://github.com/t-woerner/firewalld/pull/125 (patch https://github.com/t-woerner/firewalld/pull/125/commits/19a6150ae26361543c0de1830952124e9c40ceb1)

Fixed upstream: 
https://github.com/t-woerner/firewalld/commit/2a10874935f93e103c0b6846eb441876fa1ad231
https://github.com/t-woerner/firewalld/commit/19a6150ae26361543c0de1830952124e9c40ceb1

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, 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://rhn.redhat.com/errata/RHSA-2016-2597.html