** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819869
Title:
linux-cloud-tools-common 3.13.0-166.216 in Trusty is missing
27.2.1 is in bionic, focal and hirsute. According to @raof it was
SRU'ed, yesterday. Seems this bug slipped through.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936833
Title:
postinst fails when
I see two errors, both of which are unrelated to this update:
1) A call to "snap prepare-image" fails because download of a model assertion
fails.
2) A FileNotFoundError in test_does_not_fit
None of these involve a snap-tool invocation.
--
You received this bug notification because you are a
Tested and confirmed functionality on Disco and Bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837871
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837871
Title:
Add retry logic to snap-tool to make downloads more
MPs for disco:
https://code.launchpad.net/~tobijk/livecd-rootfs/+git/livecd-rootfs/+merge/371794
and bionic:
https://code.launchpad.net/~tobijk/livecd-rootfs/+git/livecd-rootfs/+merge/371795
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> (Odds are that whatever causes it to be recreated later in boot would be
> blocked by cloud-init waiting.)
But that's not happening. The instance does boot normally, the only
service degraded is cloud-init and there is no significant delay either.
So conversely, if I put a loop into cloud-init
I may be missing the point, but the symlink in question is eventually
recreated, does that tell us anything? This here
> Dan had put a udevadm settle in this spot like so
>
> def get_size(filename)
>util.subp(['udevadm', 'settle'])
>os.open()
looks to me like the event queue should
** Changed in: cloud-init
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
To manage notifications about this bug go
@daniel-thewatkins, I'm not convinced that this bug is invalid for
cloud-init. After reading through all of this again, I still don't
understand, what guarantee there is that when `udevadm settle` is
called, all relevant events have already been queued.
Copying udevadm over, and with that
When I say unorthodox, I mean I copied the binary ;) So that should
narrow it down quite a bit. Unless there is more funniness involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
Oh, good observation, Dan. Yes, it was happening on Cosmic and later.
But I cannot say when it started. Now in a moment of despair I tried
something very unorthodox: I copied udevadm from Bionic to the Eoan
image and ran the tests again. Look and behold, all pass.
** No longer affects:
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
To manage
Public bug reported:
[Impact]
* livecd-rootfs builds will fail immediately when a snap-tool invocation
fails to contact the snapstore because of ephemeral connection problems
or a transient error on the server side.
* The snap-tool script included with livecd-rootfs in Eoan has been
enhanced to
** Patch added: "Patch Bionic"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1837871/+attachment/5279186/+files/backport-bionic.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Patch Disco"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1837871/+attachment/5279187/+files/backport-disco.diff
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
I have verified (bionic 2.525.28 and disco 2.578.6) that the changes to
snap_preseed do not break existing functionality and that an error is
thrown when the helper _snap_preseed is called with an invalid snap
name, resulting in snap-info failing to retrieve the base.
** Tags removed:
I believe that comment #27 is correct, because after that the
autopkgtests for ubuntu-image succeeded (triggered by a qemu update)
using the previous revision of livecd-rootfs on disco. But I'm not able
to tell how the changes made to livecd-rootfs affect the
operation/testing of ubuntu-image.
--
** Patch added: "Backport for Disco"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1828500/+attachment/5277326/+files/disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ * Failing to do error checks on `snap-tool info` calls while determining
+ the bases of snaps can lead to inconsistently-seeded images as reported
+ in the original bug report below.
+
+ * This affects all stable releases which use automatic detection of
Maybe also useful: modifications to snap-tool to make it more resilient
to connection failures of all sorts:
https://code.launchpad.net/~tobijk/livecd-rootfs/+git/livecd-
rootfs/+merge/370139
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
My mistake that I didn't do proper error checking while determining the
base of a snap. This here
https://code.launchpad.net/~tobijk/livecd-rootfs/+git/livecd-
rootfs/+merge/370096
will hopefully prevent this from happening again.
--
You received this bug notification because you are a member
I ran the following test on the current version of livecd-rootfs for
Bionic:
https://pastebin.ubuntu.com/p/wQknctr6ys/
with a positive result:
https://pastebin.ubuntu.com/p/N8PXRJJV9b/
So I think in principle it should work, but maybe there are silent
download failures. We definitely need
Public bug reported:
On a recent Bionic Azure image, the command
grub-probe --device /dev/sda1 --target=fs_uuid
fails with
grub-probe: error: not a directory.
The reason for this seems to be that grub-probe finds the minixfs
superblock magic 0x138F at offset
0410 8f 13 3a 00
** Description changed:
[Impact]
When there is an error with the apt proxy the headers are not returned
which makes debugging hard.
[Test Case]
This was tested on xenial when the release lacked the InRelease file by-
- hash. It's hard to test otherwise unless there are
Public bug reported:
AFFECTED RELEASE:
Bionic
PACKAGE VERSION:
debconf - 1.5.66
DESCRIPTION:
When upgrading the kernel on a recent Bionic minimal image, the user is
prompted to resolve a conflict in the file /boot/grub/menu.lst.
The minimal images do not have dialog/whiptail installed, so
** Tags added: bionic cosmic xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063
Title:
[Hyper-V] KVP daemon fails to start on first boot of disco VM
To manage notifications about this
This also happens in Bionic minimal images and seems to be a simple race
where the daemon is launched when the device is not yet visible.
It seems Fedora had the same or a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1195029
>From the conversation in that bug report, my
I would like to propose this change to snap-tool to partially mitigate
the problems discussed here:
https://code.launchpad.net/~tobijk/livecd-rootfs/+git/livecd-
rootfs/+merge/364800
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verified-trusty
** Tags added: verified-done-trusty
** Tags removed: verified-done-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have verified that version 3.13.0-167.217 contains the missing files
and that after installation hv_kvp_daemon and hv_vss_daemon are active.
** Tags removed: verification-needed-trusty
** Tags added: verified-trusty
--
You received this bug notification because you are a member of Ubuntu
This is a packaging issue, so logs should be irrelevant.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819869
Title:
Public bug reported:
Version 3.13.0-165.215 of linux-cloud-tools-common has the following
contents
/.
/usr
/usr/sbin
/usr/sbin/hv_vss_daemon
/usr/sbin/hv_kvp_daemon
/usr/sbin/hv_fcopy_daemon
/usr/sbin/hv_get_dhcp_info
/usr/sbin/hv_set_ifconfig
/usr/sbin/hv_get_dns_info
/usr/share
/usr/share/man
Images for Xenial, Bionic and Cosmic have been generated and tested. We
have confirmation that all images are working as expected with this
version of rax-nova-agent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
* Affects environments where the base image is read-only but kernel
modules are copied to a tempfs or other overlay mounted on /lib/modules.
* This affects users of our stable release images available from http
://cloud-images.ubuntu.com.
*
debdiff for Cosmic.
** Description changed:
[Impact]
* Affects environments where the base image is read-only but kernel
modules are copied to a tempfs or other overlay mounted on /lib/modules.
* This affects users of our stable release images available from http
debdiff for Bionic.
** Patch added: "debdiff for Bionic."
https://bugs.launchpad.net/cloud-images/+bug/1792905/+attachment/5190910/+files/livecd-rootfs-bionic.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
* Affects environments where the base image is read-only but kernel
modules are copied to a tempfs or other overlay mounted on /lib/modules.
* This affects users of our stable release images.
* The attached fixes ensure /lib/modules always
** Description changed:
- #! NB Foundations coding day task !#
-
[Impact]
- * An explanation of the effects of the bug on users and
+ * Affects environments where the base image is read-only but kernel
+ modules are copied to a tempfs or other overlay mounted on /lib/modules.
- *
39 matches
Mail list logo
