[Bug 1761899] [NEW] [FFe] Please merge with 1.13.10-1 from Debian unstable

[Nish Aravamudan]

Public bug reported:

Feature Freeze exception:

Much like 16.04, we want to get nginx in 18.04 as close to a LTS release
as possible. Future updates to get the actual upstream LTS release will
come from bionic-updates.

Features between 1.13.6 and 1.13.10:

https://nginx.org/en/CHANGES

** Affects: nginx (Ubuntu)
 Importance: Undecided
 Status: New

** Merge proposal linked:
   
https://code.launchpad.net/~nacc/ubuntu/+source/nginx/+git/nginx/+merge/342762

** Description changed:

  Feature Freeze exception:
  
  Much like 16.04, we want to get nginx in 18.04 as close to a LTS release
  as possible. Future updates to get the actual upstream LTS release will
  come from bionic-updates.
+ 
+ Features between 1.13.6 and 1.13.10:
+ 
+ https://nginx.org/en/CHANGES

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1761899

Title:
  [FFe] Please merge with 1.13.10-1 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1761899/+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 1761370] Re: package libapache2-mod-php7.0 7.0.28-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nish Aravamudan]

Thank you for filing this bug report.

Per the output:

modified.conffile..etc.apache2.mods-available.php7.0.conf: [deleted]
modified.conffile..etc.apache2.mods-available.php7.0.load: [deleted]

You have deleted the apache2 configuration for the php7.0 module. If
your goal was to disable PHP support in apache2, you should either
remove the libapache2-mod-php metapackage, or run `sudo a2dismod php7.0`
(I think on the latter, it might be `sudo a2dismod php`).

As this appears to be a local configuration issue, I'm marking it as
incomplete. If you feel that is incorrect, please provide a comment
indicating why and mark it as New.

** Changed in: php7.0 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1761370

Title:
  package libapache2-mod-php7.0 7.0.28-0ubuntu0.16.04.1 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/php7.0/+bug/1761370/+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 1757344] Re: package php7.1-sqlite3 7.1.15-0ubuntu0.17.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Nish Aravamudan]

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1757344

Title:
  package php7.1-sqlite3 7.1.15-0ubuntu0.17.10.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1757344/+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 1638957] Re: [MIR] http-parser, dependency of sssd

[Nish Aravamudan]

Given the security team ack, and the package generally, fine to MIR

I believe the only package that needs promotion (other than the source):

libhttp-parser2.7.1

** Changed in: http-parser (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1638957

Title:
  [MIR] http-parser, dependency of sssd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/http-parser/+bug/1638957/+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 1757344] Re: package php7.1-sqlite3 7.1.15-0ubuntu0.17.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Nish Aravamudan]

Hello and thank you for filing this bug!

Was your update performed from a terminal (e.g., using apt or apt-get)
or from a GUI (e.g. update-manager)? If the latter, which GUI?

The segmentation fault reported is actually in the package manager
itself (the frontend of it), not with PHP.

A workaround is probably to use apt/apt-get, if you weren't already, to
perform the upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1757344

Title:
  package php7.1-sqlite3 7.1.15-0ubuntu0.17.10.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1757344/+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 1638957] Re: [MIR] http-parser, dependency of sssd

[Nish Aravamudan]

** Changed in: http-parser (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1638957

Title:
  [MIR] http-parser, dependency of sssd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/http-parser/+bug/1638957/+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 1753018] Re: Please merge strongswan 5.6.2-1 from Debian

[Nish Aravamudan]

FYI, the CVE was already fixed in 5.6.1-2ubuntu4.

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1753018

Title:
  Please merge strongswan 5.6.2-1 from Debian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1753018/+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.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

** Attachment added: "php7.1_7.1.15-0ubuntu0.17.10.1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079883/+files/php7.1_7.1.15-0ubuntu0.17.10.1.dsc

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

@Marc: php7.0/7.1 is ready to sponsor into xenial-security (and
-updates). You should only need to do some changelog mangling to match
the security team's format, and a `uscan` to grab the orig tarball from
upstream.

** Changed in: php7.0 (Ubuntu Xenial)
 Assignee: Nish Aravamudan (nacc) => Marc Deslauriers (mdeslaur)

** Changed in: php7.1 (Ubuntu Artful)
 Assignee: Nish Aravamudan (nacc) => Marc Deslauriers (mdeslaur)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

** Attachment added: "php7.1_7.1.15-0ubuntu0.17.10.1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079884/+files/php7.1_7.1.15-0ubuntu0.17.10.1.debian.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

** Attachment added: "php7.0_7.0.28-0ubuntu0.16.04.1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079866/+files/php7.0_7.0.28-0ubuntu0.16.04.1.debian.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

** Attachment added: "php7.0_7.0.28-0ubuntu0.16.04.1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1744148/+attachment/5079867/+files/php7.0_7.0.28-0ubuntu0.16.04.1.dsc

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

** Changed in: php7.2 (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1744148] Re: [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

[Nish Aravamudan]

** Also affects: php7.1 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: php7.0 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: php7.1 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** No longer affects: php7.0 (Ubuntu Artful)

** Changed in: php7.1 (Ubuntu)
   Status: New => Invalid

** Changed in: php7.1 (Ubuntu Artful)
   Status: New => In Progress

** Changed in: php7.1 (Ubuntu Artful)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Also affects: php7.2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: php7.2 (Ubuntu)
   Status: New => In Progress

** Changed in: php7.2 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1744148

Title:
  [MRE] Please update to latest upstream release 7.0.28 / 7.1.15 / 7.2.3

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 1596474] Re: openipmi adding to autoload fail

[Nish Aravamudan]

** Changed in: openipmi (Ubuntu Xenial)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1596474

Title:
  openipmi adding to autoload fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1596474/+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

[Nish Aravamudan]

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 into place).

If, in the future, an additional security/bugfix update was to be
applied to Trusty for corosync, we should revisit this.

-- 
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 1744072] Re: [MIR] Chrony in 18.04

[Nish Aravamudan]

I reviewed chrony; it's fine to MIR (and has security team approval).
MIR ACKed.

** Changed in: chrony (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1744072

Title:
  [MIR] Chrony in 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp-charm/+bug/1744072/+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 1749745] [NEW] php7.2 has removed the mcrypt module

[Nish Aravamudan]

Public bug reported:

http://php.net/manual/en/migration71.deprecated.php

There are a  number of affected packages.

** Affects: cakephp (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gosa (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: php-crypt-chap (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: php-horde-crypt-blowfish (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: php-horde-passwd (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: roundcube (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: tcpdf (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: tt-rss (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: yubikey-ksm (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: php-crypt-chap (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: php-horde-passwd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1749745

Title:
  php7.2 has removed the mcrypt module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cakephp/+bug/1749745/+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 1744072] Re: [MIR] Chrony in 18.04

[Nish Aravamudan]

** Changed in: chrony (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: chrony (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1744072

Title:
  [MIR] Chrony in 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ntp-charm/+bug/1744072/+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

[Nish Aravamudan]

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
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

[Nish Aravamudan]

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 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

[Nish Aravamudan]

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 following scenarios:

(to level-set)
X -> B [should be broken]

X -> B + PPA [should work]

A -> B [may or may not be broken, because there is not a corosync
version change]

A -> B + PPA [should work]

as well as the prior cases of fresh install in B and reinstall in B.

Additionally, we should be able to test starting/stopping/restarting of
corosync in B successfully doing the same state to pacemaker.

Presuming these tests pass and the Canonical Server Team reviews and
approves them, I will upload them this week.

Eric & co. at that point, I'm wondering if perhaps your team can pick up
the SRUs to X, A and T? I think X and A will take the same changes. As
we discussed, we would do the minimum required for the older releases,
as in my MPs already up. The only thing currently missing is a debconf
note prompt, I think, that says pacemaker will have been stopped by the
corosync upgrade and will need to be manually restarted.

-- 
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 1621386] Re: [MIR] libsodium

[Nish Aravamudan]

** Changed in: libsodium (Ubuntu)
   Status: Fix Released => Won't Fix

** Changed in: libsodium (Ubuntu)
   Status: Won't Fix => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsodium in Ubuntu.
https://bugs.launchpad.net/bugs/1621386

Title:
  [MIR] libsodium

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsodium/+bug/1621386/+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

[Nish Aravamudan]

** Changed in: php7.0 (Ubuntu Xenial)
   Status: Confirmed => In Progress

-- 
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 1743904] Re: Please merge with Debian unstable 57

[Nish Aravamudan]

** Description changed:

  php-defaults (57ubuntu1) bionic; urgency=medium
-   
-   * Merge with Debian unstable (LP: #1743904). Remaining changes:
- - d/control, d/rules: bump to php7.1 as the default.
-   + Update text of d/control to refer to Ubuntu and 7.1 as well.
-   + d/control generated by `./debian/rules debian/control`
  
-  -- Nishanth Aravamudan   Wed, 17 Jan
- 2018 15:55:22 -0800
+   * Merge with Debian unstable (LP: #1743904). Remaining changes:
+ - d/control, d/rules: bump to php7.2 as the default.
+   + Update text of d/control to refer to Ubuntu and 7.2 as well.
+   + d/control generated by `./debian/rules debian/control`
+ 
+  -- Nishanth Aravamudan   Tue, 23 Jan
+ 2018 10:07:51 -0800

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1743904

Title:
  Please merge with Debian unstable 57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1743904/+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

[Nish Aravamudan]

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
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

[Nish Aravamudan]

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 end result is that pacemaker will be started in
these cases, which does not seem directly harmful, but I'm not 100% (it
would also presumablly start on next reboot anyways).

-- 
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

[Nish Aravamudan]

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 errors, both are still disabled

2) install corosync and pacemaker, enable corosync only
Upgrade to the PPA packages
No errors, corosyc is restarted

3) install corosync and pacemaker, enable both
Upgrade to the PPA packages
No errors, corosync and pacemaker restarted

I'm moving on to update the xenial branches now.

-- 
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

[Nish Aravamudan]

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

[Nish Aravamudan]

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

[Nish Aravamudan]

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

[Nish Aravamudan]

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

[Nish Aravamudan]

** 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

[Nish Aravamudan]

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

[Nish Aravamudan]

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

[Nish Aravamudan]

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 1743904] [NEW] Please merge with Debian unstable 57

[Nish Aravamudan]

Public bug reported:

php-defaults (57ubuntu1) bionic; urgency=medium
  
  * Merge with Debian unstable (LP: #1743904). Remaining changes:
- d/control, d/rules: bump to php7.1 as the default.
  + Update text of d/control to refer to Ubuntu and 7.1 as well.
  + d/control generated by `./debian/rules debian/control`

 -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Wed, 17 Jan
2018 15:55:22 -0800

** Affects: php-defaults (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Changed in: php-defaults (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php-defaults (Ubuntu)
   Status: New => In Progress

** Description changed:

- TBD
+ php-defaults (57ubuntu1) bionic; urgency=medium
+   
+   * Merge with Debian unstable (LP: #1743904). Remaining changes:
+ - d/control, d/rules: bump to php7.1 as the default.
+   + Update text of d/control to refer to Ubuntu and 7.1 as well.
+   + d/control generated by `./debian/rules debian/control`
+ 
+  -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Wed, 17 Jan
+ 2018 15:55:22 -0800

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1743904

Title:
  Please merge with Debian unstable 57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1743904/+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

[Nish Aravamudan]

** 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 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

[Nish Aravamudan]

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) is running...

Add PPA and upgrade corosync:

# add-apt-repository ppa:nacc/lp1740892
# apt-get update; apt-get install corosync

# service corosync status; service pacemaker status
 * corosync is running
pacemakerd is stopped

So what is in my PPA is not yet a fix and I think I see why:

Preparing to unpack .../corosync_2.3.3-1ubuntu4.1~ppa3_amd64.deb ...
 * Stopping corosync daemon corosync  
...
Setting up corosync (2.3.3-1ubuntu4.1~ppa3) ...
Installing new version of config file /etc/init.d/corosync ...
 * Restarting corosync daemon corosync  

   warning [MAIN  ] Could not 
lock memory of service to avoid page faults: Cannot allocate memory (12)

So the postinst change is correct and we now restart corosync instead of
start it. However, because the old package's prerm is run, that leads to
a stop of corosync which in turn causes pacemaker to exit. When we run
our updated init-script, it does not detect that pacemaker is running
and so does not restart it.

-- 
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

[Nish Aravamudan]

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 both cases, but requires different changes in each release.

I will propose similar MPs for bionic as are in xenial.

The corresponding packages are building in the PPA currentlly.

-- 
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

[Nish Aravamudan]

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 without pacemaker, so there is
no direct reverse-dependency on pacemaker for corosync.

8b) pacemaker.service already is After= and Requires= corosync.service.
This makes me less interested in the heartbeat case for 16.04+, as that
would imply administrator customization (afaict).

8c) The above stanza elements only ensure that when pacemaker.service is
started, that it is after corosync.service (After=) and ensures
corosync.service is running (Requires=). There is no expression that
would currently assert that corosync.service should start
pacemaker.service (and as mentioned in 8a, as well as based upon Trusty,
that would be incorrect).

9) It seems like what we want to express for systemd is that when
corosync.service is restarted, that pacemaker.service is restarted, if
it was running before; similar to the proposed Trusty change. I believe
PartOf would achieve this correctly, as stops are safe to propogate from
corosync to pacemaker as the systemd unit files by default have the
Requires= dependency already.

10) invoke-rc.d is the means by which both Trusty and Xenial+ end up
stopping corosync.service (prerm) and starting it (postinst) in the
maintscripts. xnox is right, I believe, that if the scripts were updated
to restart corosync.service on upgrade, rather than manually stopping
and starting them, this would be solved in coordination the PartOf=
change. However, if that is not doable in the SRU, then it might make
sense to check the status of pacemakerd in the prerm (before we stop
corosync) and ensure it is back in that state in the postinst (after we
start corosync).

11) I think the correct thing to do for Xenial is set PartOf in the
pacemaker service file.

12) For both Trusty and Xenial (the actual change may be different), we
want to ensure the corosync postinst correctly restores the state of
pacemaker regardless of the init system in place.

-- 
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

[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: `service {start,stop,restart}
{corosync,pacemaker}` where each of corosync and pacemaker can begin in
one of {started,stopped}; 3 * 2 * 2 * 2 = 24.

3) For now, I'm ignoring the case of pacemaker configured to use
heartbeat, as that is not the default in the current Ubuntu release.

4) On Trusty, 6 of those combinations are not possible by default
(corosync stopped but pacemaker running).

5) On Trusty, the only failing situation I can provoke is `service
restart corosync` when corosync and pacemaker are running already. In
all other 17 cases, the expected result is obtained with existing
packages.

6) I have submitted an MP to the Ubuntu Server Git repository for
general review and submitted a build to a PPA at:
https://launchpad.net/~nacc/+archive/ubuntu/lp1740892/, which adds a
manual SysV start of pacemaker in corosync's SysV restart logic, if
pacemaker was running before corosync was restarted. I think this is the
least likely path to affect any existing configurations. In
particularly, this does not affect the corosync start path, which may or
may not have previously started pacemaker (that is a local configuration
decision, afaict).

7) In my investigation (this relates to xnox's and other's comments),
there is no SysV link between pacemaker and corosync. Instead, pacemaker
itself quits due to not finding corosync if it's not already started.
This is why the SysV do_stop routine for corosync ends up resulting in
pacemaker stopping.

-- 
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

[Nish Aravamudan]

** Tags removed: regression-update

-- 
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 1743059] Re: Please merge with Debian unstable 1.1.18~rc4-1

[Nish Aravamudan]

** Merge proposal linked:
   
https://code.launchpad.net/~nacc/ubuntu/+source/pacemaker/+git/pacemaker/+merge/336063

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1743059

Title:
  Please merge with Debian unstable 1.1.18~rc4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1743059/+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 1743059] [NEW] Please merge with Debian unstable 1.1.18~rc4-1

[Nish Aravamudan]

Public bug reported:

pacemaker (1.1.18~rc4-1ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable (LP: #1743059). Remaining changes:
- d/control: Demote fence-agents to Suggests, avoiding main
  inclusion.
- d/control: Promote crmsh | pcs to Recommends for upgraders from
  14.04.

 -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Fri, 12 Jan
2018 16:30:04 -0800

** Affects: pacemaker (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Changed in: pacemaker (Ubuntu)
   Status: New => In Progress

** Changed in: pacemaker (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Description changed:

- TBD
+ +pacemaker (1.1.18~rc4-1ubuntu1) bionic; urgency=medium
+ +
+ +  * Merge with Debian unstable (LP: #1743059). Remaining changes:
+ +- d/control: Demote fence-agents to Suggests, avoiding main
+ +  inclusion.
+ +- d/control: Promote crmsh | pcs to Recommends for upgraders from
+ +  14.04.
+ +
+ + -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Fri, 12 Jan 2018 
16:30:04 -0800

** Description changed:

- +pacemaker (1.1.18~rc4-1ubuntu1) bionic; urgency=medium
- +
- +  * Merge with Debian unstable (LP: #1743059). Remaining changes:
- +- d/control: Demote fence-agents to Suggests, avoiding main
- +  inclusion.
- +- d/control: Promote crmsh | pcs to Recommends for upgraders from
- +  14.04.
- +
- + -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Fri, 12 Jan 2018 
16:30:04 -0800
+ pacemaker (1.1.18~rc4-1ubuntu1) bionic; urgency=medium
+ 
+   * Merge with Debian unstable (LP: #1743059). Remaining changes:
+ - d/control: Demote fence-agents to Suggests, avoiding main
+   inclusion.
+ - d/control: Promote crmsh | pcs to Recommends for upgraders from
+   14.04.
+ 
+  -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Fri, 12 Jan
+ 2018 16:30:04 -0800

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1743059

Title:
  Please merge with Debian unstable 1.1.18~rc4-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1743059/+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 1742319] Re: Please merge with Debian unstable 3.1.20-3.1

[Nish Aravamudan]

** Changed in: at (Ubuntu)
   Status: New => In Progress

** Changed in: at (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to at in Ubuntu.
https://bugs.launchpad.net/bugs/1742319

Title:
  Please merge with Debian unstable 3.1.20-3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at/+bug/1742319/+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 1597315] Re: package libapache2-mod-php7.0 7.0.4-7ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nish Aravamudan]

** Changed in: php7.0 (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1597315

Title:
  package libapache2-mod-php7.0 7.0.4-7ubuntu2.1 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/php7.0/+bug/1597315/+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 1742319] [NEW] Please merge with Debian unstable 3.1.20-3.1

[Nish Aravamudan]

Public bug reported:

TBD

** Affects: at (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to at in Ubuntu.
https://bugs.launchpad.net/bugs/1742319

Title:
  Please merge with Debian unstable 3.1.20-3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at/+bug/1742319/+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 1566519] Re: Please add native systemd units

[Nish Aravamudan]

This was fixed in Debian in 2.4.23-5, which is in Zesty+.

** Changed in: apache2 (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1566519

Title:
  Please add native systemd units

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1566519/+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

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

[Nish Aravamudan]

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 Cluster Manager...
> Jan  8 16:24:37 xenial-corosync pacemakerd[28747]:   notice: Invoking handler 
> for signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: State transition 
> S_IDLE -> S_POLICY_ENGINE [ input=I_SHUTDOWN cause=C_SHUTDOWN 
> origin=crm_shutdown ]
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Delaying fencing 
> operations until there are resources to manage
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Scheduling Node 
> xenial-corosync for shutdown
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Calculated 
> Transition 1: /var/lib/pacemaker/pengine/pe-input-52.bz2
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Transition 1 
> (Complete=1, Pending=0, Fired=0, Skipped=0, Incomplete=0, 
> Source=/var/lib/pacemaker/pengine/pe-input-52.bz2): Complete
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Disconnecting from 
> Corosync
> Jan  8 16:24:37 xenial-corosync cib[28748]:  warning: new_event_notification 
> (28748-28753-12): Broken pipe (32)
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Invoking handler 
> for signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync attrd[28751]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync lrmd[28750]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync stonith-ng[28749]:   notice: Invoking handler 
> for signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
> Corosync
> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
> Corosync
> Jan  8 16:24:37 xenial-corosync systemd[1]: Stopped Pacemaker High 
> Availability Cluster Manager.
>
>
> Pacemakerd shuts down sending SIGTERM to its components, but after the 
> install, corosync does not start pacemaker. BTW, "systemctl restart corosync" 
> restarts both services perfectly
>
> I think that the option A from James Page (#11) is the way to go

Hrm, sorry, the above isn't exactly what is relevant here. That is, if
you only issued  stop on corosync, then the above is fully correct
(and I'm not seeing the 'same' error you mention (which would be about
the library or so).

It is fully correct based upon the unit files that if you issue
`systemctl stop corosync` that you will see in the logs that pacemaker
is stopped first (the last line above shows this happening). It is not
expected that stopping corosync would cause pacemaker to restart.

If you, in the above env, issue `systemctl start corosync`, does
pacemaker start? Here is what I see in a Xenial LXD:

root@splendid-viper:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled;
vendor preset: enabled)
   Active: active (running) since Mon 2018-01-08 18:23:34 UTC; 18s ago
 Main PID: 3619 (corosync)
Tasks: 2
   Memory: 42.8M
  CPU: 329ms
   CGroup: /system.slice/corosync.service
   └─3619 /usr/sbin/corosync -f

Jan 08 18:23:34 splendid-viper corosync[3619]:   [TOTEM ] Initializing
transport (UDP/IP Multicast).
Jan 08 18:23:34 splendid-viper corosync[3619]:   [TOTEM ] Initializing
transmit/receive security (NSS) crypto: none hash: none
Jan 08 18:23:34 splendid-viper corosync[3619]:   [TOTEM ] The network
interface [127.0.0.1] is now up.
Jan 08 18:23:34 splendid-viper corosync[3619]:   [QB] server name: cmap
Jan 08 18:23:34 splendid-viper corosync[3619]:   [QB] server name: cfg
Jan 08 18:23:34 splendid-viper corosync[3619]:   [QB] server name: cpg
Jan 08 18:23:34 splendid-viper corosync[3619]:   [QB] server name:
votequorum
Jan 08 18:23:34 splendid-viper corosync[3619]:   [QB] server name: quorum
Jan 08 18:23:34 splendid-viper corosync[3619]:   [TOTEM ] A new
membership (127.0.0.1:16) was formed. Members joined: 2130706433
Jan 08 18:23:34 splendid-viper systemd[1]: Started Corosync Cluster Engine.
root@splendid-viper:~# systemctl restart corosync
root@splendid-viper:~# systemctl status corosync
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled;
vendor preset: enabled)
   Active: active (running) since Mon 2018-01-08 18:24:10 UTC; 15s ago
 Main PID: 3640 (corosync)
Tasks: 2
   Memory: 42.1M
  CPU: 263ms
   CGroup: /system.slice/corosync.service
   └─3640 /usr/sbin/corosync -f

Jan 08 18:24:10 

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

[Nish Aravamudan]

On Mon, Jan 8, 2018 at 10:04 AM, Nish Aravamudan
<nish.aravamu...@canonical.com> wrote:
> On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan
> <nish.aravamu...@canonical.com> wrote:
>> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia <victor.ta...@canonical.com> 
>> 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 Cluster Manager...
>>> Jan  8 16:24:37 xenial-corosync pacemakerd[28747]:   notice: Invoking 
>>> handler for signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Invoking handler for 
>>> signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: State transition 
>>> S_IDLE -> S_POLICY_ENGINE [ input=I_SHUTDOWN cause=C_SHUTDOWN 
>>> origin=crm_shutdown ]
>>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Delaying fencing 
>>> operations until there are resources to manage
>>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Scheduling Node 
>>> xenial-corosync for shutdown
>>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Calculated 
>>> Transition 1: /var/lib/pacemaker/pengine/pe-input-52.bz2
>>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Transition 1 
>>> (Complete=1, Pending=0, Fired=0, Skipped=0, Incomplete=0, 
>>> Source=/var/lib/pacemaker/pengine/pe-input-52.bz2): Complete
>>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Disconnecting from 
>>> Corosync
>>> Jan  8 16:24:37 xenial-corosync cib[28748]:  warning: 
>>> new_event_notification (28748-28753-12): Broken pipe (32)
>>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Invoking handler 
>>> for signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync attrd[28751]:   notice: Invoking handler 
>>> for signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync lrmd[28750]:   notice: Invoking handler for 
>>> signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync stonith-ng[28749]:   notice: Invoking 
>>> handler for signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Invoking handler for 
>>> signal 15: Terminated
>>> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
>>> Corosync
>>> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
>>> Corosync
>>> Jan  8 16:24:37 xenial-corosync systemd[1]: Stopped Pacemaker High 
>>> Availability Cluster Manager.
>>>
>>>
>>> Pacemakerd shuts down sending SIGTERM to its components, but after the 
>>> install, corosync does not start pacemaker. BTW, "systemctl restart 
>>> corosync" restarts both services perfectly
>>>
>>> I think that the option A from James Page (#11) is the way to go
>>
>> I took a quick look at a LXD container after seeing Felipe and
>> Victor's posts. It seems like this is a bug in the xenial (at least)
>> systemd unit files:
>>
>> # grep pacemaker /lib/systemd/system/corosync.service
>> #  pacemaker.service, and if you want to exert the watchdog when a
>>
>> # grep corosync /lib/systemd/system/pacemaker.service
>> After=corosync.service
>> Requires=corosync.service
>> # ExecStopPost=/bin/sh -c 'pidof crmd || killall -TERM corosync'
>>
>> So, what I see is that corosync.service has no dependency on
>> pacemaker.service (in the file).
>>
>> pacemaker.service will start after corosync.service. And when
>> pacemaker.service is shutdown it will be before corosync.service.
>> Additionally, if pacemaker.service is started, then corosync.service
>> is started as well.
>>
>> Note, nothing specifies what Felipe said -- there is no guarantee that
>> pacemaker is started, restarted, etc. when corosync is.
>>
>> I think the next step is to look at Bionic's systemd services
>> (probably newer) or upstream's and see if there is a difference, or
>> new dependencies added there.
>
> Or perhaps ask upstream what they think is providing this assurance in
> their systemd files, because I'm not seeing it.
>
> If we have a hard dependency between pacemaker and corosync, then I
> think we might need a PartOf directive, in order to ensure they are
> always following the state transitions together.

Or if that is bad (because it does feel l

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

[Nish Aravamudan]

On Mon, Jan 8, 2018 at 9:51 AM, Nish Aravamudan
<nish.aravamu...@canonical.com> wrote:
> On Mon, Jan 8, 2018 at 8:48 AM, Victor Tapia <victor.ta...@canonical.com> 
> 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 Cluster Manager...
>> Jan  8 16:24:37 xenial-corosync pacemakerd[28747]:   notice: Invoking 
>> handler for signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Invoking handler for 
>> signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: State transition 
>> S_IDLE -> S_POLICY_ENGINE [ input=I_SHUTDOWN cause=C_SHUTDOWN 
>> origin=crm_shutdown ]
>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Delaying fencing 
>> operations until there are resources to manage
>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Scheduling Node 
>> xenial-corosync for shutdown
>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Calculated 
>> Transition 1: /var/lib/pacemaker/pengine/pe-input-52.bz2
>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Transition 1 
>> (Complete=1, Pending=0, Fired=0, Skipped=0, Incomplete=0, 
>> Source=/var/lib/pacemaker/pengine/pe-input-52.bz2): Complete
>> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Disconnecting from 
>> Corosync
>> Jan  8 16:24:37 xenial-corosync cib[28748]:  warning: new_event_notification 
>> (28748-28753-12): Broken pipe (32)
>> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Invoking handler 
>> for signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync attrd[28751]:   notice: Invoking handler for 
>> signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync lrmd[28750]:   notice: Invoking handler for 
>> signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync stonith-ng[28749]:   notice: Invoking 
>> handler for signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Invoking handler for 
>> signal 15: Terminated
>> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
>> Corosync
>> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
>> Corosync
>> Jan  8 16:24:37 xenial-corosync systemd[1]: Stopped Pacemaker High 
>> Availability Cluster Manager.
>>
>>
>> Pacemakerd shuts down sending SIGTERM to its components, but after the 
>> install, corosync does not start pacemaker. BTW, "systemctl restart 
>> corosync" restarts both services perfectly
>>
>> I think that the option A from James Page (#11) is the way to go
>
> I took a quick look at a LXD container after seeing Felipe and
> Victor's posts. It seems like this is a bug in the xenial (at least)
> systemd unit files:
>
> # grep pacemaker /lib/systemd/system/corosync.service
> #  pacemaker.service, and if you want to exert the watchdog when a
>
> # grep corosync /lib/systemd/system/pacemaker.service
> After=corosync.service
> Requires=corosync.service
> # ExecStopPost=/bin/sh -c 'pidof crmd || killall -TERM corosync'
>
> So, what I see is that corosync.service has no dependency on
> pacemaker.service (in the file).
>
> pacemaker.service will start after corosync.service. And when
> pacemaker.service is shutdown it will be before corosync.service.
> Additionally, if pacemaker.service is started, then corosync.service
> is started as well.
>
> Note, nothing specifies what Felipe said -- there is no guarantee that
> pacemaker is started, restarted, etc. when corosync is.
>
> I think the next step is to look at Bionic's systemd services
> (probably newer) or upstream's and see if there is a difference, or
> new dependencies added there.

Or perhaps ask upstream what they think is providing this assurance in
their systemd files, because I'm not seeing it.

If we have a hard dependency between pacemaker and corosync, then I
think we might need a PartOf directive, in order to ensure they are
always following the state transitions together.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker 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

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

[Nish Aravamudan]

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 Cluster Manager...
> Jan  8 16:24:37 xenial-corosync pacemakerd[28747]:   notice: Invoking handler 
> for signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: State transition 
> S_IDLE -> S_POLICY_ENGINE [ input=I_SHUTDOWN cause=C_SHUTDOWN 
> origin=crm_shutdown ]
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Delaying fencing 
> operations until there are resources to manage
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Scheduling Node 
> xenial-corosync for shutdown
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Calculated 
> Transition 1: /var/lib/pacemaker/pengine/pe-input-52.bz2
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Transition 1 
> (Complete=1, Pending=0, Fired=0, Skipped=0, Incomplete=0, 
> Source=/var/lib/pacemaker/pengine/pe-input-52.bz2): Complete
> Jan  8 16:24:37 xenial-corosync crmd[28753]:   notice: Disconnecting from 
> Corosync
> Jan  8 16:24:37 xenial-corosync cib[28748]:  warning: new_event_notification 
> (28748-28753-12): Broken pipe (32)
> Jan  8 16:24:37 xenial-corosync pengine[28752]:   notice: Invoking handler 
> for signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync attrd[28751]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync lrmd[28750]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync stonith-ng[28749]:   notice: Invoking handler 
> for signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Invoking handler for 
> signal 15: Terminated
> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
> Corosync
> Jan  8 16:24:37 xenial-corosync cib[28748]:   notice: Disconnecting from 
> Corosync
> Jan  8 16:24:37 xenial-corosync systemd[1]: Stopped Pacemaker High 
> Availability Cluster Manager.
>
>
> Pacemakerd shuts down sending SIGTERM to its components, but after the 
> install, corosync does not start pacemaker. BTW, "systemctl restart corosync" 
> restarts both services perfectly
>
> I think that the option A from James Page (#11) is the way to go

I took a quick look at a LXD container after seeing Felipe and
Victor's posts. It seems like this is a bug in the xenial (at least)
systemd unit files:

# grep pacemaker /lib/systemd/system/corosync.service
#  pacemaker.service, and if you want to exert the watchdog when a

# grep corosync /lib/systemd/system/pacemaker.service
After=corosync.service
Requires=corosync.service
# ExecStopPost=/bin/sh -c 'pidof crmd || killall -TERM corosync'

So, what I see is that corosync.service has no dependency on
pacemaker.service (in the file).

pacemaker.service will start after corosync.service. And when
pacemaker.service is shutdown it will be before corosync.service.
Additionally, if pacemaker.service is started, then corosync.service
is started as well.

Note, nothing specifies what Felipe said -- there is no guarantee that
pacemaker is started, restarted, etc. when corosync is.

I think the next step is to look at Bionic's systemd services
(probably newer) or upstream's and see if there is a difference, or
new dependencies added there.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker 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

Re: [Bug 1658469] Re: [FFe] mod_http2 is not available in Apache

[Nish Aravamudan]

On Wed, Nov 22, 2017 at 5:20 AM, Mathias <1658...@bugs.launchpad.net> wrote:
> Bionic includes the /etc/apache2/mods-available/proxy_http2.load file,
> but the module mod_proxy_http2.so has been removed.
>
> Is it a mistake?
>
> Suite: Ubuntu 18.04 (bionic)
> https://packages.ubuntu.com/bionic/amd64/apache2/filelist
> https://packages.ubuntu.com/bionic/amd64/apache2-bin/filelist

To be clear provided by apache2-bin.

Note that providing links to URLs whose content changes based upon
when they are viewed is not a particularly useful practice, IMO. In
the future, show the contents, or a grep or something that indicates
what the problem is, as otherwise I'd assume it's PEBKAC.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1658469

Title:
  [FFe] mod_http2 is not available in Apache

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1658469/+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 1658469] Re: [FFe] mod_http2 is not available in Apache

[Nish Aravamudan]

This is now enabled in bionic.

** Changed in: apache2 (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1658469

Title:
  [FFe] mod_http2 is not available in Apache

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1658469/+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 1740160] Re: Please consider removing tickcount from Ubuntu

[Nish Aravamudan]

@kirkland: accumulated justifications:

1) no python3 support (not possible? per c#1) -- which implies we'd
remove it eventually anyways

2) no reverse-depends (no consumers)

3) not in Debian, so it's purely technical debt?

I haven't looked to see if there have been many/any bugs over the years,
but IMO, the above is enough for removing it.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tickcount in Ubuntu.
https://bugs.launchpad.net/bugs/1740160

Title:
  Please consider removing tickcount from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tickcount/+bug/1740160/+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

[Nish Aravamudan]

@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, which seems like it could easily be
an exported symbol / API / ABI.

afaict, there would be no harm in leaving this struct member in place,
but now unused, in the backported patch. The replacement, in the code,
is to pass this struct member in the callers themselves, but this in
turn changed the callback layout, which again might be part of the
exported interface of the library.

How easy is this to reproduce? Do you have a testcase handy that I might
be able to run?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker 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

[Nish Aravamudan]

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
Server Team, which is subscribed to pacemaker 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

Re: [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Does the Ubuntu php build use the bundled tzdata? A lot of stuff comes from
the system not the source (e.g, pcre iirc)

On Dec 1, 2017 18:40, "Eric Desrochers" 
wrote:

> Same thing with new php pkg release in debian/unstable (php - 7.1.12-1).
> It still displays America/Sao_Paulo
>
> That exclude my theory about the tz bundle update. I'll do a proper
> bisect next week.
>
> - Eric
>
> --
> You received this bug notification because you are subscribed to php7.1
> in Ubuntu.
> Matching subscriptions: PHP7.0
> https://bugs.launchpad.net/bugs/1734967
>
> Title:
>   tzdata info for WGT/WGST broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1734967

Title:
  tzdata info for WGT/WGST broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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

Re: [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Is this already fixed in proposed (MRE to latest upstream php 7.0 and
7.1)?

On Dec 1, 2017 03:48, "Bug Watch Updater" <1734...@bugs.launchpad.net>
wrote:

> ** Changed in: php7.0 (Debian)
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to php7.1
> in Ubuntu.
> Matching subscriptions: PHP7.0
> https://bugs.launchpad.net/bugs/1734967
>
> Title:
>   tzdata info for WGT/WGST broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1734967

Title:
  tzdata info for WGT/WGST broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Just to be clear, this isn't a bug based upon comment 1 but new tasks
were opened in comment 2?

If it's purely an SRU regression in tzdata that should be figured out.

Im guessing this is an upstream php issue. Has it been fixed there?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1734967

Title:
  tzdata info for WGT/WGST broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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 1732918] Re: iscsitarget-dkms 1.4.20.3+svn502-2ubuntu4.4 doesn't build for Xenial hwe (4.10) kernel

[Nish Aravamudan]

You dont' need iscsitarget-dkms on any new kernel.

https://bugs.launchpad.net/bugs/1668808

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iscsitarget in Ubuntu.
https://bugs.launchpad.net/bugs/1732918

Title:
  iscsitarget-dkms 1.4.20.3+svn502-2ubuntu4.4 doesn't build for Xenial
  hwe (4.10) kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1732918/+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 1729036] Re: [MRE] Please update to latest upstream release 7.1.11

[Nish Aravamudan]

Performed my normal LXD verification by upgrade php7.1 in a 17.10
container.

# apt policy php7.1
php7.1:
  Installed: 7.1.11-0ubuntu0.17.10.1
  Candidate: 7.1.11-0ubuntu0.17.10.1
  Version table:
 *** 7.1.11-0ubuntu0.17.10.1 500
500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 7.1.8-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

Upgrade was successful.

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1729036

Title:
  [MRE] Please update to latest upstream release 7.1.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1729036/+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

[Nish Aravamudan]

Brian, was there any problem with the 16.04 upload, or were you letting
17.04 shake out any issues first?

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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

[Nish Aravamudan]

Performed my normal LXD verification for an upgrade in 17.04 from
7.0.22-0ubuntu0.17.04.1 to 7.0.25-0ubuntu0.17.04.1.

root@fluent-grouse:~# apt policy php7.0
php7.0:
  Installed: 7.0.25-0ubuntu0.17.04.1
  Candidate: 7.0.25-0ubuntu0.17.04.1
  Version table:
 *** 7.0.25-0ubuntu0.17.04.1 500
500 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 7.0.22-0ubuntu0.17.04.1 500
500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 Packages
 7.0.15-1ubuntu4 500
500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages


** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

-- 
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

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

I'm guessing this might be a quirk of the armhf runners:

test_tree_garbage (__main__.ChrootRunner)
copied source tree contains only expected files ... : Operation not permitted
cp: cannot create special file ‘/tmp/tmp36ee0r77/chroot//dev/null’:
Operation not permitted
cp: cannot create special file ‘/tmp/tmplo89rot6/chroot//dev/null’:
Operation not permitted
cp: cannot create special file ‘/tmp/tmpsd8_r783/chroot//dev/null’:
Operation not permitted
ERROR
test_tree_norestrictions_nobuild_fail_on_exit (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with non-zero ... ERROR
test_tree_norestrictions_nobuild_fail_on_stderr (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with stderr ... ERROR
test_tree_norestrictions_nobuild_fail_on_stderr_and_exit (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with stderr+exit ... ERROR

I'll see if it might need some restrictions (or if the runner env
changed)?

-Nish

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

If someone is interested in the proper upstream fixes, please file a new
bug and we will need to fix bionic and prepare a distinct SRU for the
existing releases.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1712441] Re: pacemaker 1.1.17-1ubuntu1 FTBFS

[Nish Aravamudan]

I just uploaded

https://launchpad.net/ubuntu/+source/pacemaker/1.1.18~rc3-1ubuntu1

which has the fix from Debian for the corresponding bug (I'm not sure
why the Debian bug hasn't been closed).

I'm not sure if it's worth SRU'ing it or not. I suppose to artful-
proposed, at least, it is, since the uploaded version is broken there.
I'll see if I can do that shortly.

** Also affects: pacemaker (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: pacemaker (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: pacemaker (Ubuntu)
   Status: New => Fix Released

** No longer affects: pacemaker (Ubuntu Zesty)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pacemaker in Ubuntu.
https://bugs.launchpad.net/bugs/1712441

Title:
  pacemaker 1.1.17-1ubuntu1 FTBFS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1712441/+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

[Nish Aravamudan]

** Description changed:

  There have been a number of microreleases of PHP 7.0 upstream since the
  last update to Xenial (which corresponded to the last update in Zesty). As
  it has been a few months, it feels appropriate to provide another
  MRE update to php7.0. A number of critical security and bug-fixes are
  present in each 7.0.x. Rather than backporting individual patches (e.g.,
  Bug # 1569509), I believe it makes significantly more sense to follow
  the upstream 7.0.x. Upstream PHP is demonstrating an improved approach
  of bugfixes only in 7.0.x:
  
-  - 7.0.24: http://php.net/ChangeLog-7.php
+  - 7.0.25: http://php.net/ChangeLog-7.php
  
  The upstream CI is at: https://travis-ci.org/php/php-src and is run
  regularly.
  
  Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
  cgi, fpm and cli. We have also updated the packing to run the source
  tests during the build itself.
  
  I do not believe there is a firm statement from upstream on API/ABI
  stability, but the general approach seems to be a BC-break would result
  in 7.1.0 (which is present in Artful, and is why the Artful task is invalid).

-- 
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

[Nish Aravamudan]

** Also affects: php7.0 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: php7.0 (Ubuntu Zesty)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php7.0 (Ubuntu Zesty)
   Status: New => In Progress

-- 
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

[Nish Aravamudan]

** Summary changed:

- [MRE] Please update to latest upstream release 7.0.24
+ [MRE] Please update to latest upstream release 7.0.25

** No longer affects: php7.0 (Ubuntu Trusty)

-- 
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

Re: [Bug 1729064] Re: package bacula-director-pgsql 7.0.5+dfsg-4ubuntu0.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Nish Aravamudan]

On Wed, Nov 1, 2017 at 7:26 AM, Andreas Hasenack  wrote:
> It worked out of the box in artful, so the fix is somewhere in between
> xenial and artful.

I would check the changes in 7.4.1~dfsg-1 or 7.4.2+dfsg-1 or
7.4.3+dfsg-1.

Also, iirc (only vaguely possibly true), bacula-director-pgsql only
depends on a postgres client, not on a postgres server. So is this
with an --install-recommends installation?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1729064

Title:
  package bacula-director-pgsql 7.0.5+dfsg-4ubuntu0.1 failed to
  install/upgrade: sub-processo script post-installation instalado
  retornou estado de saída de erro 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1729064/+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

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <1720...@bugs.launchpad.net> wrote:
> @arges
>
> Hi, would you need any more testing from us?

Nope, your part is done. All SRUs have to bake for 7 days in -proposed
to shake out regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1729036] [NEW] [MRE] Please update to latest upstream release 7.1.11

[Nish Aravamudan]

Public bug reported:

There have been a number of microreleases of PHP 7.1 upstream since the last 
update to Artful. As
it has been a few months, it feels appropriate to provide a MRE update to 
php7.1. A number of critical security and bug-fixes are present in each 7.1.x. 
Rather than backporting individual patches, I believe it makes significantly 
more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an 
improved approach of bugfixes only in 7.1.x:

 - 7.1.11: http://php.net/ChangeLog-7.php

The upstream CI is at: https://travis-ci.org/php/php-src and is run
regularly.

Our php7.1 source package has autopkgtests for the 4 SAPIs, mod-php,
cgi, fpm and cli. We have also updated the packaging to run the source
tests during the build itself.

I do not believe there is a firm statement from upstream on API/ABI
stability, but the general approach seems to be a BC-break would result
in 7.2.0.

We already had an MRE for php7.0 in X and Y, and this is the
corresponding source package in AA.

** Affects: php7.1 (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Affects: php7.1 (Ubuntu Artful)
 Importance: Undecided
 Status: New

** Affects: php7.1 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Changed in: php7.1 (Ubuntu)
   Status: New => In Progress

** Changed in: php7.1 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Also affects: php7.1 (Ubuntu Bionic)
   Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
   Status: In Progress

** Also affects: php7.1 (Ubuntu Artful)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1729036

Title:
  [MRE] Please update to latest upstream release 7.1.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1729036/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

** No longer affects: php7.1 (Ubuntu Artful)

** Summary changed:

- [MRE] Please update to latest upstream release 7.1.10
+ Please update to latest upstream release 7.1.10

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

Thanks for letting me know. I'll do an update to 7.1.11 shortly for
bionic and then work with the security team to replace the update in
artful.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1283

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

Are you referring to:

PCRE:
Fixed bug #75207 (applied upstream patch for CVE-2016-1283).

?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

I asked Steve Langasek to reject the unapproved upload of php7.1 so that
I can do a proper SRU version, now that Bionic is open.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1721607] Re: please update to latest upstream release 7.0.24

[Nish Aravamudan]

Just an FYI that I have uploaded an update to php7.0 for x and z and
php7.1 for aa (which should get copied to bb, but bb will end up with
7.2 before release), but not as a security update. It will go through
the normal SRU process before being available.

-- 
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/1721607

Title:
  please update to latest upstream release 7.0.24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1721607/+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

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote:
> On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> > I had a look at the two proposals and could not spot any obvious
> > mistakes:
> > 
> > - the correct upstream git commit has been cherry-picked
> > - I don't have any objections to attribution or log messages
> > 
> > Thanks again for shepherding this one through!
> 
> You're welcome, I'll upload them both today.
> 
> Thank you and Monique for filing the SRU template properly!

I have sponsored both packages. They will need to be approved by an SRU
team member (probably next week) before they appear in
{trusty,xenial}-proposed and then they will need testing as built in
proposed, with a minimum bake time of 7 days in proposed.

Thank you and Monique for your contribution to Ubuntu!

-Nish

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> I had a look at the two proposals and could not spot any obvious
> mistakes:
> 
> - the correct upstream git commit has been cherry-picked
> - I don't have any objections to attribution or log messages
> 
> Thanks again for shepherding this one through!

You're welcome, I'll upload them both today.

Thank you and Monique for filing the SRU template properly!

-Nish

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 20.10.2017 [07:09:00 -], Jan Gutter wrote:
> I concur with option 2), unnecessary deviation will just cause
> confusion.

Thank you for confirming that!

> Regarding the other buffer sizes, the last time I looked they were
> mostly OK. The issue reared its head in this particular case because the
> netlink message that previously had a pretty constant per-netdev
> response size suddenly had the ability to balloon with "no warning". A
> number of workarounds exist (i.e. you have to explicitly ask for the VF
> info), but, in this case we actually want the VF info and iproute2 was
> just unprepared for the size of it.

Ok, that's good to hear.

> I guess the core issue is that it's entirely possible for the kernel to
> add extra netlink attributes to any query response, iproute2 makes the
> assumption that the queries it's making is not necessarily going to
> explode with gigabytes of new annotations and 16k will easily fit any
> current real-world system. A pragmatic approach would probably be to
> handle the "Message Truncated" path with a dynamically sized buffer as
> an exceptional case.

Yep, I can see how iproute2 itself has to move in lockstep with the
kernel, which also means older iproute2 that can run on newer kernels
needs periodic updates like this one.

> Any fix in iproute2 that "properly" addresses this issue has to be
> carefully vetted. Who knows how many inherent races will get exposed if
> the ip command doubles in execution time.

Yep :) I'm fine with eventually doubling the buffer again statically if
that is the conclusion upstream reaches. My guess is that is the
simplest solution.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

I have set up two MPs with the adjustments (it looks like Monique's
latest debdiffs followed path 2) from my previous comment already) to
the DEP3 headers that I think make the most sense. Please take a look at
them and if you approve the changes I will upload them.

I note also there are a number of statically sized buffers in the
iproute2 code -- is there any concern about other buffers overflowing?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

** Description changed:

  There have been a number of microreleases of PHP 7.1 upstream since the last 
update to Artful. As
  it has been a few months, it feels appropriate to provide a MRE update to 
php7.1. A number of critical security and bug-fixes are present in each 7.1.x. 
Rather than backporting individual patches, I believe it makes significantly 
more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an 
improved approach of bugfixes only in 7.1.x:
  
   - 7.1.10: http://php.net/ChangeLog-7.php
  
  The upstream CI is at: https://travis-ci.org/php/php-src and is run
  regularly.
  
- Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
+ Our php7.1 source package has autopkgtests for the 4 SAPIs, mod-php,
  cgi, fpm and cli. We have also updated the packaging to run the source
  tests during the build itself.
  
  I do not believe there is a firm statement from upstream on API/ABI
  stability, but the general approach seems to be a BC-break would result
  in 7.2.0.
+ 
+ We already had an MRE for php7.0 in X and Y, and this is the
+ corresponding source package in AA.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

I will probably SRU this ahead of BB opening, which will imply we'll
need a copy-forward for BB.

** Changed in: php7.1 (Ubuntu Bb-series)
   Status: Invalid => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1724902] Re: [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

** Changed in: php7.1 (Ubuntu Artful)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php7.1 (Ubuntu Bb-series)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: php7.1 (Ubuntu Bb-series)
   Status: New => In Progress

** Changed in: php7.1 (Ubuntu Artful)
   Status: New => In Progress

** Changed in: php7.1 (Ubuntu Bb-series)
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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 1724902] [NEW] [MRE] Please update to latest upstream release 7.1.10

[Nish Aravamudan]

Public bug reported:

There have been a number of microreleases of PHP 7.1 upstream since the last 
update to Artful. As
it has been a few months, it feels appropriate to provide a MRE update to 
php7.1. A number of critical security and bug-fixes are present in each 7.1.x. 
Rather than backporting individual patches, I believe it makes significantly 
more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an 
improved approach of bugfixes only in 7.1.x:

 - 7.1.10: http://php.net/ChangeLog-7.php

The upstream CI is at: https://travis-ci.org/php/php-src and is run
regularly.

Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
cgi, fpm and cli. We have also updated the packaging to run the source
tests during the build itself.

I do not believe there is a firm statement from upstream on API/ABI
stability, but the general approach seems to be a BC-break would result
in 7.2.0.

** Affects: php7.1 (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Affects: php7.1 (Ubuntu Artful)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Affects: php7.1 (Ubuntu Bb-series)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Also affects: php7.1 (Ubuntu Bb-series)
   Importance: Undecided
   Status: New

** Also affects: php7.1 (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Description changed:

  There have been a number of microreleases of PHP 7.1 upstream since the last 
update to Artful. As
  it has been a few months, it feels appropriate to provide a MRE update to 
php7.1. A number of critical security and bug-fixes are present in each 7.1.x. 
Rather than backporting individual patches, I believe it makes significantly 
more sense to follow the upstream 7.1.x. Upstream PHP is demonstrating an 
improved approach of bugfixes only in 7.1.x:
  
-  - 7.1.10: http://php.net/ChangeLog-7.php
+  - 7.1.10: http://php.net/ChangeLog-7.php
  
  The upstream CI is at: https://travis-ci.org/php/php-src and is run
  regularly.
  
  Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
  cgi, fpm and cli. We have also updated the packaging to run the source
  tests during the build itself.
  
  I do not believe there is a firm statement from upstream on API/ABI
  stability, but the general approach seems to be a BC-break would result
- in 7.2.0 (which will probably be present in BB once released, which is
- why there is no BB task).
+ in 7.2.0.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php7.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1724902

Title:
  [MRE] Please update to latest upstream release 7.1.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1724902/+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] [NEW] [MRE] Please update to latest upstream release 7.0.24

[Nish Aravamudan]

Public bug reported:

There have been a number of microreleases of PHP 7.0 upstream since the
last update to Xenial (which corresponded to the last update in Zesty). As
it has been a few months, it feels appropriate to provide another
MRE update to php7.0. A number of critical security and bug-fixes are
present in each 7.0.x. Rather than backporting individual patches (e.g.,
Bug # 1569509), I believe it makes significantly more sense to follow
the upstream 7.0.x. Upstream PHP is demonstrating an improved approach
of bugfixes only in 7.0.x:

 - 7.0.24: http://php.net/ChangeLog-7.php

The upstream CI is at: https://travis-ci.org/php/php-src and is run
regularly.

Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php,
cgi, fpm and cli. We have also updated the packing to run the source
tests during the build itself.

I do not believe there is a firm statement from upstream on API/ABI
stability, but the general approach seems to be a BC-break would result
in 7.1.0 (which is present in Artful, and is why the Artful task is invalid).

** Affects: php7.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: php7.0 (Ubuntu Trusty)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Affects: php7.0 (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: In Progress

** Also affects: php7.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: php7.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: php7.0 (Ubuntu)
   Status: New => Invalid

** Changed in: php7.0 (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: php7.0 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: php7.0 (Ubuntu Trusty)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** 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/1724896

Title:
  [MRE] Please update to latest upstream release 7.0.24

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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

@mvandenberg,

Couple of nits in your debdiffs.

1) changelogs are targetting UNRELEASED, please update to xenial and
trusty respectively.

2) Is there a reason your fix is different than the fix upstream/Debian?
Does Debian need your version instead?

3) Please use appropriate DEP3 headers (dpkg-source --commit creates a
template patch with them): http://dep.debian.net/deps/dep3/, especially
Origin (not Origin/Author).

4) The actual author appears to be Phil Sutter, not Jan Gutter, although
Jan authored the patch in this bug. Consider using dep3changelog once
you have a quilt patch to generate the changelog in the standard format
(with an attribution to Phil or Jan as you decide).

5) The trusty version number seems off, it should be 3.12.0-2ubuntu1.1.
Please take a look at
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging.

Can you fix these up and reupload the debdiffs?

Thanks,
Nish

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 17.10.2017 [08:56:17 -], Jan Gutter wrote:
> @nacc I built from source to verify that the one-liner is directly
> responsible for fixing and breaking the issue (inherent paranoia). I did
> test with the binaries and they worked.

Ah ok, yeah -- I guess that's reasonable, and is a good preemptive test,
but given that it needs to be backported to a different release, feels a
bit like busywork (the same time could have been spent building it for
xenial :)

> Apologies, I'm unfamiliar with the Ubuntu SRU process as you can
> probably see. What exactly is an "MP" and how would one go about to
> propose one?

MP = Merge Proposal. Roughly like GitHub's Pull Requests (PR), except
less formal with Git (bzr I think is somewhat more first-class in
Launchpad).

> I'm aware of the need of testing bugfixes like these, I'm not familiar
> with your release pipeline, however.

http://www.justgohome.co.uk/blog/2017/07/developing-ubuntu-using-
git.html

may help a bit. Roughly:

$ sudo snap install --classic git-ubuntu
$ git ubuntu clone iproute2
$ cd iproute2
$ ... make and commit changes
$ git ubuntu submit

Now, the issue is that middle bit, where you have to know a bit about
source packaging. That is, simply cherry-picking the upstream/Debian fix
is not quite right, as you need to change it into a Quilt patch and then
insert a changelog entry.

We are currently developing a fix for that so you can just do a

$ git ubuntu remote add debian
$ git cherry-pick 72b365e83
$ git ubuntu build-source

And it should spit out a commit that has the quiltify'd and
changelogify'd result that you can use as a base or to submit.

Feel free to find me on IRC if you want some more pointers.

In the meanwhile, I'll try and look at Monique's debdiffs this week.

-Nish

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720029] Re: Backport "Re-enable SSL support by default. Compatibility with older versions has been fixed." to zesty.

[Nish Aravamudan]

Hello and thank you again for the report. I am looking at the fix, and
the NEWS and changelog files say:

+  The bug that caused the SSL support between NRPE 2.x and 3.x not
+  to work has been fixed.

What bug? Where was it fixed? Will updating just nagios-nrpe break
existing 17.04 installs?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-nrpe in Ubuntu.
https://bugs.launchpad.net/bugs/1720029

Title:
  Backport "Re-enable SSL support by default. Compatibility with older
  versions has been fixed." to zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1720029/+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 1721607] Re: please update to latest upstream release 7.0.24

[Nish Aravamudan]

Thank Tyler :)

Steven,

a) The patched version from Ondrej's repo is not an official, nor
supported version, it's irrelevant to this discussion.

b) If you can provide the CVEs that Tyler asked for, then a security
update will occur.

c) We do have an MRE for PHP7.0 (probably also for PHP7.1 by the same
logic) and I plan on submitting an update to the latest PHP7.0 upstream
in the next week or two. But that will only be present in -updates, not
-security unless b) is addressed.

Sorry for the delay on my end in replying to this bug.

-- 
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/1721607

Title:
  please update to latest upstream release 7.0.24

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1721607/+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 1721468] Re: Free invalid pointer crash in vnc

[Nish Aravamudan]

@berrange, if so, can @peter-sabaini verify that it is fixed in 17.04
(2.8 based) and Artful (2.10 based).

** Changed in: qemu (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1721468

Title:
  Free invalid pointer crash in vnc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1721468/+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 1719671] Re: [SRU][xenial] include fips enablement into ubuntu-advantage

[Nish Aravamudan]

After chatting on IRC, this was fixed in Artful in LP: #1718291.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Fix Released

** Also affects: ubuntu-advantage-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Zesty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1719671

Title:
  [SRU][xenial] include fips enablement into ubuntu-advantage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

@jangutter: I'm not sure why you built from source? I assume you
actually tested the version in 17.04 and it worked.

The proper solution is to backport the Debian change to xenial and
trusty, most likely. A git repository that can be used with `git-ubuntu`
(sudo snap install --classic git-ubuntu`) is available here:
https://code.launchpad.net/~usd-import-
team/ubuntu/+source/iproute2/+git/iproute2

Feel free to propose MPs against ubuntu/xenial-devel and ubuntu/trusty-
devel, or I can do it if you'd prefer.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1721546] Re: max open files limit prevents max_connections over 214 on systemd

[Nish Aravamudan]

Should this be fixed in Debian? Or at least reported there? So that it
does not add to the delta?

And is the underlying proposed fix to add the Service LimitNOFILE change
to the default mysql service file?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.7 in Ubuntu.
Matching subscriptions: main
https://bugs.launchpad.net/bugs/1721546

Title:
  max open files limit prevents max_connections over 214 on systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1721546/+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 1719671] Re: [SRU][xenial] include fips enablement into ubuntu-advantage

[Nish Aravamudan]

@j-latten: It's unclear to me if this is actually intended for all
releases (based upon the nominated tasks by Manoj and Andreas) or just
Xenial (based upon the bug description). Can you clarify?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1719671

Title:
  [SRU][xenial] include fips enablement into ubuntu-advantage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1719671/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

** Also affects: iproute2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: iproute2 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: iproute2 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: iproute2 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: iproute2 (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: iproute2 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: iproute2 (Ubuntu)
   Importance: High => Undecided

** Also affects: iproute2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1720126

Title:
  [ip link] Message truncated error for large number of passthrough VFs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1722808] Re: update to 2.10.1 point release

[Nish Aravamudan]

@paelzer, should this be assigned to you? Not sure if there is an
explicit request here for someone else to pick this up?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1722808

Title:
  update to 2.10.1 point release

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1722808/+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 1718291] Re: [FFe]: Include FIPS into the ubuntu-advantage tool

[Nish Aravamudan]

Sponsored.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1718291

Title:
  [FFe]: Include FIPS into the ubuntu-advantage tool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1718291/+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