RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #576000 +++

Description of problem:

When setting up and you forget your firewall on (like I did).

totem gets stuck in the gather state:
Mar 23 09:39:16 corosync [TOTEM ] entering GATHER state from 3.
Mar 23 09:39:18 corosync [TOTEM ] The consensus timeout expired.
...

Our current shutdown relies on the ability to send a token.
It hooks into sched_work() which gets fired on token_send.
In the above state we are not in a state to send a token
so we can't shutdown.

We probably need to check that the totem state is operational
before calling schedwrk_create(), if not call
service_exit_schedwrk_handler() directly.


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

How reproducible:
100%

Steps to Reproduce:
1.enable firewall (default one)
2.service corosync restart
3.
  
Actual results:
it will never shutdown

Expected results:
shutdown quickly

Additional info:

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