Bug 1347530 – Add port for corosync-qnetd to high-availability service

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1347530 - Add port for corosync-qnetd to high-availability service

Summary:	Add port for corosync-qnetd to high-availability service

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	firewalld (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Thomas Woerner
QA Contact:	Tomas Dolezal
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	614122 1185000
Blocks:
	Show dependency tree / graph

Reported:	2016-06-17 03:41 EDT by Jan Friesse
Modified:	2016-11-03 17:03 EDT (History)
CC List:	1 user (show)

See Also:
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 17:03:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:2597	normal	SHIPPED_LIVE	Moderate: firewalld security, bug fix, and enhancement update	2016-11-03 08:11:47 EDT

Groups: None (edit)

Description Jan Friesse 2016-06-17 03:41:04 EDT

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 05:57:33 EDT

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 17:03:08 EDT

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

Note You need to log in before you can comment on or make changes to this bug.