** Changed in: corosync (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage no
This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.4
---
pacemaker (1.1.14-2ubuntu1.4) xenial; urgency=high
* Properly restart corosync and pacemaker together (LP: #1740892)
- d/pacemaker.preinst: flag corosync to restart pacemaker on
upgrade.
-- Eric Desroche
This bug was fixed in the package pacemaker -
1.1.17+really1.1.16-1ubuntu2
---
pacemaker (1.1.17+really1.1.16-1ubuntu2) artful; urgency=medium
* Rebuilding with a version greater than 1.1.17:
- pacemaker 1.1.17 was pushed to Artful at one point and then got deleted.
pacemaker (
This bug was fixed in the package corosync - 2.3.5-3ubuntu2.1
---
corosync (2.3.5-3ubuntu2.1) xenial; urgency=high
* Properly restart corosync and pacemaker together (LP: #1740892)
- d/rules: pass --restart-after-upgrade to dh_installinit
- d/control: indicate this version b
This bug was fixed in the package corosync - 2.4.2-3ubuntu0.17.10.1
---
corosync (2.4.2-3ubuntu0.17.10.1) artful; urgency=high
* Properly restart corosync and pacemaker together (LP: #1740892)
- d/rules: pass --restart-after-upgrade to dh_installinit
- d/control: indicate th
[VERIFICATION ARTFUL]
Upgrade went well, and have restarted pacemaker on a corosync
installation as it should.
# systemctl status corosync
Active: active (running) since Thu 2018-03-01 15:18:08 UTC; 2min 37s ago
Main PID: 2366 (corosync)
systemctl status pacemaker
Active: active (running)
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fa
[VERIFICATION XENIAL]
* == corosync upgrade (with pacemaker installed) ==
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
# dpkg -l
ii corosync 2.3.5-3ubuntu2 amd64 cluster engine daemon
Hello Drew, or anyone else affected,
Accepted pacemaker into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pacemaker/1.1.17+really1.1.16-1ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package
I had to re-uploader pacemaker for artful.
at one point someone tried to push 1.1.17 into Artful and it then got
deleted, which leave me with no other choice but to re-upload with a
version greater than 1.1.17 for the SRU machinery to accept the changes.
--
You received this bug notification bec
Hello Drew, or anyone else affected,
Accepted corosync into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/corosync/2.4.2-3ubuntu0.17.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
** Description changed:
[Impact]
When corosync and pacemaker are both installed, a corosync upgrade
caused pacemaker to fail. pacemaker will need to be restarted manually
to work again, it won't recover by itself.
[Test Case]
1) Have corosync (< 2.3.5-3ubuntu2) and pacemaker (
Uploaded for Xenial and Artful, it is now waiting in the upload queue
for SRU verification team approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02
[Artful (pre-sru)]
# dpkg -l | egrep "corosync|pacemaker"
ii corosync 2.4.2-3build1
amd64cluster engine daemon and utilities
ii crmsh 2.3.2-1
amd64
I'll resume the SRU and hopefully upload everything next Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notif
Was able to build fine using (optional)
Standard symbol tags
optional
A symbol marked as optional can disappear from the library at any time
and that will never cause dpkg-gensymbols to fail. However, disappeared
optional symbols will continuously appear as MISSING in the
another quick update base on a discussion between nacc/slangasek and
myself :
...
slangasek: fair, above patch results in
https://paste.ubuntu.com/p/hb68G8rpMw/
nacc: those are pretty clearly internal symbols which are not part
of the ABI and you should just mark them (optional) instead of doi
Quick update
The corosync/pacemaker SRU is on hold for now until the FBTFS situation
is fix for Artful.
As mentioned above in comment #58 based on the build log error I had and
the debbug #869986, it is related to some libqb header issues.
Server team will have a look at this, and I'll then
I did some preliminary investigation on the second build failing for
pacemaker in Artful.
And it seems to be related to a binutils/libqb issue
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869986
https://bugzilla.redhat.com/show_bug.cgi?id=1477354
https://github.com/ClusterLabs/libqb/pull/266
I think the chance we have users running pacemaker on Artful can be
consider low and will become even more lower with the release of Bionic
in ~2months.
Bionic already contain the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Before nacc and I spend time on fixing Artful FTBFS situation in order
to SRU this fix... I'll ask the SRU team for guidance if, base on Artful
current information/situation, it is reasonable to skip Artful and focus
on Xenial.
--
You received this bug notification because you are a member of Ubu
Based upon discussion, we will not be fixing this in Trusty. Updating
the SysV scripts to be more error-proof is itself error-prone.
Additionally, corosync on Trusty has not received significant updates,
and this update itself would lead to at least an additional outage (in
order to put the fix int
Forgot the mentioned that It still fails to build, but it fails
differently now than before applying debian commit
"a7476dd96e79197f65acf0f049f75ce8e8f9e801"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
It still FTBFS with the above Debian candidate commit ^
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifi
I *think* this debian commit could possibly be a good candidate to fix
Artful FTBFS situation.
---
$ git show a7476dd9
commit a7476dd96e79197f65acf0f049f75ce8e8f9e801
Author: Jan Pokorny
Date: Thu Feb 2 14:51:46 2017 +0100
Fix: crm_mon: protect against non-standard or failing asctime
[ARTFUL pacemaker - note ]
pacemaker package doesn't build (doesn't build as is without any
changes) in Artful. I suspect the package has been first build in Zesty
and then simply copied to Artful when the release was first created
(without going through the build farm again). Additionally, no cha
** Description changed:
[Impact]
When corosync and pacemaker are both installed, a corosync upgrade
caused pacemaker to fail. pacemaker will need to be restarted manually
to work again, it won't recover by itself.
[Test Case]
1) Have corosync (< 2.3.5-3ubuntu2) and pacemaker (
** Description changed:
+ [Impact]
+
+ When corosync and pacemaker are both installed, a corosync upgrade
+ caused pacemaker to fail. pacemaker will need to be restarted manually
+ to work again, it won't recover by itself.
+
+ [Test Case]
+
+ 1) Have corosync (< 2.3.5-3ubuntu2) and pacemaker (
[XENIAL (pre-SRU)]
== BEFORE UPGRADE ==
# dpkg -l | egrep "corosync|pacemaker"
ii corosync 2.3.5-3ubuntu2
amd64cluster engine daemon and utilities
ii crmsh2.2.0-1
amd64
** Also affects: pacemaker (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Status: New => In Progress
** Changed in: pacemaker (Ubuntu)
Status: In Progress => Fix Released
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Nish A
** Tags added: id-5a53cc961fb7361dbac726f8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifications about this bu
I'll proceed with the SRU next week.
As per my discussion with server team, we will fix Xenial and Artful but
we won't fix Trusty.
** Changed in: corosync (Ubuntu Artful)
Assignee: Nish Aravamudan (nacc) => Eric Desrochers (slashd)
** Changed in: corosync (Ubuntu Xenial)
Assignee: Nish
This bug was fixed in the package corosync - 2.4.2-3ubuntu1
---
corosync (2.4.2-3ubuntu1) bionic; urgency=medium
* Properly restart corosync and pacemaker together (LP: #1740892)
- d/rules: pass --restart-after-upgrade to dh_installinit
- d/control: indicate this version bre
I have uploaded the fixes today to Bionic. I will update the bug once
they are migrated, but the SRUs should be startable now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync u
Hello
I'm fixing the other pacemaker/glib bug[1]. but it is blocked by this
issue.
It would be good if there is good news for this issue i hope.
Thanks.
[1] https://bugs.launchpad.net/bugs/1316970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: corosync (Ubuntu Artful)
Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc)
** Changed in: corosync (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc)
** Changed in: corosync (Ubuntu Trusty)
Assignee: Victor Tapia (vtapia) => Nish
I did some cursory testing yesterday (I still need to think about how to
do a X -> B upgrade w/ a PPA) of B -> B updates. pacemaker stays running
as expected. I am checking (via the MP, a comment recently) if it's
possible to minimize our changes even more in 18.04.
--
You received this bug notif
Sorry for the long delay on my end!
I have pushed up MPs for the correct resolution (I think) for Bionic
(incl. appropriate comments of what can be dropped after B+1 opens).
I am building them in my PPA (pacemaker 1.1.18~rc4-1ubuntu1~ppa1 and
corosync 2.4.2-3ubuntu1~ppa1) now and will test the fo
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336063
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336879
** Merge proposal linked:
https://code.launchpad.net/~nacc/
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336579
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336508
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336509
--
You received this bug notification because you are a member o
[VERIFICATION for XENIAL]
-
[UPGRADE SCENARIO]
# dpkg -l | egrep "corosync|pacemaker"
ii corosync 2.3.5-3ubuntu2
amd64cluster engine daemon and utilities
ii crmsh
4) a case I am not sure what to do with yet (in Trusty or Xenial):
stopping pacemaker and then installing the PPA packages. I'm not sure
how to handle this, really, for 16.04, as the deb-helper scripts don't
seem to have status wrappers and calling systemctl directly does not
apparently work. The e
On Xenial:
corosync2.3.5-3ubuntu2.1~ppa3
pacemaker 1.1.14-2ubuntu1.4~ppa3
The same 3 test cases as in c#39 alll passed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
c
@slashd, @vtapia: I would appreciate additional testing and I will work
on the bionic uploads on Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 c
After hitting some corner cases with my Trusty packages (and Xenial), I
uploaded new versions:
corosync - 2.3.3-1ubuntu4.1~ppa7
pacemaker - 1.1.10+git20130802-1ubuntu2.5~ppa4
And ran the following tests:
1) install corosync and pacemaker, but do not enable either
Upgrade to the PPA packages
No
Xenial MPs updated and packages uploaded to PPA:
corosync - 2.3.5-3ubuntu2.1~ppa2
pacemaker - 1.1.14-2ubuntu1.4~ppa2
Bionic will have to wait til tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336338
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336339
--
You received this bug notification because you are a member o
I tested the versions mentioned in the last comment (with one syntax
fix) and the upgrade path successfully worked! I need to test more
corner-cases and would appreciate help with that (e.g., corosync only
installed, installing pacemaker separately, etc)
The MPs have been updated and I'm building
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336336
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336337
--
You received this bug notification because you are a member o
Big thanks to Robie Basak for providing some feedback and discussion on
IRC and in the MP.
We came up with the following, which I'm currently testing, to try and
resolve this issue:
In addition to all the changes currently in the MP(s), modify:
corosync to Breaks: on older pacemaker versions tha
** Changed in: corosync (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notific
** Bug watch added: Debian Bug tracker #887563
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563
** Also affects: corosync (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887563
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
Testing on Trusty:
# apt-get install corosync pacemaker
# Make corosync start at boot
# sed -i 's/no/yes/' /etc/default/corosync
# Make pacemaker start at boot
# update-rc.d pacemaker defaults
# reboot
# service corosync status; service pacemaker status
* corosync is running
pacemakerd (pid 1927
Ok, I've put up MPs for Trusty (just corosync) and Xenial (corosync and
pacemaker). I think that's correct, and the underlying bug here (package
upgrade of corosync does not lead to pacemaker restarting) should be
resolved in both cases [1) in c#33]. Additionally, case 2) in c#33 is
resolved in bot
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336257
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336256
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 20
Sorry for the long-winded, and delayed update to the bug!
Here's my TL;DR:
1) We want the postinst of corosync to be created with dh_installinit
--restart-on-upgrade, which is the default in compat levels <= 10.
2) We want the init scripts (of whatever type) to restart pacemaker, if
they restart
8) On Xenial and on, where we have systemd .service files for both
corosync and pacemaker, this is my current understanding (after looking
at the .service files and thinking about the Trusty case, as well; some
of this is repeats of others' observations):
8a) corosync can be installed configured w
My findings from today:
1) This situation has always existed on Trusty, afaict. Removing the
regression related tag.
2) There are 24 possible combinations to consider (some are by
definition green already, but I'm including them for completeness; and
some are not achievable) for each release: `se
** Merge proposal linked:
https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336185
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 20
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifications about this bug go to:
** No longer affects: corosync (Ubuntu Zesty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifications about this
** Changed in: corosync (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02
1. Xenial+:
- Overriding dh_installinit[1] would still fail the first time it's
upgraded because of the old corosync.prerm file [2], that contains:
# Automatically added by dh_installinit
if [ -x "/etc/init.d/corosync" ] || [ -e "/etc/init/corosync.conf" ]; then
invoke-rc.d corosync stop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: corosync (Ubuntu Zesty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Titl
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: corosync (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: corosync (Ubuntu Artful)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: corosync (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Tit
This issue has been identified as Field Critical. The medium importance
assigned to this defect seems counter intuitive to the SLA level
assigned.
@Eric
can you provide some insight into a time frame for a fix. Typically under
Critical SLA we expect a dedicated engineer and a fix in a week.
--
Forgot the link to Pacemaker's FAQ
[1] https://wiki.clusterlabs.org/wiki/FAQ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To
I was wrong regarding iii) "when corosync is stopped, do not stop
pacemaker": Pacemaker can use other applications[1] (e.g. heartbeat)
instead of corosync, so this is a property we want to keep.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In my opinion, from the list of desired properties, only the second one is true:
i) Corosync can be used on its own, regardless of having pacemaker installed or
not. Starting both of them would force to mask pacemaker's unit file under
particular scenarios.
iii) IIRC, pacemaker requires corosync
(maybe actually even /bin/systemctl try-restart pacemaker.service ->
restart, if it's running)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pace
Currently, in bionic:
$ systemctl cat pacemaker.service
# /lib/systemd/system/pacemaker.service
After=corosync.service
Requires=corosync.service
$ systemctl cat corosync.service
Desired properties:
i) when corosync is started, attempt to start pacemaker
ii) when corosync is restarted, attempt to
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Zes
On Trusty + corosync=2.3.3-1ubuntu1:
- Stopping corosync while pacemaker is still running:
Jan 9 09:26:55 trusty-corosync corosync[5492]: [MAIN ] Node was shut down
by a signal
Jan 9 09:26:55 trusty-corosync corosync[5492]: [SERV ] Unloading all
Corosync service engines.
Jan 9 09:26:55
As per nacc's comment it seems like "Wants=" is the recommended way to
hook start-up of one unit to the start-up of another unit.[1]
[1] -
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Wants=
So far I have tested using 2 scenarios (including
"Wants=pacemaker.service") and it
On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia wrote:
> As mentioned by Mario @ #10, stopping corosync while pacemaker runs
> throws the same error as the upgrade. Syslog from Xenial +
> corosync=2.3.5-3ubuntu1:
>
> Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping Pacemaker High
> Availability
On Mon, Jan 8, 2018 at 10:04 AM, Nish Aravamudan
wrote:
> On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan
> wrote:
>> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia
>> wrote:
>>> As mentioned by Mario @ #10, stopping corosync while pacemaker runs
>>> throws the same error as the upgrade. Syslog f
On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan
wrote:
> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia
> wrote:
>> As mentioned by Mario @ #10, stopping corosync while pacemaker runs
>> throws the same error as the upgrade. Syslog from Xenial +
>> corosync=2.3.5-3ubuntu1:
>>
>> Jan 8 16:24:37 xe
On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia wrote:
> As mentioned by Mario @ #10, stopping corosync while pacemaker runs
> throws the same error as the upgrade. Syslog from Xenial +
> corosync=2.3.5-3ubuntu1:
>
> Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping Pacemaker High
> Availability
As mentioned by Mario @ #10, stopping corosync while pacemaker runs
throws the same error as the upgrade. Syslog from Xenial +
corosync=2.3.5-3ubuntu1:
Jan 8 16:24:37 xenial-corosync systemd[1]: Stopping Pacemaker High
Availability Cluster Manager...
Jan 8 16:24:37 xenial-corosync pacemakerd[28
"""
> 3.) Stopping and starting corosync doesn't awake the node up again:
> systemctl stop corosync;sleep 10;systemctl restart corosync
> Online: [ kvm01 lb01 ]
> OFFLINE: [ lb02 ]
> Stays in that state until pacemaker is restarted: systemctl restart
> pacemaker
> Bug?
No, pacemaker shou
Based on #10 and some testing I did early today, it really feels like
this might be a bug in pacemaker when re-connecting to corosync after a
restart; I think there are two ways forward on this:
a) corosync package updates should always restart pacemaker
b) we should look for a fix in pacemaker to
** Changed in: corosync (Ubuntu)
Assignee: Eric Desrochers (slashd) => Victor Tapia (vtapia)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused p
Hi, David. This was not induced by the SRU from bug 1739033, as this
issue existed before.
I just tried installing previous version of corosync, and when I
stop/start corosync, pacemaker dies, and needs to be restarted.
As dpkg, when upgrading packages, first stops the service,
copies/extracts ne
This particular bug is under investigation already by some of my
teammate. I'll sync-up with them on Monday.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on
Assigning to slashd as agreed on IRC. This was introduced from the SRU
in bug 1739033 and would be best fixed with that context in mind.
** Changed in: corosync (Ubuntu)
Assignee: Nish Aravamudan (nacc) => Eric Desrochers (slashd)
--
You received this bug notification because you are a mem
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifications about this bug go to:
https://bugs.la
@afreiberger, thank you for the extra info!
Reading the upstream patch referred to in Bug 1739033, I see this
change:
struct main_cp_cb_data {
- enum main_cp_cb_data_state state;
-
int ringnumber;
char *bindnetaddr;
char *mcastaddr;
Now, that is a struct size change
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage notifications about this bug go to:
h
So, it was NOT a pacemaker restart, it was pacemaker trying to perform
standard dropped connection reconnect with an incompatible library for
CPG API access to the restarted corosync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
@nacc:
The error condition was that when corosync restarted, pacemaker
disconnected (as was normal) and then tried reconnecting, but when
reconnecting ran into this error:
error: pcmk_cpg_dispatch: Connection to the CPG API failed: Library
error (2)
So, pacemaker is trying to re-handshake with t
** Changed in: corosync (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To manage noti
Hello,
Being relatively new to pacemaker/corosync -- what is the actual error
condition here? That when corosync is stopped (as part of the package
upgrade), pacemakerd stops and does not restart?
Thanks,
Nish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
bug 1739033 was the stable release update that went in around this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
To mana
** Changed in: corosync (Ubuntu)
Assignee: (unassigned) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to
** Also affects: corosync (Ubuntu)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu)
Importance: Undecided
Status: New
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bu
99 matches
Mail list logo
