Corosync is doing it's job, if there are failures in the resource it will log those failures. What's more of an issue here is that charm- deployed clouds have very frequent failures on nova-consoleauth. Retargetting this bug.
** Package changed: corosync (Ubuntu) => nova-cloud-controller (Juju Charms Collection) -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1709633 Title: Failed actions requiring manual clean up when resource is running Status in nova-cloud-controller package in Juju Charms Collection: New Bug description: We often run into an issue where we find corosync reporting failed actions that require manual intervention to clean up. To clean up (since the resources are active) we run: crm_resource -P :: crm status found Failed Actions: * res_nova_consoleauth_monitor_5000 on juju-2691ab-21-lxd-0 'not running' (7): call=147, status=complete, exitreason='none', last-rc-change='Tue Mar 21 16:25:11 2017', queued=0ms, exec=0ms :: ran # crm_resource -P :: check returned OK afterwards https://pastebin.canonical.com/183213/ :: or if this does not work aka check does not clear afterwards we have to run $ sudo crm resource cleanup $resourcename To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/nova-cloud-controller/+bug/1709633/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
