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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on
[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
I'll resume the SRU and hopefully upload everything next Monday.
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
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
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
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 STS
Sponsors, which is subscribed to the bug report.
[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
** Tags added: id-5a53cc961fb7361dbac726f8
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
Status in OpenStack
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:
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
** 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:
** 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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync
** 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
[VERIFICATION for XENIAL]
-
[UPGRADE SCENARIO]
# dpkg -l | egrep "corosync|pacemaker"
ii corosync 2.3.5-3ubuntu2
amd64cluster engine daemon and utilities
ii crmsh
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 STS
Sponsors, which is subscribed to the bug report.
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
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
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
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
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:
** 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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync
** No longer affects: corosync (Ubuntu Zesty)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02 caused pacemaker to fail
Status in OpenStack
** Changed in: corosync (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => Nish Aravamudan (nacc)
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on
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 STS
Sponsors, which is subscribed to the bug report.
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 STS
Sponsors, which is subscribed to the bug report.
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.
--
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 STS
Sponsors, which is subscribed
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
(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 STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1740892
Title:
corosync upgrade on 2018-01-02
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
34 matches
Mail list logo
