** Merge proposal linked:
https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/396020
** Merge proposal linked:
https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/396021
** Merge proposal linked:
https://code.launchpad.net/~dav
Public bug reported:
livecd-rootfs v2.700 in hirsute introduced a fix to produce unpacked
artifacts for use by multipass on macOS hosts. These hosts require
direct access to a kernel and initrd to boot the buildd images.
See: https://git.launchpad.net/livecd-
rootfs/commit/?id=065c82314464fa78337
Hi dhbaird - sorry, the focal backport has languished in my queue for
quite a while now. I have not been able find time to focus on it.
Another developer, patviafore, has offered to take the task off my
hands, and I believe he is hoping to start looking into it at the start
of the new year. Happy h
Hi dhbaird - this was fixed in v2.672, v2.674, and v2.678 of the livecd-
rootfs package in groovy; however, those changes have not been
backported to focal, yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
This also affects me running Ubuntu 20.10 MATE on a pi400
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907432
Title:
Raspberry Pi 400 Kernel Panic
To manage notifications about this bug go to:
ht
@tmolloy, thank you for circling back around. I'm glad the patches worked for
you :-)
Note that there are other (unrelated) packages in @waveform's PPA that may get
installed with an apt upgrade. I don't know what the state of those packages
are. I disabled the PPA after installing bluez, just t
On Ubuntu 20.10 MATE on a pi400, I ran through the following steps:
* Boot the Ubuntu 20.10 MATE for Pi image on a Pi 400 (Was not a fresh
installation)
* Start the Settings application and switch to the Bluetooth tab
* Verify that Bluetooth is not enabled and attempting to activate it fails
* su
@colin-king dmesg output:
[0.00] Linux version 5.8.0-1008-gcp (buildd@lgw01-amd64-043) (gcc
(Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1)
#8-Ubuntu SMP Thu Oct 15 12:48:27 UTC 2020 (Ubuntu 5.8.0-1008.8-gcp 5.8.14)
[0.00] Command line: BOOT_IMAGE=/boot
Public bug reported:
On a GCE e2-medium instance running Groovy with a standard persistent
disk, we see:
$ cat /sys/block/sda/queue/rotational
1
$ cat /sys/block/sda/queue/scheduler
[none] mq-deadline
I'd expect the contents of /sys/block/sda/queue/scheduler to be:
[mq-deadline] none
---
$
Public bug reported:
The default fstab entries for ubuntu cloud images are:
LABEL=cloudimg-rootfs / ext4 defaults 0 0
LABEL=UEFI /boot/efi vfat defaults 0 0
These entries do not align with the defaults that we use elsewhere. We
should decide on the defaults for fstab, and apply those consistentl
Public bug reported:
We have a cloud-images qualification test for the google-guest-agent to
ensure the following daemons are enabled for GCE images:
- accounts_daemon
- clock_skew_daemon
- network_daemon
I could not find a way to inspect a currently running agent to determine
the configuration
Sorry, that was v2.672 and v2.678 of the livecd-rootfs package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
To manage notifications about this bug go
Robert Jennings's proposal from comment #33 landed in groovy v2.672.
A mechanism was also added in groovy v2.678 to detect if we've booted
using the panic fallback behavior mentioned by Steve Langasek in comment
#21.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I ran the following quick test against a real EKS cluster,
and everything seemed to work as expected:
xenial $ # Enable proposed
xenial $ sudo apt-get install -y \
awscli/xenial-proposed \
python3-botocore/xenial-proposed \
python3-s3transfer/xenial-proposed
[..snip..]
xenial $ aws ia
It looks like this may only be an upgrade failure:
If you grab the 20200812 groovy image with systemd v245.7-1ubuntu1:
https://cloud-images.ubuntu.com/minimal/daily/groovy/20200812/groovy-minimal-cloudimg-amd64.img
And update systemd to v246-2ubuntu1, you see the breakage described in
this bug.
Autopkgtests for v2.664.5 have passed (which build ubuntu-
cpc:minimized).
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Description changed:
# Description:
After this upgrade in groovy, networking stopped working:
Start-Date: 2020-08-14 17:02:50
Commandline: apt-get dist-upgrade --assume-yes
Requested-By: ubuntu (1000)
Install: motd-news-config:amd64 (11ubuntu11, automatic)
Upgrade: libaudit
Public bug reported:
# Description:
After this upgrade in groovy, networking stopped working:
Start-Date: 2020-08-14 17:02:50
Commandline: apt-get dist-upgrade --assume-yes
Requested-By: ubuntu (1000)
Install: motd-news-config:amd64 (11ubuntu11, automatic)
Upgrade: libaudit-common:amd64 (1:2.8.
This may not be a new problem. Running the test case against a bionic
image from June shows similar behavior:
$ multipass launch
'https://cloud-images.ubuntu.com/minimal/releases/bionic/release-20200610/ubuntu-18.04-minimal-cloudimg-amd64.img'
Launched: main-gnu
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880999
Title:
SRU: bump version to make compatible with upstream awscli requirements
To manage notifications abou
The python-boto3 unit and functional tests seem to do a pretty good job
exercising python-botocore and python-s3transfer. I ran those tests
against botocore/updates and s3transfer/updates for each suite, and
compared those results to the same tests run against botocore/proposed
and s3transfer/propo
Oops, I missed focal. Updated the repository to include logs for focal
too:
https://git.launchpad.net/~davidkrauser/+git/logs/tree/LP1875485/20200714?id=17b08c1f3ea389dd3f49f2a511f6ed6ed45c6ac4
==> focal-proposed-py3.log <==
OK
==> focal-updates-py3.log <==
OK
I also forgot to mention: the docu
The python-boto3 unit and functional tests seem to do a pretty good job
exercising python-botocore and python-s3transfer. I ran those tests
against botocore/updates and s3transfer/updates for each suite, and
compared those results to the same tests run against botocore/proposed
and s3transfer/propo
The tests in `python-scrapy-1.5.0/tests/test_downloader_handlers.py` run
during python-scrapy's autopkgtests exercise botocore and s3transfer by
generating mocked requests and comparing to known good values. They
don't make any real API requests over the network.
--
You received this bug notifica
There was a small bug in the script posted previously - it ran tests for
kombu and swift that are unnecessary. The python-scrapy tests are the
only relevant autopkgtests to run for python3-botocore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sorry, link to helper script was mangled in previous message:
https://git.launchpad.net/~davidkrauser/+git/scripts/plain/autopkgtest-
rdepends.sh?id=7cb005185744047f30e6f275eec19509eda50182
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hi Brian,
I've run autopkgtests for each package listed by reverse-depends:
reverse-depends -lsb python3-botocore
Against python3-botocore/bionic-proposed and python3-s3transfer/bionic
using this helper script:
https://git.launchpad.net/~davidkrauser/+git/scripts/plain/autopkhttps://git.launchp
Performed verification steps on a fresh eoan VM:
- Enable proposed
- apt install python-s3transfer/eoan-proposed and
python3-s3transfer/eoan-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3
** Tags removed: verification-needed-eoan
** Tags added: verifi
Performed verification steps on a fresh xenial VM:
- Enable proposed
- apt install python-s3transfer/xenial-proposed and
python3-s3transfer/xenial-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3
** Tags removed: verification-needed-xenial
** Tags adde
Performed verification steps on a fresh bionic VM:
- Enable proposed
- apt install python-s3transfer/bionic-proposed and
python3-s3transfer/bionic-proposed
- dpkg -s python-s3transfer shows v0.3.3
- dpkg -s python3-s3transfer shows v0.3.3
** Tags removed: verification-needed-bionic
** Tags adde
Followed testing steps in a fresh eoan VM:
- Enabled eoan-proposed
- Installed awscli/eoan-proposed and python3-botocore/eoan-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and updated the local kube
Performed verification steps on a fresh xenial VM:
- Enable proposed
- apt install python-botocore/xenial-proposed and
python3-botocore/xenial-proposed
- dpkg -s python-botocore shows v1.16.19
- dpkg -s python3-botocore shows v1.16.19
** Tags removed: verification-needed-xenial
** Tags added: v
Performed verification steps on a fresh bionic VM:
- Enable proposed
- apt install python-botocore/bionic-proposed and
python3-botocore/bionic-proposed
- dpkg -s python-botocore shows v1.16.19
- dpkg -s python3-botocore shows v1.16.19
** Tags removed: verification-needed-bionic
** Tags added: ve
Performed verification steps on a fresh focal VM:
- Enable proposed
- apt install python3-botocore/focal-proposed
- dpkg -s python3-botocore shows v1.16.19
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a m
Performed verification steps on a fresh eoan VM:
- Enable proposed
- apt install python-botocore/eoan-proposed and python3-botocore/eoan-proposed
- dpkg -s python-botocore shows v1.16.19
- dpkg -s python3-botocore shows v1.16.19
** Tags removed: verification-needed verification-needed-eoan
** Ta
Followed testing steps for xenial:
- Enabled focal-proposed
- Installed awscli/focal-proposed and python3-botocore/focal-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig
- This failed to run successfully. Got error:
A
Followed testing steps for focal:
- Enabled focal-proposed
- Installed awscli/focal-proposed and python3-botocore/focal-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and updated the local kube
conf
** 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/1867673
Title:
[SRU] awscli not kept up to date
To manage notificat
Followed testing steps for bionic:
- Enabled bionic-proposed
- Installed awscli/bionic-proposed and python3-botocore/bionic-proposed
- Ran aws --version (got expected 1.18.69)
- Ran aws eks help (got expected help text)
- Ran aws eks update-kubeconfig (ran successfully and updated the local kube
Public bug reported:
LXD can't use nftables on the latest linux-kvm kernels for eoan, focal,
and groovy:
- groovy: 5.4.0.1009.9
- focal: 5.4.0-1011.11
- eoan: 5.3.0.1017.19
LXD detects that nft tools are available, and nft tables can be listed;
however, trying to create a new table or rule fails
The updated packages have been verified in GCE and work as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878654
Title:
Remove automatically added groups from os-login
To manage notificat
I built a test bionic image with open-iscsi from proposed, uploaded to
OCI, booted on a PV instance, then performed a reboot. That reboot
worked as expected without any scsi-related delays.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
--
You re
** 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/1863024
Title:
SRU: bootable buildd images for all releases
To mana
I did the following to validate v2.525.43:
- Performed livefs build with project ubuntu-base and subproject buildd
- Ensured the img artifact from that build boots using Multipass
- Performed a livecd-rootfs build using the rootfs tarball from that build
Everything appears to be working as it
sergiusens and cjwatson,
after more digging, I've found:
- The bootable buildd image work that recently merged into the
ubuntu/master (focal) branch inadvertently enabled the updates and
security pockets in /etc/apt/sources.list
- By switching the image format from 'none' to 'ext4', we no
** Merge proposal linked:
https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/381270
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860780
Title:
buildd images have
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
[Impact]
* We don't have bootable buildd images, and we need them for Multipass.
[Test Case]
* Perform livefs build with project ubuntu-base and subproject bu
** Description changed:
We want to backport bootable enabling bootable buildd images to eoan,
bionic, and xenial.
-
[Impact]
* We don't have bootable buildd images, and we need them for Multipass.
[Test Case]
* Perform livefs build with project ubuntu-base and subproject
Focal images are configured to use -updates and -security; however,
bionic images are not.
Bionic images will be updated to match.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860780
Title:
build
Hey cjwatson,
Digging into this more, while our buildd images are populated only with
packages from the release pocket, they include -updates and -security in
their `/etc/apt/sources.list`.
Is this expected or desired?
--
You received this bug notification because you are a member of Ubuntu
Bug
@fginther,
The touchscreen works great with the -proposed kernel, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865836
Title:
Touchscreen Unresponsive in Focal, but Works in Eoan
To manag
ges
Status: New => In Progress
** Changed in: cloud-images
Assignee: (unassigned) => David Krauser (davidkrauser)
** Project changed: cloud-images => livecd-rootfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
With kernel version 5.3.0, the touchscreen works. Attaching a dmesg with
this kernel.
** Attachment added: "dmesg.5.3.0-29-generic.log"
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+attachment/5334325/+files/dmesg.5.3.0-29-generic.log
--
You received this bug notification
With kernel version 5.4.0, the touchscreen does not work. Attaching a
dmesg with this kernel.
** Attachment added: "dmesg.5.4.0-14-generic.log"
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+attachment/5334326/+files/dmesg.5.4.0-14-generic.log
--
You received this bug noti
Public bug reported:
After upgrading my Surface Go to Focal from Eoan, the touchscreen has
stopped working.
A snippet from journalctl:
12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for
/dev/input/event4 13:68 fd 28 paused 0
12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (
** Summary changed:
- Build failures when specifying: project=ubuntu-base and subproject=buildd
+ Build failures when specifying in focal: project=ubuntu-base and
subproject=buildd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
I am unable to perform focal buildd image builds. DNS resolution is
broken in the chroot when attempting to install packages:
[...]
The following NEW packages will be installed:
policyrcd-script-zg2
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get
Hi all, thank you for the merge. I was able to successfully build
against the ubuntu/bionic branch (as described above).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837088
Title:
Generate HyperV
Hi brian-murray and sil2100,
I tested this with the ubuntu/disco branch today, and the image built
successfully. I used ubuntu-bartender as described above to do the
build.
When attempting with the ubuntu/bionic branch, however, it doesn't
appear that my changes have merged in. Is that expected?
I'm seeing very similar behavior on Ubuntu 19.10 with X11 and a single
monitor:
I've noticed on Ubuntu 19.10 with X11 fractional scaling set to 1.25x,
the pointer duplicates itself when I login to a new session. The
original pointer sticks on the screen at 1x size, and I get a new
pointer to use t
We ran into this bug initially on xenial when doing image builds.
Manually installing the cloud-guest-utils 0.31-0ubuntu1.1 deb in that
environment resolves the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Proposed Changes:
Disco:
https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/370330
Bionic:
https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/370331
** Merge proposal linked:
https://code.launchpad.net/~davidkrauser/livecd-rootfs/+
Public bug reported:
[Overview]
We can generate HyperV Image Gallery builds for Eoan images with livecd-
rootfs, but not for Bionic and Disco. These images are necessary for
users to install Ubuntu on their Windows machines from the HyperV Image
Gallery:
https://ubuntu.com/blog/optimised-ubuntu-
Thank you both for addressing the issue :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835124
Title:
growpart mishandles image filenames that end in a number
To manage notifications about this
The error occurs with a gpt formatted image, which is supported by
sfdisk.
This logic in growpart is broken for image files:
if [ -b "${DISK}p${PART}" -a "${DISK%[0-9]}" != "${DISK}" ]; then
If an image filename ends with a number, sfdisk identifies each
partition like:
${DISK}p${PART_NUMBER}
Public bug reported:
When growpart attempts to determine the partition to resize, it uses
this logic:
$ sed -n '266,275p' $(which growpart)
dpart="${DISK}${PART}" # disk and partition number
if [ -b "${DISK}p${PART}" -a "${DISK%[0-9]}" != "${DISK}" ]; then
# for bl
line wrap killed the link:
https://i430477153.restricted.launchpadlibrarian.net/430477153/buildlog_ubuntu_xenial_powerpc_powerpc_cpc_BUILDING.txt.gz?token=cXQZLr4n6nn9LNfgRxL1Q5LX0zCzhS2z
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The specific error:
Setting up snapd (2.39.2) ...
md5sum: /etc/apparmor.d/usr.lib.snapd.snap-confine: No such file or directory
chmod: cannot access '/var/lib/snapd/void': No such file or directory
dpkg: error processing package snapd (--configure):
subprocess installed post-installation script r
We're still seeing powerpc builds failing on xenial:
https://i430477153.restricted.launchpadlibrarian.net/430477153/buildlog_ubuntu_xenial_powerpc_powerpc_
cpc_BUILDING.txt.gz?token=cXQZLr4n6nn9LNfgRxL1Q5LX0zCzhS2z
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I tested this fix on disco, and it appears to be working as intended.
The issue still exists on bionic, however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800681
Title:
open-iscsi should not l
70 matches
Mail list logo
