Bug 613835

Summary:	invalid multicast address in corosync.conf file results in bad behavior
Product:	[Fedora] Fedora	Reporter:	Steven Dake <sdake>
Component:	corosync	Assignee:	Steven Dake <sdake>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	14	CC:	agk, fdinitto, sdake
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	613836 (view as bug list)		Environment:
Last Closed:	2011-04-11 01:38:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	613836

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