Bug 1530512 – clean up port map on brick disconnect

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

Bug 1530512 - clean up port map on brick disconnect

Summary:	clean up port map on brick disconnect

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	glusterd (Show other bugs)
Sub Component:
Version:	3.4
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Atin Mukherjee
QA Contact:	Bala Konda Reddy M
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1503244 1503246 1507747 1507749 1526371
Blocks:	1503137
	Show dependency tree / graph

Reported:	2018-01-03 02:47 EST by Atin Mukherjee
Modified:	2018-09-04 02:42 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	glusterfs-3.12.2-3
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1526371
Environment:
Last Closed:	2018-09-04 02:40:51 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-2018:2607	None	None	None	2018-09-04 02:42 EDT

Groups: None (edit)

Comment 5 Bala Konda Reddy M 2018-04-18 03:49:44 EDT

Verified with 3.12.2-7

Followed these steps mentioned in the description.
1. Blocked port 49152 by running a program
2. Create a volume and start the volume so that brick starts listening to 49153
3. kill -9 <brick process id>
4. Released the port 49152 and waited for more than 2 minutes
5. force start the volume so that the brick now start listen to 49152.
6. Try to mount the volume

As expected mount is successful and cleanup of port is happening

Hence marking it as verified.

Comment 7 errata-xmlrpc 2018-09-04 02:40:51 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://access.redhat.com/errata/RHSA-2018:2607

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