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
** Tags added: canonical-bootstack
--
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
Looks like crm_mon is still reporting a connection failure:
ubuntu@juju-machine-0-lxc-11:~$ /usr/sbin/crm_mon -1 -r -f
Could not establish cib_ro connection: No such file or directory (2)
Connection to cluster failed: Transport endpoint is not connected
--
You received this bug notification
I've found that when you run crm_resource -P alone, though the failure
clears from the crm status, the service does not appear in the resource
group.
After running crm_resource -P (which isn't in the man page?) but before
running a resource cleanup:
Last updated: Sat Nov 4 21:56:18 2017
Last
For those that can see it adding an action to clean up was proposed:
https://rt.admin.canonical.com/Ticket/Display.html?id=101456
** Bug watch added: rt.admin.canonical.com/ #101456
https://rt.admin.canonical.com/Ticket/Display.html?id=101456
--
You received this bug notification because you
Looks like this almost exclusively occurs with ncc on our clouds.
Sometimes self resolves and sometimes requires manual cleanup as noted above
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
6 matches
Mail list logo
