Bug 1395700 – qdrouterd 0.4-19 segfault when qpidd down for longer time and goferd restarted

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

Bug 1395700 - qdrouterd 0.4-19 segfault when qpidd down for longer time and goferd restarted

Summary:	qdrouterd 0.4-19 segfault when qpidd down for longer time and goferd restarted

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	katello-agent (Show other bugs)
Sub Component:
Version:	6.2.4
Hardware:	x86_64 Linux

Priority	urgent Severity urgent (vote)
Target Milestone:	Beta
Target Release:	Unused
Assigned To:	satellite6-bugs
QA Contact:	Jitendra Yejare
Docs Contact:

URL:	https://bugzilla.redhat.com/show_bug....
Whiteboard:
Keywords:	Triaged

Depends On:	1393128 1396568
Blocks:	1399395
	Show dependency tree / graph

Reported:	2016-11-16 08:24 EST by Bryan Kearney
Modified:	2018-02-21 07:57 EST (History)
CC List:	12 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Under certain conditions, build 19 of the dispatch router can terminate unexpectedly with a segmentation fault. The memory management has been improved to prevent this happening.
Story Points:	---
Clone Of:	1393128
Environment:
Last Closed:	2018-02-21 07:57:01 EST
Type:	---
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 Knowledge Base (Solution)	2765811	None	None	None	2016-11-16 08:24 EST
Red Hat Product Errata	RHBA-2018:0338	normal	SHIPPED_LIVE	Red Hat Satellite 6.3 Tools	2018-02-21 14:30:02 EST

Groups: None (edit)

Comment 2 Jitendra Yejare 2017-10-04 11:12:07 EDT

Verifying this bug using steps mentioned in comment of similar bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1393128#c11

Steps Followed:

1. Had all Sat services running

2. On satellite6, freezed qpidd process for at least 11 seconds and then unfreezed it:
# kill -SIGSTOP $(pgrep qpidd); sleep 11; kill -SIGCONT $(pgrep qpidd)

3. Immediately after the expect script is running, restarted goferd on only one content(DIDNT TRY WITH MULTIPLE) host :
# service goferd restart; sleep 3; service goferd restart

4. Check qdrouterd service status


Behavior:

I don't see any segfault in qdrouterd status.

@pavel, Is this ok if I can mark this bug as verified ?

Comment 3 Pavel Moravec 2017-10-05 07:14:39 EDT

(In reply to Jitendra Yejare from comment #2)
> Verifying this bug using steps mentioned in comment of similar bug: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1393128#c11
> 

Yes, that is the most reliable reproducer of the race condition (though using artificial steps not triggered by a regular activity - just mimicking some unknown real activity). One Content Host (with 2 goferd restarts in sequence) is sufficient.

Sat 6.3 uses quite higher version of qdrouterd, so it is probable that this segfault has never been in that rebased version of qdrouterd.

Comment 4 Jitendra Yejare 2017-10-05 08:22:15 EDT

As per comment 2 and 3, changing the bug status to Verified!

Comment 7 errata-xmlrpc 2018-02-21 07:57:01 EST

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/RHBA-2018:0338

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