Bug 613835 - invalid multicast address in corosync.conf file results in bad behavior
Summary: invalid multicast address in corosync.conf file results in bad behavior
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: corosync
Version: 14
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Steven Dake
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 613836
TreeView+ depends on / blocked
 
Reported: 2010-07-12 22:18 UTC by Steven Dake
Modified: 2016-04-26 16:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 613836 (view as bug list)
Environment:
Last Closed: 2011-04-11 01:38:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Steven Dake 2010-07-12 22:18:57 UTC 
Description of problem:
corosync behaves erratically when invalid multicast address is specified in corosync.conf file.

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


How reproducible:


Steps to Reproduce:
1. set multicast address to 220.1.1.1
2. corosync wont form configuration
3.
  
Actual results:
coroysnc fails in odd ways

Expected results:
error should be logged and corosync should fail to start

Additional info:
Comment 1 Bug Zapper 2010-07-30 12:32:25 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Note You need to log in before you can comment on or make changes to this bug.