Activity log for bug #1691489

Date Who What changed Old value New value Message
2017-05-17 14:21:07 Scott Moser bug added bug
2017-05-17 14:35:56 Scott Moser attachment added orig-boot.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878322/+files/orig-boot.tar.xz
2017-05-17 14:36:06 Scott Moser cloud-init: status New Confirmed
2017-05-17 14:36:09 Scott Moser cloud-init: importance Undecided Medium
2017-05-17 14:36:31 Scott Moser attachment added upgrade-first-reboot.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878323/+files/upgrade-first-reboot.tar.xz
2017-05-17 14:37:18 Scott Moser attachment added after-restart.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878324/+files/after-restart.tar.xz
2017-05-17 14:39:45 Scott Moser attachment removed upgrade-first-reboot.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878323/+files/upgrade-first-reboot.tar.xz
2017-05-17 14:39:55 Scott Moser attachment removed after-restart.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878324/+files/after-restart.tar.xz
2017-05-17 14:42:54 Scott Moser attachment added upgrade-first-reboot.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878325/+files/upgrade-first-reboot.tar.xz
2017-05-17 14:43:07 Scott Moser attachment added after-restart.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878326/+files/after-restart.tar.xz
2017-05-17 14:43:18 Scott Moser attachment added after-restart-with-fsck.tar.xz https://bugs.launchpad.net/cloud-init/+bug/1691489/+attachment/4878327/+files/after-restart-with-fsck.tar.xz
2017-05-17 16:10:54 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/324191
2017-05-19 18:36:42 Scott Moser bug added subscriber Dimitri John Ledkov
2017-05-22 14:36:22 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/324401
2017-05-25 16:54:09 Balint Reczey cloud-init: assignee Balint Reczey (rbalint)
2017-06-26 14:08:13 Scott Moser bug task added cloud-init (Ubuntu)
2017-06-26 14:08:20 Scott Moser cloud-init (Ubuntu): status New Confirmed
2017-06-26 14:08:23 Scott Moser cloud-init (Ubuntu): importance Undecided Medium
2017-06-26 14:08:30 Scott Moser nominated for series Ubuntu Artful
2017-06-26 14:08:30 Scott Moser bug task added cloud-init (Ubuntu Artful)
2017-06-26 14:08:30 Scott Moser nominated for series Ubuntu Xenial
2017-06-26 14:08:30 Scott Moser bug task added cloud-init (Ubuntu Xenial)
2017-06-26 14:08:30 Scott Moser nominated for series Ubuntu Zesty
2017-06-26 14:08:30 Scott Moser bug task added cloud-init (Ubuntu Zesty)
2017-06-26 14:08:30 Scott Moser nominated for series Ubuntu Yakkety
2017-06-26 14:08:30 Scott Moser bug task added cloud-init (Ubuntu Yakkety)
2017-06-26 14:08:39 Scott Moser cloud-init (Ubuntu Xenial): status New Confirmed
2017-06-26 14:08:42 Scott Moser cloud-init (Ubuntu Yakkety): status New Confirmed
2017-06-26 14:08:44 Scott Moser cloud-init (Ubuntu Zesty): status New Confirmed
2017-06-26 14:08:47 Scott Moser cloud-init (Ubuntu Xenial): importance Undecided Medium
2017-06-26 14:08:48 Scott Moser cloud-init (Ubuntu Yakkety): importance Undecided Medium
2017-06-26 14:08:50 Scott Moser cloud-init (Ubuntu Zesty): importance Undecided Medium
2017-07-12 11:34:15 Balint Reczey cloud-init: assignee Balint Reczey (rbalint)
2017-07-12 11:34:55 Balint Reczey cloud-init: assignee Balint Reczey (rbalint)
2017-07-31 14:37:05 Launchpad Janitor cloud-init (Ubuntu Artful): status Confirmed Fix Released
2017-08-04 01:03:46 Brian Murray cloud-init: status Confirmed Fix Released
2017-08-04 01:36:31 Scott Moser description As reported in bug 1686514, sometimes /mnt will not get mounted when re-delpoying or stopping-then-starting a Azure vm of L32S. This is probably a more generic issue, I suspect shown due to the speed of disks on these systems. Related bugs: * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks === Begin SRU Template === [Impact] There is a race condition on a re-deployment of cloud-init on Azure where /mnt will not get properly formatted or mounted. This is due to "dirty" entries in /etc/fstab that cause a device to be busy when cloud-init goes to format it. This shows itself usually as 'mkfs' complaining that the device is busy. The cause is that systemd starts an fsck and collides with cloud-init re-formatting the disk. The problem can be seen other places but seemed to be most reproducible and originally found on Azure. [Test Case] 1.) Launch a Azure vm, ideally size L32S. 2.) Log in and verify the system properly mounted /mnt. 3.) Re-deploy the vm through the web ui and try again. [Regression Potential] Worst case scenario, these changes unnecessarily slow down boot and do not fix the problem. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=1f5489c258 === End SRU Template === As reported in bug 1686514, sometimes /mnt will not get mounted when re-delpoying or stopping-then-starting a Azure vm of L32S. This is probably a more generic issue, I suspect shown due to the speed of disks on these systems. Related bugs:  * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks
2017-08-04 13:47:15 Scott Moser cloud-init: status Fix Released Fix Committed
2017-08-23 12:27:50 Chris J Arges cloud-init (Ubuntu Xenial): status Confirmed Fix Committed
2017-08-23 12:27:53 Chris J Arges bug added subscriber Ubuntu Stable Release Updates Team
2017-08-23 12:27:55 Chris J Arges bug added subscriber SRU Verification
2017-08-23 12:27:58 Chris J Arges tags verification-needed verification-needed-xenial
2017-08-23 12:31:17 Chris J Arges cloud-init (Ubuntu Zesty): status Confirmed Fix Committed
2017-08-23 12:31:22 Chris J Arges tags verification-needed verification-needed-xenial verification-needed verification-needed-xenial verification-needed-zesty
2017-09-12 22:03:16 Chad Smith tags verification-needed verification-needed-xenial verification-needed-zesty verification-done-xenial verification-needed verification-needed-zesty
2017-09-12 22:43:17 Chad Smith tags verification-done-xenial verification-needed verification-needed-zesty verification-done-xenial verification-done-zesty
2017-09-13 01:26:05 Launchpad Janitor cloud-init (Ubuntu Xenial): status Fix Committed Fix Released
2017-09-13 01:26:36 Chris Halse Rogers removed subscriber Ubuntu Stable Release Updates Team
2017-09-13 01:27:27 Launchpad Janitor cloud-init (Ubuntu Zesty): status Fix Committed Fix Released
2017-09-15 10:00:10 thermoman bug added subscriber thermoman
2017-09-15 14:16:09 Scott Moser cloud-init (Ubuntu Yakkety): status Confirmed Won't Fix
2017-09-15 14:18:39 Scott Moser description === Begin SRU Template === [Impact] There is a race condition on a re-deployment of cloud-init on Azure where /mnt will not get properly formatted or mounted. This is due to "dirty" entries in /etc/fstab that cause a device to be busy when cloud-init goes to format it. This shows itself usually as 'mkfs' complaining that the device is busy. The cause is that systemd starts an fsck and collides with cloud-init re-formatting the disk. The problem can be seen other places but seemed to be most reproducible and originally found on Azure. [Test Case] 1.) Launch a Azure vm, ideally size L32S. 2.) Log in and verify the system properly mounted /mnt. 3.) Re-deploy the vm through the web ui and try again. [Regression Potential] Worst case scenario, these changes unnecessarily slow down boot and do not fix the problem. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=1f5489c258 === End SRU Template === As reported in bug 1686514, sometimes /mnt will not get mounted when re-delpoying or stopping-then-starting a Azure vm of L32S. This is probably a more generic issue, I suspect shown due to the speed of disks on these systems. Related bugs:  * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks === Begin SRU Template === [Impact] There is a race condition on a re-deployment of cloud-init on Azure where /mnt will not get properly formatted or mounted. This is due to "dirty" entries in /etc/fstab that cause a device to be busy when cloud-init goes to format it. This shows itself usually as 'mkfs' complaining that the device is busy. The cause is that systemd starts an fsck and collides with cloud-init re-formatting the disk. The problem can be seen other places but seemed to be most reproducible and originally found on Azure. [Test Case] 1.) Launch a Azure vm, ideally size L32S. 2.) Log in and verify the system properly mounted /mnt. 3.) Re-deploy the vm through the web ui and try again. [Regression Potential] Worst case scenario, these changes unnecessarily slow down boot and do not fix the problem. [Regression] This SRU change caused bug 1717477. [Other Info] Upstream commit at   https://git.launchpad.net/cloud-init/commit/?id=1f5489c258 === End SRU Template === As reported in bug 1686514, sometimes /mnt will not get mounted when re-delpoying or stopping-then-starting a Azure vm of L32S. This is probably a more generic issue, I suspect shown due to the speed of disks on these systems. Related bugs:  * bug 1686514: Azure: cloud-init does not handle reformatting GPT partition ephemeral disks * bug 1717477: cloud-init generates ordering cycle via After=cloud-init in systemd-fsck
2017-09-15 15:58:01 Launchpad Janitor merge proposal linked https://code.launchpad.net/~rbalint/cloud-init/+git/cloud-init/+merge/330842
2017-09-15 18:35:29 Scott Moser cloud-init: status Fix Committed Confirmed
2017-09-15 18:35:33 Scott Moser cloud-init: assignee Balint Reczey (rbalint)
2017-09-15 18:35:45 Scott Moser cloud-init (Ubuntu Xenial): status Fix Released Confirmed
2017-09-15 18:35:55 Scott Moser cloud-init (Ubuntu Xenial): status Confirmed Fix Released
2017-09-15 21:34:36 Ryan Harper bug added subscriber Ryan Harper
2017-09-18 15:34:22 Łukasz Zemczak cloud-init (Ubuntu Artful): status Fix Released Confirmed
2017-09-23 02:32:41 Scott Moser cloud-init: status Confirmed Fix Released
2017-10-03 16:05:19 Scott Moser cloud-init: status Fix Released Confirmed
2017-10-03 16:05:53 Scott Moser cloud-init (Ubuntu Xenial): status Fix Released Fix Committed
2017-10-03 16:05:58 Scott Moser cloud-init (Ubuntu Xenial): status Fix Committed Confirmed
2017-10-03 16:06:00 Scott Moser cloud-init (Ubuntu Zesty): status Fix Released Confirmed
2018-07-20 14:54:16 Scott Moser cloud-init (Ubuntu Zesty): status Confirmed Won't Fix
2018-07-20 14:54:19 Scott Moser cloud-init (Ubuntu Artful): status Confirmed Won't Fix
2021-01-04 14:52:27 Dan Watkins cloud-init: status Confirmed Fix Released
2023-05-11 01:52:20 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/2892
2023-05-11 05:00:00 thermoman removed subscriber thermoman