[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-16 Thread Nish Aravamudan
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

[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-16 Thread Nish Aravamudan
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:

[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-16 Thread Launchpad Bug Tracker
** 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

[Sts-sponsors] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-01-16 Thread Chris Newcomer
Ran 3.5 version for Trusty, Xenial, and Artful on a VM that was MAAS- deployed. I have not been able to discover any issues. I also installed it on a bare-metal server running Xenial with no problems as well. -- You received this bug notification because you are a member of STS Sponsors, which

[Sts-sponsors] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-01-16 Thread Doug Parrish
Ran 3.5 version for Trusty, Xenial, and Artful. No problems appear to have been introduced by this version. -- 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/1734983 Title: Request to

[Sts-sponsors] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-01-16 Thread Alex Moldovan
Marked Zesty as invalid as it reached end of like on Jan 13 2018. ** Changed in: sosreport (Ubuntu Zesty) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1734983] Re: Request to backport sosreport v3.5

2018-01-16 Thread Alex Moldovan
Testing done for Trusty, Xenial and Arful with no errors noticed. -- 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/1734983 Title: Request to backport sosreport v3.5 Status in sosreport:

[Sts-sponsors] [Bug 1699179] Re: PackageReporter kicks in during do-release-upgrade

2018-01-16 Thread Eric Desrochers
** No longer affects: landscape-client (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/1699179 Title: PackageReporter kicks in during do-release-upgrade Status in Landscape

[Sts-sponsors] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

2018-01-16 Thread Eric Desrochers
** No longer affects: apparmor (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/1717714 Title: @{pid} variable broken on systems with pid_max more than 6 digits Status in

[Sts-sponsors] [Bug 1743232] Re: set vm_info to kvm for digitalocean instances

2018-01-16 Thread Eric Desrochers
** No longer affects: landscape-client (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/1743232 Title: set vm_info to kvm for digitalocean instances Status in Landscape

[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-16 Thread Eric Desrochers
** 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

[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-16 Thread Eric Desrochers
** 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

[Sts-sponsors] [Bug 1743232] Re: set vm_info to kvm for digitalocean instances

2018-01-16 Thread Andreas Hasenack
** Changed in: landscape-client Status: In Progress => Fix Committed -- 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/1743232 Title: set vm_info to kvm for digitalocean instances

[Sts-sponsors] [Bug 1743232] Re: set vm_info to kvm for digitalocean instances

2018-01-16 Thread Andreas Hasenack
** Changed in: landscape-client Milestone: None => 18.01 -- 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/1743232 Title: set vm_info to kvm for digitalocean instances Status in Landscape