Back to bug 1324546

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-04-06 15:17:45 UTC Target Release --- 8.0
Marius Cornea 2016-04-06 15:20:44 UTC Target Milestone --- ga
Michele Baldessari 2016-04-06 15:23:12 UTC CC michele
Mike Burns 2016-04-06 17:39:07 UTC Depends On 1245951
Doc Text Cause: Corosync sometimes fails to start correctly in IPv6 environments

Consequence: Corosync can fail to start on reboot of controller nodes

Workaround (if any): On reboot of the controller nodes, when the host comes back up, check for corosync status. If it failed, restart it.

Result: The corosync service should come up correctly when restarted.
Doc Type Bug Fix Known Issue
Michele Baldessari 2016-04-06 17:45:13 UTC Doc Text Cause: Corosync sometimes fails to start correctly in IPv6 environments

Consequence: Corosync can fail to start on reboot of controller nodes

Workaround (if any): On reboot of the controller nodes, when the host comes back up, check for corosync status. If it failed, restart it.

Result: The corosync service should come up correctly when restarted.
Cause: Corosync sometimes fails to start correctly in IPv6 environments

Consequence: Corosync can fail to start on reboot of controller nodes

Workaround (if any): On reboot of the controller nodes, when the host comes back up, check for corosync status. If it failed, start the following services manually and in the following order: corosync, pacemaker, pcsd

Result: The corosync service and related cluster services should come up correctly when restarted.
Mike Burns 2016-04-07 21:36:02 UTC Target Release 8.0 10.0
Target Milestone ga ---
Mike Burns 2016-04-13 14:50:09 UTC Target Release 10.0 (Newton) 8.0 (Liberty)
Vincent S. Cojot 2016-04-22 18:24:54 UTC CC vcojot
Alex Schultz 2017-01-27 23:21:46 UTC CC aschultz
Fabio Massimo Di Nitto 2017-02-22 12:08:33 UTC Status NEW CLOSED
CC fdinitto
Resolution --- DUPLICATE
Last Closed 2017-02-22 07:08:33 UTC

Back to bug 1324546