Activity log for bug #1840347

Date Who What changed Old value New value Message
2019-08-15 18:31:30 Kellen Renshaw bug added bug
2019-08-15 18:41:16 Dan Hill description Upgrading from 12.2.11-0ubuntu0.18.04.2 to 12.2.12-0ubuntu0.18.04.1 on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then if [ -d /run/systemd/system ]; then systemctl --system daemon-reload >/dev/null || true if [ -n "$2" ]; then _dh_action=restart else _dh_action=start fi deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true fi fi # End automatically added section ``` 2019-08-15 10:49:18 upgrade ceph-common:amd64 12.2.11-0ubuntu0.18.04.2 12.2.12- ... 2019-08-15 10:49:29 configure ceph-common:amd64 12.2.12-0ubuntu0.18.04.1 <none> .. 2019-08-15 10:49:56 status installed ceph-common:amd64 12.2.12-0ubuntu0.18.04.1 Upgrading from 12.2.11-0ubuntu0.18.04.2 to 12.2.12-0ubuntu0.18.04.1 on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section dpkg.log after the upgrade shows that "configure" was exercised: 2019-08-15 10:49:18 upgrade ceph-common:amd64 12.2.11-0ubuntu0.18.04.2 12.2.12- ... 2019-08-15 10:49:29 configure ceph-common:amd64 12.2.12-0ubuntu0.18.04.1 <none> .. 2019-08-15 10:49:56 status installed ceph-common:amd64 12.2.12-0ubuntu0.18.04.1
2019-08-15 19:36:15 Eric Desrochers bug added subscriber Eric Desrochers
2019-08-15 19:38:07 Eric Desrochers tags sts
2019-08-15 19:38:22 Eric Desrochers ceph (Ubuntu): importance Undecided High
2019-08-16 01:33:53 Eric Desrochers bug added subscriber Jesse Williamson
2019-08-16 01:34:03 Eric Desrochers bug added subscriber Dan Hill
2019-08-19 17:31:17 Launchpad Janitor ceph (Ubuntu): status New Confirmed
2019-08-19 17:31:31 Pedro Principeza bug added subscriber Pedro Principeza
2019-08-20 00:11:47 Eric Desrochers ceph (Ubuntu): status Confirmed In Progress
2019-08-20 00:11:49 Eric Desrochers ceph (Ubuntu): assignee Eric Desrochers (slashd)
2019-08-20 12:44:26 Eric Desrochers nominated for series Ubuntu Eoan
2019-08-20 12:44:26 Eric Desrochers bug task added ceph (Ubuntu Eoan)
2019-08-20 12:44:26 Eric Desrochers nominated for series Ubuntu Disco
2019-08-20 12:44:26 Eric Desrochers bug task added ceph (Ubuntu Disco)
2019-08-20 12:44:26 Eric Desrochers nominated for series Ubuntu Bionic
2019-08-20 12:44:26 Eric Desrochers bug task added ceph (Ubuntu Bionic)
2019-08-20 12:44:37 Eric Desrochers ceph (Ubuntu Bionic): importance Undecided High
2019-08-20 12:44:39 Eric Desrochers ceph (Ubuntu Eoan): importance High Medium
2019-08-20 12:45:14 Eric Desrochers ceph (Ubuntu Disco): assignee Eric Desrochers (slashd)
2019-08-20 12:45:24 Eric Desrochers ceph (Ubuntu Bionic): assignee Eric Desrochers (slashd)
2019-08-20 12:45:28 Eric Desrochers ceph (Ubuntu Disco): importance Undecided Medium
2019-08-20 12:45:41 Eric Desrochers ceph (Ubuntu Disco): status New In Progress
2019-08-20 12:45:43 Eric Desrochers ceph (Ubuntu Bionic): status New In Progress
2019-08-20 12:57:36 Eric Desrochers description Upgrading from 12.2.11-0ubuntu0.18.04.2 to 12.2.12-0ubuntu0.18.04.1 on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section dpkg.log after the upgrade shows that "configure" was exercised: 2019-08-15 10:49:18 upgrade ceph-common:amd64 12.2.11-0ubuntu0.18.04.2 12.2.12- ... 2019-08-15 10:49:29 configure ceph-common:amd64 12.2.12-0ubuntu0.18.04.1 <none> .. 2019-08-15 10:49:56 status installed ceph-common:amd64 12.2.12-0ubuntu0.18.04.1 [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] [Other Informations]
2019-08-20 19:28:18 Eric Desrochers description [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] [Other Informations] [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred. The goal is for the admin to choose when (and which) ceph services move to the new code level. [Other Information]
2019-08-21 00:14:35 Launchpad Janitor merge proposal linked https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371549
2019-08-21 00:20:08 Launchpad Janitor merge proposal linked https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371550
2019-08-21 00:25:47 Launchpad Janitor merge proposal linked https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371551
2019-08-27 00:25:18 Eric Desrochers description [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred. The goal is for the admin to choose when (and which) ceph services move to the new code level. [Other Information] [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred, not 2 (1 due to ceph postinst and 1 for the reboot (to load new kernel) for instance). The goal is for the admin to choose when (and which) ceph services move to the new code level. [Other Information]
2019-08-27 00:25:33 Eric Desrochers description [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred, not 2 (1 due to ceph postinst and 1 for the reboot (to load new kernel) for instance). The goal is for the admin to choose when (and which) ceph services move to the new code level. [Other Information] [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred, not 2 (1 due to ceph postinst and 1 for the reboot (to load new kernel) for instance). The goal is for the admin to choose when (and which) ceph services move to the new code level, after upgrading the package. [Other Information]
2019-08-27 00:30:04 Eric Desrochers description [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred, not 2 (1 due to ceph postinst and 1 for the reboot (to load new kernel) for instance). The goal is for the admin to choose when (and which) ceph services move to the new code level, after upgrading the package. [Other Information] [Impact] Upgrading from ceph on Ubuntu 18.04 causes the ceph-osd services to be restarted without prompting. This appears to be in the configure section on the ceph-common,postinst: # Automatically added by dh_systemd_start/11.1.6ubuntu2 if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then         if [ -d /run/systemd/system ]; then                 systemctl --system daemon-reload >/dev/null || true                 if [ -n "$2" ]; then                         _dh_action=restart                 else                         _dh_action=start                 fi                 deb-systemd-invoke $_dh_action 'ceph.target' >/dev/null || true         fi fi # End automatically added section This is a change of behaviour compare to debhelper 9. --restart-after-upgrade is the default in compat 10. The expected behavior during a package upgrade is to leave all the ceph service states unmodified. They should not be enabled/disabled or stopped/started. [Test Case] * Check pid of ceph-osd (before upgrade) * sudo apt-get update * sudo apt-get upgrade * Check pid of ceph-osd (after upgrade) If the pid changes, it means ceph-osd has been restarted, and the restart or stop/start has been exercised. [Potential Regression] Low, the desire is to control the precise timing of the restart. The larger context is that there may multiple updates (in this case kernel) and one want a single stop/start when the reboot occurred, not 2 (1 due to ceph postinst and 1 for the reboot (to load new kernel) for instance). The goal is for the admin to choose when (and which) ceph services move to the new code level, after upgrading the package. [Other Information] Ubuntu ceph package uses a more modern version of dh (10) as oppose to ceph upstream which uses dh 9[0]. Ceph package also doesn't exclude any ceph services like Ubuntu does[1] Upstream ceph doesn't have the restart behaviour because they are not there yet (dh 10),but they are likely to take the same road as we do as they upgrade debhelper. [0] https://github.com/ceph/ceph/blob/master/debian/control#L15 [1] https://github.com/ceph/ceph/blob/master/debian/rules#L86
2019-08-27 15:22:42 Launchpad Janitor merge proposal linked https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371886
2019-08-27 15:25:50 Launchpad Janitor merge proposal linked https://code.launchpad.net/~slashd/ubuntu/+source/ceph/+git/ceph/+merge/371887
2019-08-28 16:17:16 James Page bug added subscriber Ubuntu Stable Release Updates Team
2019-08-29 07:52:36 James Page ceph (Ubuntu Disco): importance Medium High
2019-08-29 07:52:38 James Page ceph (Ubuntu Eoan): importance Medium High
2019-08-29 22:25:41 Launchpad Janitor ceph (Ubuntu Eoan): status In Progress Fix Released
2019-08-29 22:25:41 Launchpad Janitor cve linked 2019-10222
2019-08-30 06:27:15 Alvaro Uria bug added subscriber Canonical IS BootStack
2019-08-30 06:27:26 Alvaro Uria tags sts canonical-bootstack sts
2019-08-30 06:27:42 Alvaro Uria bug added subscriber The Canonical Sysadmins
2019-08-30 06:36:18 Trent Lloyd bug added subscriber Trent Lloyd
2019-08-30 10:04:39 James Page bug task added cloud-archive
2019-08-30 10:04:50 James Page nominated for series cloud-archive/queens
2019-08-30 10:04:50 James Page bug task added cloud-archive/queens
2019-08-30 10:04:50 James Page nominated for series cloud-archive/stein
2019-08-30 10:04:50 James Page bug task added cloud-archive/stein
2019-08-30 10:04:50 James Page nominated for series cloud-archive/train
2019-08-30 10:04:50 James Page bug task added cloud-archive/train
2019-08-30 10:04:50 James Page nominated for series cloud-archive/rocky
2019-08-30 10:04:50 James Page bug task added cloud-archive/rocky
2019-08-30 10:04:57 James Page cloud-archive/train: status New In Progress
2019-08-30 10:05:00 James Page cloud-archive/stein: status New In Progress
2019-08-30 10:05:02 James Page cloud-archive/rocky: status New In Progress
2019-08-30 10:05:05 James Page cloud-archive/queens: status New In Progress
2019-08-30 10:05:11 James Page cloud-archive/train: importance Undecided High
2019-08-30 10:05:13 James Page cloud-archive/stein: importance Undecided High
2019-08-30 10:05:14 James Page cloud-archive/rocky: importance Undecided High
2019-08-30 10:05:16 James Page cloud-archive/queens: importance Undecided High
2019-08-30 10:08:05 James Page cve unlinked 2019-10222
2019-08-30 10:08:25 James Page cloud-archive/train: assignee James Page (james-page)
2019-08-30 10:08:27 James Page cloud-archive/stein: assignee James Page (james-page)
2019-08-30 10:08:29 James Page cloud-archive/rocky: assignee James Page (james-page)
2019-08-30 10:08:31 James Page cloud-archive/queens: assignee James Page (james-page)
2019-09-05 12:32:57 Łukasz Zemczak ceph (Ubuntu Disco): status In Progress Fix Committed
2019-09-05 12:33:00 Łukasz Zemczak bug added subscriber SRU Verification
2019-09-05 12:33:05 Łukasz Zemczak tags canonical-bootstack sts canonical-bootstack sts verification-needed verification-needed-disco
2019-09-05 12:39:17 Łukasz Zemczak ceph (Ubuntu Bionic): status In Progress Fix Committed
2019-09-05 12:39:25 Łukasz Zemczak tags canonical-bootstack sts verification-needed verification-needed-disco canonical-bootstack sts verification-needed verification-needed-bionic verification-needed-disco
2019-09-05 17:30:58 Eric Desrochers tags canonical-bootstack sts verification-needed verification-needed-bionic verification-needed-disco canonical-bootstack sts verification-done-bionic verification-needed verification-needed-disco
2019-09-05 18:21:06 Eric Desrochers tags canonical-bootstack sts verification-done-bionic verification-needed verification-needed-disco canonical-bootstack sts verification-done-bionic verification-done-disco verification-needed
2019-09-06 07:30:35 James Page cloud-archive/rocky: status In Progress Fix Committed
2019-09-06 07:30:38 James Page tags canonical-bootstack sts verification-done-bionic verification-done-disco verification-needed canonical-bootstack sts verification-done-bionic verification-done-disco verification-needed verification-rocky-needed
2019-09-06 07:30:54 James Page cloud-archive/train: status In Progress Fix Committed
2019-09-06 07:31:49 James Page cloud-archive/stein: status In Progress Fix Committed
2019-09-06 07:31:54 James Page tags canonical-bootstack sts verification-done-bionic verification-done-disco verification-needed verification-rocky-needed canonical-bootstack sts verification-done-bionic verification-done-disco verification-needed verification-rocky-needed verification-stein-needed
2019-09-09 13:28:39 Edward Hope-Morley tags canonical-bootstack sts verification-done-bionic verification-done-disco verification-needed verification-rocky-needed verification-stein-needed canonical-bootstack sts sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-rocky-needed verification-stein-needed
2019-09-23 09:18:11 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2019-09-23 09:28:03 Launchpad Janitor ceph (Ubuntu Disco): status Fix Committed Fix Released
2019-09-30 08:20:14 Launchpad Janitor ceph (Ubuntu Bionic): status Fix Committed Fix Released
2019-09-30 10:12:58 James Page cloud-archive/queens: status In Progress Fix Committed
2019-09-30 10:13:00 James Page tags canonical-bootstack sts sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-rocky-needed verification-stein-needed canonical-bootstack sts sts-sru-needed verification-done-bionic verification-done-disco verification-needed verification-queens-needed verification-rocky-needed verification-stein-needed
2019-10-14 12:45:38 James Page cloud-archive/stein: status Fix Committed Fix Released
2019-10-14 12:48:48 James Page cloud-archive/rocky: status Fix Committed Fix Released
2019-10-14 13:39:17 James Page cloud-archive/train: status Fix Committed Fix Released