Bug 1347530

Summary:	Add port for corosync-qnetd to high-availability service
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Friesse <jfriesse>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	todoleza
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	firewalld-0.4.3-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-03 21:03:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	614122, 1185000
Bug Blocks:

Description Jan Friesse 2016-06-17 07:41:04 UTC

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)

Comment 2 Thomas Woerner 2016-06-17 09:57:33 UTC

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

Comment 8 errata-xmlrpc 2016-11-03 21:03:08 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, 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