[Bug 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
** 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/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/396022 ** Merge proposal linked: https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/396023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910557] [NEW] Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
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=065c82314464fa78337d5122e1d4826a7d6edbb0 This change needs to be backported to all suites. [Impact] * Without this change, users are unable to use the buildd images with multipass on macOS hosts. Snapcraft utilizes multipass to build snaps, so this blocks macOS users from building snaps. As a workaround, the CPC team is manually extracting these artifacts and publishing them to cloud-images.ubuntu.com. This is not ideal for the long-term, and could result in breakage in the event that the CPC team forgets to manually publish these artifacts. [Test Case] * After this change lands, a user should be able to build images with the ubuntu-base project and buildd subproject, and the resulting build should produce extracted kernel and initrd artifacts. [Where problems could occur] * These changes are minor, but a mistake could result in broken buildd image hooks (where the build fails) or broken buildd image artifacts (where the images don't work as expected). * Since all buildd images are manually tested by the launchpad team, multipass team, and snapcraft team before they enter production, the risk of introducing breakage for end users is low. ** Affects: livecd-rootfs (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/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
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 holidays to you, too :-) -- 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 to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
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.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907432] Re: Raspberry Pi 400 Kernel Panic
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: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1907432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
@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 to be sure I didn't unintentionally install the other packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez # I noticed there were other packages in the PPA that I did not install * sudo nvi /etc/apt/sources.list.d/waveform-ubuntu-pi-bluetooth-groovy.list # Comment out PPA * sudo apt update && sudo apt upgrade -y * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Pair a set of AirPods * Ensure I can hear audio through the AirPods Everything seemed to work as expected. Thank you for the patches :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903543] Re: Block device scheduler should be multiqueue for spinning disks
@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/vmlinuz-5.8.0-1008-gcp root=PARTUUID=506f6274-5923-4632-96d5-b96445cc673c ro console=ttyS0 panic=-1 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0fff] reserved [0.00] BIOS-e820: [mem 0x1000-0x00054fff] usable [0.00] BIOS-e820: [mem 0x00055000-0x0005] reserved [0.00] BIOS-e820: [mem 0x0006-0x00097fff] usable [0.00] BIOS-e820: [mem 0x00098000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbe11dfff] usable [0.00] BIOS-e820: [mem 0xbe11e000-0xbe120fff] ACPI data [0.00] BIOS-e820: [mem 0xbe121000-0xbe121fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbe122000-0xbe2d1fff] usable [0.00] BIOS-e820: [mem 0xbe2d2000-0xbe2d9fff] ACPI NVS [0.00] BIOS-e820: [mem 0xbe2da000-0xbe31afff] reserved [0.00] BIOS-e820: [mem 0xbe31b000-0xbf39afff] usable [0.00] BIOS-e820: [mem 0xbf39b000-0xbf3f2fff] reserved [0.00] BIOS-e820: [mem 0xbf3f3000-0xbf3fafff] ACPI data [0.00] BIOS-e820: [mem 0xbf3fb000-0xbf3fefff] ACPI NVS [0.00] BIOS-e820: [mem 0xbf3ff000-0xbffd] usable [0.00] BIOS-e820: [mem 0xbffe-0xbfff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00013fff] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.70 by EDK II [0.00] efi: TPMFinalLog=0xbe2d2000 ACPI=0xbf3fa000 ACPI 2.0=0xbf3fa014 SMBIOS=0xbf3cd000 MEMATTR=0xbe6d3698 RNG=0xbf3cec98 TPMEventLog=0xbd8b6018 [0.00] efi: seeding entropy pool [0.00] random: fast init done [0.00] secureboot: Secure boot disabled [0.00] SMBIOS 2.4 present. [0.00] DMI: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [0.00] Hypervisor detected: KVM [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr 45401001, primary cpu clock [0.00] kvm-clock: using sched offset of 8055433513 cycles [0.03] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.05] tsc: Detected 2300.000 MHz processor [0.89] e820: update [mem 0x-0x0fff] usable ==> reserved [0.91] e820: remove [mem 0x000a-0x000f] usable [0.96] last_pfn = 0x14 max_arch_pfn = 0x4 [0.000131] MTRR default type: write-back [0.000131] MTRR fixed ranges enabled: [0.000132] 0-9 write-back [0.000133] A-F uncachable [0.000134] MTRR variable ranges enabled: [0.000135] 0 base C000 mask 3FFFC000 uncachable [0.000136] 1 base 0100 mask 3F00 uncachable [0.000137] 2 disabled [0.000137] 3 disabled [0.000138] 4 disabled [0.000138] 5 disabled [0.000139] 6 disabled [0.000139] 7 disabled [0.000147] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.000157] last_pfn = 0xbffe0 max_arch_pfn = 0x4 [0.017358] check: Scanning 1 areas for low memory corruption [0.017395] Using GB pages for direct mapping [0.018424] secureboot: Secure boot disabled [0.018442] ACPI: Early table checksum verification disabled [0.018447] ACPI: RSDP 0xBF3FA014 24 (v02 Google) [0.018451] ACPI: XSDT 0xBF3F90E8 5C (v01 Google GOOGFACP 0001 0113) [0.018458] ACPI: FACP 0xBF3F4000 F4 (v02 Google GOOGFACP 0001 GOOG 0001) [0.018465] ACPI: DSDT 0xBF3F5000 0018BA (v01 Google GOOGDSDT 0001 GOOG 0001) [0.018474] ACPI: FACS 0xBE121000 40 [0.018477] ACPI: SSDT 0xBF3F8000 000316 (v02 GOOGLE Tpm2Tabl 1000 INTL 20160527) [
[Bug 1903543] [NEW] Block device scheduler should be multiqueue for spinning disks
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 --- $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy linux-gcp linux-gcp: Installed: 5.8.0.1008.8 Candidate: 5.8.0.1008.8 Version table: *** 5.8.0.1008.8 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: linux-gcp (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/1903543 Title: Block device scheduler should be multiqueue for spinning disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1903543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902103] [NEW] Ensure default fstab options are sane and consistent across all images
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 consistently across all Ubuntu images. -- quoted from ~xnox: I expect [these entries] to be: LABEL=cloudimg-rootfs / ext4 discard,errors=remount-ro 0 1 LABEL=UEFI /boot/efi vfat umask=0077 0 1 ** Affects: curtin (Ubuntu) Importance: Undecided Status: New ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Description changed: 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 consistently across all Ubuntu images. -- - quoted from ~xnox: the expect [these entries] to be: + quoted from ~xnox: I expect [these entries] to be: LABEL=cloudimg-rootfs / ext4 discard,errors=remount-ro 0 1 LABEL=UEFI /boot/efi vfat umask=0077 0 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902103 Title: Ensure default fstab options are sane and consistent across all images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1902103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901042] [NEW] Unable to inspect configuration of running google-guest-agent
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 in use. The agent only takes the following actions: - run - install - remove - start - stop - help An additional action to list the configuration in use would be very helpful. I also looked at the output of journalctl -u google-guest-agent.service, but the agent does not log configuration settings in the log, either. ** Affects: google-guest-agent Importance: Unknown Status: Unknown ** Affects: google-guest-agent (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/GoogleCloudPlatform/guest-agent/issues #85 https://github.com/GoogleCloudPlatform/guest-agent/issues/85 ** Also affects: google-guest-agent via https://github.com/GoogleCloudPlatform/guest-agent/issues/85 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901042 Title: Unable to inspect configuration of running google-guest-agent To manage notifications about this bug go to: https://bugs.launchpad.net/google-guest-agent/+bug/1901042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
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 to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867673] Re: [SRU] awscli not kept up to date
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 iam get-user # Returned expected user information xenial $ sudo snap install kubectl --classic [..snip..] xenial $ aws eks update-kubeconfig --name eks-1-17-cluster Added new context [..snip..]:cluster/eks-1-17-cluster to /home/ubuntu/.kube/config xenial $ kubectl get svc NAME TYPECLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.100.0.1 443/TCP 4m8s -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891716] Re: Networking broken after systemd update
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. If you grab the 20200817.1 groovy image with systemd v246-2ubuntu1: https://cloud-images.ubuntu.com/minimal/daily/groovy/20200817.1/groovy-minimal-cloudimg-amd64.img You won't see the breakage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891716 Title: Networking broken after systemd update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889470] Re: snap seed with channel breaks ubuntu-cpc:minimized builds on focal
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.launchpad.net/bugs/1889470 Title: snap seed with channel breaks ubuntu-cpc:minimized builds on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1889470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891716] Re: Networking broken after systemd update
** 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-common:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. + $ systemctl status systemd-networkd.service + ● systemd-networkd.service - Network Service + Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) + Active: failed (Result: exit-code) since Fri 2020-08-14 17:03:01 EDT; 12min ago + TriggeredBy: ● systemd-networkd.socket +Docs: man:systemd-networkd.service(8) +Main PID: 2745 (code=exited, status=1/FAILURE) + + Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE + Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. + Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service. + Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5. + Aug 14 17:03:01 fulfilling-hornet systemd[1]: Stopped Network Service. + Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Start request repeated too quickly. + Aug 14 17:03:01 fulfilling-hornet systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. + Aug 14 17:03:01 fulfilling-hornet systemd[1]: Failed to start Network Service. -- You received this bug notification because you are a member of Ubuntu Bugs,
[Bug 1891716] [NEW] Networking broken after systemd update
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.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libnss-systemd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ethtool:amd64 (1:5.4-1, 1:5.8-1), overlayroot:amd64 (0.45ubuntu1, 0.46ubuntu1), cloud-initramfs-copymods:amd64 (0.45ubuntu1, 0.46ubuntu1), isc-dhcp-client:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libaudit1:amd64 (1:2.8.5-2ubuntu6, 1:2.8.5-3ubuntu1), base-files:amd64 (11ubuntu10, 11ubuntu11), software-properties-common:amd64 (0.98.10, 0.99.2) End-Date: 2020-08-14 17:03:10 # Reproduction steps: $ multipass launch --name groovy-update-test daily:groovy $ multipass connect groovy-update-test # connected to VM $ sudo apt-get update && sudo apt-get dist-upgrade --assume-yes # works fine $ sudo apt-get update Err:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:2 http://archive.ubuntu.com/ubuntu groovy InRelease Temporary failure resolving 'archive.ubuntu.com' Err:3 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Temporary failure resolving 'archive.ubuntu.com' Err:4 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Temporary failure resolving 'archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-updates/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/groovy-backports/InRelease Temporary failure resolving 'archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/groovy-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. $ sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● systemd-networkd.service loaded failed failed Network Service ● systemd-networkd.socket loaded failed failed Network Service Netlink Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 2 loaded units listed. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: # Description: - After this upgrade, networking stopped working: + 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.5-2ubuntu6, 1:2.8.5-3ubuntu1), alsa-ucm-conf:amd64 (1.2.2-1ubuntu1, 1.2.2-1ubuntu2), libmpfr6:amd64 (4.0.2-1build1, 4.1.0-3), python3-software-properties:amd64 (0.98.10, 0.99.2), cloud-initramfs-dyn-netconf:amd64 (0.45ubuntu1, 0.46ubuntu1), libsystemd0:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libpam-cap:amd64 (1:2.36-1, 1:2.42-2), libgmp10:amd64 (2:6.2.0+dfsg-6, 2:6.2.0+dfsg-6ubuntu1), ubuntu-standard:amd64 (1.452, 1.453), nano:amd64 (4.9.3-1, 5.1-1), udev:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-server:amd64 (1.452, 1.453), libpipeline1:amd64 (1.5.2-2build1, 1.5.3-1), isc-dhcp-common:amd64 (4.4.1-2.1ubuntu6, 4.4.1-2.1ubuntu9), libudev1:amd64 (245.7-1ubuntu1, 246-2ubuntu1), systemd-timesyncd:amd64 (245.7-1ubuntu1, 246-2ubuntu1), ubuntu-minimal:amd64 (1.452, 1.453), libcap2:amd64 (1:2.36-1, 1:2.42-2), systemd-sysv:amd64 (245.7-1ubuntu1, 246-2ubuntu1), libcap2-bin:amd64 (1:2.36-1, 1:2.42-2), libpam-systemd:amd64 (245.7-1ubuntu1,
[Bug 1888000] Re: Bionic/Xenial minimal cloud image: failed to apply load kernel module
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 $ multipass exec main-gnu -- sudo systemctl list-units --failed --no-legend cloud-config.service loaded failed failed Apply the settings specified in cloud-config systemd-modules-load.service loaded failed failed Load Kernel Modules $ multipass exec main-gnu -- cat /etc/cloud/build.info build_name: minimal serial: 20200610 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888000 Title: Bionic/Xenial minimal cloud image: failed to apply load kernel module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880999] Re: SRU: bump version to make compatible with upstream awscli requirements
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/1880999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880999] Re: SRU: bump version to make compatible with upstream awscli requirements
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/proposed for each suite. The raw results are available here, alongside the script used to run the tests: https://git.launchpad.net/~davidkrauser/+git/logs/tree/LP1875485/20200714?id=17b08c1f3ea389dd3f49f2a511f6ed6ed45c6ac4 The summary is as follows: ==> bionic-proposed-py.log <== OK (SKIP=1) ==> bionic-proposed-py3.log <== OK ==> bionic-updates-py.log <== OK (SKIP=1) ==> bionic-updates-py3.log <== OK ==> eoan-proposed-py.log <== OK (SKIP=1) ==> eoan-proposed-py3.log <== OK ==> eoan-updates-py.log <== OK (SKIP=1) ==> eoan-updates-py3.log <== OK ==> xenial-proposed-py.log <== FAILED (SKIP=1, errors=10, failures=1) ==> xenial-proposed-py3.log <== FAILED (errors=10, failures=1) ==> xenial-updates-py.log <== FAILED (SKIP=1, errors=1, failures=1) ==> xenial-updates-py3.log <== FAILED (errors=1, failures=1) Seeing that the awscli verification for xenial against this package failed, and the test results are worse here against proposed for xenial, I'm marking this as failed verification for xenial. The other suites look to be in good order. Also: the documentation related python-boto3 tests were skipped for these runs. I couldn't get them to pass reliably, even with the dependencies from updates. ** Tags removed: verification-done-xenial ** Tags added: verification-failed-xenial -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/1880999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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 documentation related python-boto3 tests were skipped for these runs. I couldn't get them to pass reliably, even with the dependencies from updates. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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/proposed for each suite. The raw results are available here, alongside the script used to run the tests: https://git.launchpad.net/~davidkrauser/+git/logs/tree/LP1875485/20200714?id=892a5e450a359e1f7aa0a43310311129ebd48518 The summary is as follows: ==> bionic-proposed-py.log <== OK (SKIP=1) ==> bionic-proposed-py3.log <== OK ==> bionic-updates-py.log <== OK (SKIP=1) ==> bionic-updates-py3.log <== OK ==> eoan-proposed-py.log <== OK (SKIP=1) ==> eoan-proposed-py3.log <== OK ==> eoan-updates-py.log <== OK (SKIP=1) ==> eoan-updates-py3.log <== OK ==> xenial-proposed-py.log <== FAILED (SKIP=1, errors=10, failures=1) ==> xenial-proposed-py3.log <== FAILED (errors=10, failures=1) ==> xenial-updates-py.log <== FAILED (SKIP=1, errors=1, failures=1) ==> xenial-updates-py3.log <== FAILED (errors=1, failures=1) Seeing that the awscli verification for xenial against this package failed, and the test results are worse here against proposed for xenial, I'm marking this as failed verification for xenial. The other suites look to be in good order. ** Tags removed: verification-needed-eoan verification-needed-xenial ** Tags added: verification-done-eoan verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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 to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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 Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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.launchpad.net/~davidkrauser/+git/scripts/plain /autopkgtest-rdepends.sh?id =7cb005185744047f30e6f275eec19509eda50182gtest-rdepends.sh With the command: autopkgtest-rdepends.sh --package-under-test python3-botocore \ --enable-proposed-for-package python3-s3transfer \ --enable-proposed-for-package python3-botocore This gives me the following results: PASS: kombu PASS: swift FAIL: python-scrapy To compare to the baseline results (run with python3-botocore/bionic- updates and python3-s3transfer/bionic-updates), I ran this: autopkgtest-rdepends.sh --package-under-test python3-botocore And got the following results: PASS: kombu PASS: swift FAIL: python-scrapy Looking at the full autopkgtest logs (linked below), these results appear to match the results I got with the packages from proposed. Full autopackagetest logs: https://git.launchpad.net/~davidkrauser/+git/logs/tree/LP1875485/20200710/bionic?id=a60928f005e87785719b58d519b87582e435616d ** 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/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880999] Re: SRU: bump version to make compatible with upstream awscli requirements
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: verification-done-eoan -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/1880999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880999] Re: SRU: bump version to make compatible with upstream awscli requirements
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 added: verification-done-xenial -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/1880999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880999] Re: SRU: bump version to make compatible with upstream awscli requirements
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 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/1880999 Title: SRU: bump version to make compatible with upstream awscli requirements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-s3transfer/+bug/1880999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867673] Re: [SRU] awscli not kept up to date
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 config) ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done-eoan -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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: 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/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875485] Re: [SRU] python-botocore out of date
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 ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875485 Title: [SRU] python-botocore out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867673] Re: [SRU] awscli not kept up to date
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: An HTTP Client raised and unhandled exception: __init__() got an unexpected keyword argument 'ssl_context' ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial ** 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/1867673 Title: [SRU] awscli not kept up to date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867673] Re: [SRU] awscli not kept up to date
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 config) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867673] Re: [SRU] awscli not kept up to date
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867673] Re: [SRU] awscli not kept up to date
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 config) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881346] [NEW] linux-kvm should support nftables
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. Because of this, LXD has to fall back on xtables, which is a legacy package. ** Affects: linux-kvm (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/1881346 Title: linux-kvm should support nftables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1881346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878654] Re: Remove automatically added groups from os-login
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1878654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800681] Re: open-iscsi should not leave around the stamp file if no connections were made
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 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 leave around the stamp file if no connections were made To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1800681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
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 should. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860780] Re: buildd images have a very plain sources.list
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 now hit this block in livecd-rootfs: https://git.launchpad.net/livecd-rootfs/tree/live- build/functions?id=8f76e539b1c8f4473dbf4627a0961bdb3732c7c6#n771 - Once the bootable buildd image work is backported to bionic, the updates and security pockets will be enabled there, too. - Even with these changes, the bootable images are built only with packages from the release pocket. If we'd like to pull in the latest packages from updates or security, we could do something like the following attached MP: https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd- rootfs/+ref/buildd-image-perform-upgrade - Is this something that we want to do? Some of my thoughts: - Snapcraft is the only group consuming the bootable images, and if snaps are always built with updates, this will save a lot of time. - The original release plan included gating bootable images on launchpad giving a +1 on the lxd tarballs. That will be less useful if the images have widely different contents. -- 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 a very plain sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1860780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860780] Re: buildd images have a very plain sources.list
** 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 a very plain sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1860780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** 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 buildd * Boot .img file using Multipass, confirm it boots - * Have launchpad team verify the other buildd artifacts are still valid + * Perform a livecd-rootfs build using the generated buildd lxd tarball [Regression Potential] - * Break existing artifacts in the buildd subproject + * Break existing artifacts in the buildd subproject * Cause buildd subproject to fail to build [Other Info] * None -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863024] Re: SRU: bootable buildd images for all releases
** 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 buildd * Boot .img file using Multipass, confirm it boots + * Have launchpad team verify the other buildd artifacts are still valid + [Regression Potential] + + * Break existing artifacts in the buildd subproject * Cause buildd subproject to fail to build [Other Info] * None -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1863024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860780] Re: buildd images have a very plain sources.list
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: buildd images have a very plain sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1860780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860780] Re: buildd images have a very plain sources.list
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860780 Title: buildd images have a very plain sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1860780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
@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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860780] Re: buildd images have a very plain sources.list
The existing buildd images will continue to include only packages from the release pocket. The bootable buildd images, however, will be changed to include packages from the updates and security pockets. ** Changed in: cloud-images Importance: Undecided => Medium ** Changed in: cloud-images 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 Ubuntu. https://bugs.launchpad.net/bugs/1860780 Title: buildd images have a very plain sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1860780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865836] Re: Touchscreen Unresponsive in Focal, but Works in Eoan
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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1865836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865836] [NEW] Touchscreen Unresponsive in Focal, but Works in Eoan
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]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input20/event4" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TOUCHSCREEN, id 11) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "AccelerationScheme" "none" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) selected scheme none/0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration factor: 2.000 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: (accel) acceleration threshold: 4 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: is tagged by udev as: Touchscreen 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event4 - ELAN9038:00 04F3:261A: device is a touch device 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse0) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/event5) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: Applying InputClass "libinput tablet catchall" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) Using input driver 'libinput' for 'ELAN9038:00 04F3:261A' 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 29 paused 0 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) ELAN9038:00 04F3:261A: always reports core events 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "Device" "/dev/input/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "_source" "server/udev" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device removed 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (**) Option "config_info" "udev:/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN9038:00/0018:04F3:261A.0001/input/input23/event5" 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) XINPUT: Adding extended input device "ELAN9038:00 04F3:261A" (type: TABLET, id 12) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: is tagged by udev as: Tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: tablet 'ELAN9038:00 04F3:261A' unknown to libwacom 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) event5 - ELAN9038:00 04F3:261A: device is a tablet 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) config/udev: Adding input device ELAN9038:00 04F3:261A (/dev/input/mouse1) 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) No input driver specified, ignoring this device. 12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) This device may have been added with another device file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1694 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 02:27:15 2020 InstallationDate: Installed on 2020-01-29 (33 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:096f Microsoft Corp. Surface Type
[Bug 1855930] Re: Build failures when specifying in focal: project=ubuntu-base and subproject=buildd
** 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. https://bugs.launchpad.net/bugs/1855930 Title: Build failures when specifying in focal: project=ubuntu-base and subproject=buildd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1855930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855930] [NEW] Build failures when specifying: project=ubuntu-base and subproject=buildd
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 5610 B of archives. After this operation, 18.4 kB of additional disk space will be used. Err:1 http://archive.ubuntu.com/ubuntu focal/main amd64 policyrcd-script-zg2 all 0.1-3 Temporary failure resolving 'archive.ubuntu.com' E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/policyrcd-script-zg2/policyrcd-script-zg2_0.1-3_all.deb Temporary failure resolving 'archive.ubuntu.com' E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? E: config/hooks/49-policy-rc-d.binary failed (exit non-zero). You should check for errors. P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... [...] This bug was introduced in this MP: https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd- rootfs/+merge/373916 To reproduce (using ubuntu-bartender from ubuntu-old-fashioned[1]): ubuntu-bartender -- --project ubuntu-base --subproject buildd --series focal See attached MP for a proposed fix. 1: https://github.com/chrisglass/ubuntu-old-fashioned ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/376597 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855930 Title: Build failures when specifying: project=ubuntu-base and subproject=buildd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1855930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837088] Re: Generate HyperV Image Gallery Builds in Bionic and Disco
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 Image Gallery Builds in Bionic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1837088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837088] Re: Generate HyperV Image Gallery Builds in Bionic and Disco
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? -- 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 Image Gallery Builds in Bionic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1837088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
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 that's scaled for the 1.25x session. The new pointer follows the mouse, but the original pointer is stationary. If I disable/re-enable fractional scaling in the same session, the duplicate pointer disappears. ** Attachment added: "two-pointers.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+attachment/5302082/+files/two-pointers.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835124] Re: growpart mishandles image filenames that end in a number
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.launchpad.net/bugs/1835124 Title: growpart mishandles image filenames that end in a number To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1835124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837088] Re: Generate HyperV Image Gallery Builds in Bionic and Disco
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/+git/livecd-rootfs/+merge/370330 ** Merge proposal linked: https://code.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs/+merge/370331 -- 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 Image Gallery Builds in Bionic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1837088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837088] [NEW] Generate HyperV Image Gallery Builds in Bionic and Disco
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-desktop-images-available-in- microsoft-hyper-v-gallery To support this, three commits need to be backported from ubuntu/master to ubuntu/disco and ubuntu/bionic: https://git.launchpad.net/livecd-rootfs/commit/?id=0e3b1e206b8ac24e22b49b40a0de1e16e3d412dd https://git.launchpad.net/livecd-rootfs/commit/?id=124d07410161427222c002bec023b7d2ca03a465 https://git.launchpad.net/livecd-rootfs/commit/?id=5a2b49950af9bf407b63ea6a5488500fbcc4 [Test Case] These images can be built with the livecd-roottfs ubuntu/master branch by specifying the ubuntu project and the desktop-preinstalled subproject. For example (using the ubuntu-bartender helper script in ubuntu-old- fashioned [1]): ubuntu-old-fashioned/scripts/ubuntu-bartender/ubuntu-bartender -- --series eoan --project ubuntu --subproject desktop-preinstalled When backported, it's expected that these images can be built for both disco and bionic with the same parameters specified: ubuntu-old-fashioned/scripts/ubuntu-bartender/ubuntu-disco-bartender -- --project ubuntu --subproject desktop-preinstalled ubuntu-old-fashioned/scripts/ubuntu-bartender/ubuntu-bionic-bartender -- --project ubuntu --subproject desktop-preinstalled 1: https://github.com/chrisglass/ubuntu-old-fashioned [Regression Potential] The binary hook used to create the HyperV image is isolated and shouldn't affect other image builds; however, that hook depends on a symbolic link to a hook in the ubuntu-cpc project. There's a possibility of future breakage if the ubuntu-cpc project hook is modified without taking into account its use in multiple places. To enable the use of a symbolic link, some logic was changed in the live-build configuration script. Previously, all files were copied over as-is. Now, symbolic links in hook directories are dereferenced and turned into regular files. In practice, this should only have an affect on two files, and that affect should be safe: livecd-rootfs $ find . -type l -print | grep hooks ./live-build/ubuntu/hooks/033-disk-image-uefi.binary ./live-build/ubuntu-cpc/hooks.d/base/series/all This may cause undesired behavior for other users of livecd-rootfs, though, that inject symbolic links into their hooks directory. ** Affects: livecd-rootfs (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/1837088 Title: Generate HyperV Image Gallery Builds in Bionic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1837088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835124] Re: growpart mishandles image filenames that end in a number
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 bug go to: https://bugs.launchpad.net/cloud-utils/+bug/1835124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835124] Re: growpart mishandles image filenames that end in a number
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}
Each partition is _not_ a block device, though, so they fail the `-b
"${DISK}p${PART}"` check.
Removing that specific check fixes this issue; however, I don't know
what ramification that has for other use cases.
As a workaround, we are renaming the image file to end with a non-
numerical suffix, growing the partition, then renaming the image back to
its original name.
--
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 bug go to:
https://bugs.launchpad.net/cloud-utils/+bug/1835124/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835124] [NEW] growpart mishandles image filenames that end in a 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 block devices that end in a number (/dev/nbd0)
# the partition is "p" (/dev/nbd0p1)
dpart="${DISK}p${PART}"
elif [ "${DISK#/dev/loop[0-9]}" != "${DISK}" ]; then
# for /dev/loop devices, sfdisk output will be p
# format also, even though there is not a device there.
dpart="${DISK}p${PART}"
fi
If the disk is an image, and the image filename ends with a number, the
partition will be "${DISK}p${PART}"; however, "${DISK}p${PART}" will not
be a block device. Thus, the partition is improperly identified as just
"${DISK}${PART}".
This gives us a failure like:
+ growpart -v -v -v disk-uefi.ext4 1
update-partition set to true
resizing 1 on disk-uefi.ext4 using resize_sfdisk_gpt
running[sfd_list][erronly] sfdisk --list --unit=S disk-uefi.ext4
6291456 sectors of 512. total size=3221225472 bytes
running[sfd_dump][erronly] sfdisk --unit=S --dump disk-uefi.ext4
## sfdisk --unit=S --dump disk-uefi.ext4
label: gpt
label-id: A9F73A73-50FD-4335-9082-1249985F154D
device: disk-uefi.ext4
unit: sectors
first-lba: 34
last-lba: 6291422
disk-uefi.ext4p1 : start= 227328, size= 4384735,
type=0FC63DAF-8483-4772-8E79-3D69D8477DE4,
uuid=C1191CD2-0753-4A53-8CD4-E6079735CA42
disk-uefi.ext4p14 : start=2048, size=8192,
type=21686148-6449-6E6F-744E-656564454649,
uuid=3A2AD377-EB6D-4689-9126-35148C003A95
disk-uefi.ext4p15 : start= 10240, size= 217088,
type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B,
uuid=98C675C8-4FF6-425C-B783-E77FDE70C967
FAILED: failed to get start and end for disk-uefi.ext41 in disk-uefi.ext4
** Affects: cloud-utils (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/1835124
Title:
growpart mishandles image filenames that end in a number
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1835124/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830823] Re: Ubuntu image builds broken for powerpc on xenial
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. https://bugs.launchpad.net/bugs/1830823 Title: Ubuntu image builds broken for powerpc on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1830823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830823] Re: Ubuntu image builds broken for powerpc on xenial
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 returned error exit status 1 dpkg: dependency problems prevent configuration of livecd-rootfs: livecd-rootfs depends on snapd; however: Package snapd is not configured yet. dpkg: error processing package livecd-rootfs (--configure): -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830823 Title: Ubuntu image builds broken for powerpc on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1830823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830823] Re: Ubuntu image builds broken for powerpc on xenial
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830823 Title: Ubuntu image builds broken for powerpc on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1830823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800681] Re: open-iscsi should not leave around the stamp file if no connections were made
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 leave around the stamp file if no connections were made To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1800681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
