Public bug reported:
Changes to support day-of-week patching and logging to syslog were added
to upstream (https://github.com/mvo5/unattended-upgrades) over a year
ago. These changes are not present in the latest Xenial nor Trusty
packages (0.90 and 0.82.1) - requesting that these changes be pulle
Thanks Scott, Steve, and Paul for driving a fix that will help everyone!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611074
Title:
Reformatting of ephemeral drive fails on resize of Azure VM
To
I tested this latest fix and it looks good to me. The post-install fix
seems to work and after multiple resizes I still see /mnt coming back as
ext4
-> Pre-install
$ dpkg -l | grep 'cloudinit '
ii cloud-init 0.7.8-1-g3705bb5-0ubuntu1~16.04.3 all
Init scripts for
Agree with Paul, in my testing x-system.after makes no difference.
Removing ntfs-3g and blocking the ntfs kernel module are the only things
that are working for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Attaching logs from my repro as well. I did (patch -> reboot -> resize).
The included fstab is after resize, I'll check the state of fstab at
intermediary steps as well.
** Attachment added: "logs.tar.gz"
https://bugs.launchpad.net/cloud-init/+bug/1611074/+attachment/4778347/+files/logs.tar.g
Correction, if I follow the workflow (upgrade cloud-init -> reboot ->
resize) then the ephemeral drive is formatted properly. If this ins
intended functionality (reboot is required before resize) then we can
consider bug 1611074 resolved as well.
--
You received this bug notification because you
Thanks for your help Steve and Scott. I ran a test with 100 VM's (custom image
with this version of cloud-init included) and all 100 successfully came up with
/mnt formatted as ext4. So I think this bug is sorted out.
However, I'm still able to repro bug 1611074 when I resize a VM with this
vers
Users continue to hit this issue every day in Xenial, I don't see how
they'll be mitigated without backporting the fix. Can we get an ETA for
backporting to Xenial?
Thanks again,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Thanks for the quick response, in my testing I've been unable to repro
the issue. Will this be backported to Xenial? Users will continue to hit
this issue until the fix is backported.
Thanks again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
We don't have a reliable repro but would be glad to test out a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626243
Title:
Cloud-init fails to write ext4 filesystem to Azure Ephemeral Drive
T
Public bug reported:
When using the official Ubuntu 16.04 Docker image on a 16.04 Dockerhost (Docker
version 1.11.2), if we run an apt-get command that installs > 100 packages, the
101st package will fail as a hashsum mismatch. E.g.
Get:101 http://azure.archive.ubuntu.com/ubuntu xenial/main amd6
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579192
Title:
[SRU] dhclient.conf regression in walinuxagent 2.0.16-0ubuntu2~12.04.0
To manage notifications about th
12 matches
Mail list logo
