I checked the scripts executed on upgrade and didn't find a place obviously
causing this.
@Alvaro you mentioned it is related to "Invalid IPC credentials" could you
provide some background on that - that was pacemaker but how is it related to
this start/restart?
While certainly an issue currently this isn't really actionable - so I beg your
pardon but for now set this to incomplete.
Since it was also incomplete and didn't gain other affected users that might be
ok, if we find more details to go on it will show up in bug triage again on any
update here.
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1564250
Title:
Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped state
Status in pacemaker package in Ubuntu:
Incomplete
Bug description:
Using pacemaker version: 1.1.10+git20130802-1ubuntu2.3
On ubuntu: Ubuntu 14.04.4 LTS
Corosync upgrade to 2.3.3-1ubuntu2 leaves pacemaker in a stopped
state. Specifically from version 2.3.3-1ubuntu1
I have attached logs from such upgrade.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1564250/+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
