Bug 557513

Summary: Corosync doesn't shutdown if iptables service is on
Product: [Fedora] Fedora Reporter: Jan Friesse <jfriesse>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 13CC: agk, fdinitto, sdake
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-21 15:19:40 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: 600479    

Description Jan Friesse 2010-01-21 17:00:57 UTC 
Description of problem:
Corosync doesn't shutdown if iptables service is on.

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

How reproducible:
Install default Fedora 12 (Rawhide) and keep iptables service running. Then run corosync and try it shutdown. Corosync will still try to make consensus and never end.

Steps to Reproduce:
1. Install default Fedora 12 (Rawhide)
2. Run corosync -f
3. Ctrl+C or kill -TERM (PID_OF_COROSYNC)
  
Actual results:
Corosync will never end.

Expected results:
Corosync will end.

Additional info:
Tracking bug. Main problem is, that schedwrk is used for shutdown of IPC. But because schedwrk is driven by Totem, and Totem doesn't have consensus (it is not in operational state), schedwrk callback function for shutdown will be never called.

One of solution could be to put after corosync_service_unlink_all call in main.c sleep (default/configurable value) and after that, exit (some error). This has one problem: what is good default value?

Solution should work correctly, because call is in thread, so:
- if regular shutdown sewuence works -> no problem
- if it doesn't -> exit with error
Comment 1 Bug Zapper 2010-03-15 14:10:37 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Steven Dake 2010-07-21 15:19:40 UTC 

*** This bug has been marked as a duplicate of bug 576000 ***