[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
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 Server Team, which is subscribed to corosync in 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.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
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 packages that are source- identical to the MPs as corosync - 2.3.3-1ubuntu4.1~ppa6 pacemaker - 1.1.10+git20130802-1ubuntu2.5~ppa3 The reason for the repeated version bumps is these packages now have inter-related versioning. I will try and do a similar set of MPs for xenial and bionic first thing tomorrow, if not later today. ** Merge proposal unlinked: https://code.launchpad.net/~nacc/ubuntu/+source/corosync/+git/corosync/+merge/336185 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in 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.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25
Filed: https://bugs.launchpad.net/debian/+source/php-sabre- vobject-3/+bug/1744166 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to latest upstream release 7.0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1724896/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25
The only legitimate bug is php-sabre-vobject-3, which is unrelated to this upload. I will fix it independently. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880337 ** Bug watch added: Debian Bug tracker #880337 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880337 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to latest upstream release 7.0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1724896/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744148] Re: [MRE] Please update to latest upstream release 7.0.27
** Changed in: php7.0 (Ubuntu) Status: New => Confirmed ** Also affects: php7.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: php7.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: php7.0 (Ubuntu Xenial) Status: New => Confirmed ** Changed in: php7.0 (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: php7.0 (Ubuntu Xenial) Assignee: (unassigned) => Nish Aravamudan (nacc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1744148 Title: [MRE] Please update to latest upstream release 7.0.27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1744148/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail
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 than the one we are going to provide in this update pacemaker's preinst to mark via a file in /run if pacemaker is running, if upgrading from an older version of pacemaker corosync's postinst to check the file in /run and start pacemaker, if upgrading from an older version of corosync The effect of these changes together is to force corosync to upgrade pacemaker (via the Breaks) and for pacemaker to indicate to corosync whether it should start pacemaker in the maintainer scripts. The currently building versions for Trusty in my PPA (corosync = 2.3.3-1ubuntu4.1~ppa4 and pacemaker=1.1.10+git20130802-1ubuntu2.5~ppa1) are meant to contain these additional changes and upgrade together. I will test them once they are built. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in 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.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25
I should say, retrigger the lot, once we are allowed to again :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to latest upstream release 7.0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1724896/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1724896] Re: [MRE] Please update to latest upstream release 7.0.25
So far everyting I've seen is false negatives due to infra issues. I'm retriggering the lot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php7.0 in Ubuntu. https://bugs.launchpad.net/bugs/1724896 Title: [MRE] Please update to latest upstream release 7.0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1724896/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1744016] Re: package samba 2:4.5.8+dfsg-0ubuntu0.17.04.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. I note you are trying to start samba-ad-dc, which is meant for active directory controllers. Could you please attach your smb.conf file? It must be configured as an AD/DC server. While you are at it, please also attach the log files from /var/log/samba/log*, they should tell us what is going on and why the service didn't start. You do have a warning about an error in your smb.conf, but I don't think it's fatal: Jan 18 11:40:54 SCHLAP-IT69 samba[28867]: WARNING: Ignoring invalid value 'SMB1' for parameter 'client min protocol' You probably meant NT1 there. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1744016 Title: package samba 2:4.5.8+dfsg-0ubuntu0.17.04.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1744016/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
