Bug 500313 - With DHCP reset timeout set to 30 seconds - openais segfaults
Summary: With DHCP reset timeout set to 30 seconds - openais segfaults
Alias: None
Product: Fedora
Classification: Fedora
Component: corosync   
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Jan Friesse
QA Contact: Fedora Extras Quality Assurance
Keywords: Reopened
Depends On:
TreeView+ depends on / blocked
Reported: 2009-05-12 08:42 UTC by Steven Dake
Modified: 2016-04-27 05:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 224518
Last Closed: 2009-06-03 14:58:30 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Steven Dake 2009-05-12 08:42:28 UTC
+++ This bug was initially created as a clone of Bug #224518 +++

Description of problem:
Segfault occurs when DHCP reset timeout set to 30 seconds.

Version-Release number of selected component (if applicable):

How reproducible:
takes a few hours to reproduce.

Steps to Reproduce:
1.Set DHCP timeout to 30 seconds for machines in a RHCS setup.
2.Run revolver.
Actual results:

Expected results:
No segfault

Additional info:
This use case is not supported - however - the software should still not segfault.

Comment 1 Steven Dake 2009-05-12 08:43:37 UTC
This is very low priority, but if you run out of better things to do, try to reproduce this bug and let us know if it still exists or close as not a defect in corosync.

Comment 2 Jan Friesse 2009-06-01 15:13:24 UTC
I'm trying to reproduce this bug. It's fully dynamic DHCP (pool, but leases are still same), and running testcpg in while cycle (send one message). Whole thing is running 6 hours now, and I was not able to get error.

On a beginning, I was able to get "bus error" and "aborted" messages, with shutting down and up dhclient, but never get segfault.

Is my testing correct?

If yes, is 6 hours enough, to close bug?

Comment 3 Steven Dake 2009-06-02 17:53:13 UTC
Did you have lease period set to 30 seconds?  If so, then go ahead close fixed currentrelease.


Comment 4 Jan Friesse 2009-06-03 14:58:30 UTC
I was unable to reproduce this bug with corosync trunk (r2203) so I'm closing the bug.

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