[Touch-packages] [Bug 1677668] Re: no GARPs during ephemeral boot
Cloud-init now prefers dhcpcd over dhclient, which includes RFC 5227 support. Closing. ** Changed in: cloud-init (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1677668 Title: no GARPs during ephemeral boot Status in MAAS: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Deploys time out with an error on the console that says, "Can not apply stage final, no datasource found! Likely bad things to come!" How to duplicate: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) 1) Rack Controller and Region Controller in different VLANs 2) Use Cisco ASA as the router with "ARP Inspection" enabled 3) Clear the router ARP cache 4) Deploy 2 maas machines with interfaces set to "Static assign" 5) Observe deploys successfully 6) Release both machines and swap IP's. 7) Redeploy the same 2 machines 8) Observe deploy failure with the machine consoles stuck in the "ubuntu login" screen with "Can not apply stage final, no datasource Found! Likely bad things to come!" The root cause is that during ephemeral PXE booting, no GARPs are sent, which in our environment will cause our router (Cisco ASA) to hold on to ARP table entries until it expires (default= 4 hours). Then combined with ASA feature "ARP Inspection" will drop packets from a MaaS machine using the previously used IP from a different MaaS machine. The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily. Running tcpdump on the Rack Controller, showed no GARPs from the deploying MaaS machine. If there were GARPs sent, then the router would refresh its ARP cache thus avoiding the ARP Inspection dropping. [Excerpt from Cisco ASA] http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf When you enable ARP inspection, the ASA compares the MAC address, IP address, and source interface in all ARP packets to static entries in the ARP table, and takes the following actions: • If the IP address, MAC address, and source interface match an ARP entry, the packet is passed through. • If there is a mismatch between the MAC address, the IP address, or the interface, then the ASA drops the packet. • If the ARP packet does not match any entries in the static ARP table, then you can set the ASA to either forward the packet out all interfaces (flood), or to drop the packet. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1677668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675571] Re: Cloud-init update renders secondary addresses to be incompatible with standard tools
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1675571
Title:
Cloud-init update renders secondary addresses to be incompatible with
standard tools
Status in cloud-init:
Expired
Status in curtin:
Confirmed
Status in cloud-init package in Ubuntu:
Won't Fix
Status in resolvconf package in Ubuntu:
New
Status in resolvconf package in Debian:
Won't Fix
Bug description:
The change of how cloud-init renders
/etc/network/interface.d/50-cloud-init.cfg, standard tools no longer work as
expected:
* resolvconf will nullify nameservers
* if* commands ignore secondary addresses
[ORIGINAL REPORT]
Regresion from Bug #1657940.
When provisioning with multiple eth0 addresses, /etc/resolv.conf is
empty:
Consider:
root@tester:~# cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 138.197.98.102
dns-nameservers 8.8.8.8 8.8.4.4
gateway 138.197.96.1
netmask 255.255.240.0
# control-alias eth0
iface eth0 inet static
address 10.17.0.11
netmask 255.255.0.0
Which then yields an empty /etc/resolv.conf:
root@tester:/run/resolvconf# cat interface/eth0.inet
root@tester:/run/resolvconf# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
The problem is that resolvconfg does pattern matching for eth*.inet.
The second definition of eth0 has no nameserver and therefore
overrides the definition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1675571/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060326] [NEW] unnattended upgrades stuck burning 100% cpu
Public bug reported: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2060326 Title: unnattended upgrades stuck burning 100% cpu Status in unattended-upgrades package in Ubuntu: New Bug description: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2060326] Re: unnattended upgrades stuck burning 100% cpu
** Attachment added: "strace.40801" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+attachment/5761743/+files/strace.40801 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2060326 Title: unnattended upgrades stuck burning 100% cpu Status in unattended-upgrades package in Ubuntu: New Bug description: For the last hour or so, unattended upgrades has been stuck burning 100% of a cpu. series: noble version: 2.9.1+nmu4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations
** Changed in: cloud-utils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034967 Title: cloud-init & cloud-guest-utils are installed on non-cloud installations Status in cloud-init package in Ubuntu: Invalid Status in cloud-utils package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: New Bug description: ~$ apt-cache rdepends --installed cloud-init cloud-init Reverse Depends: cloud-guest-utils ~$ apt-cache rdepends --installed cloud-guest-utils cloud-guest-utils Reverse Depends: |cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations
** Also affects: subiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034967 Title: cloud-init & cloud-guest-utils are installed on non-cloud installations Status in cloud-init package in Ubuntu: Invalid Status in cloud-utils package in Ubuntu: New Status in subiquity package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: New Bug description: ~$ apt-cache rdepends --installed cloud-init cloud-init Reverse Depends: cloud-guest-utils ~$ apt-cache rdepends --installed cloud-guest-utils cloud-guest-utils Reverse Depends: |cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034967] Re: cloud-init & cloud-guest-utils are installed on non-cloud installations
** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034967 Title: cloud-init & cloud-guest-utils are installed on non-cloud installations Status in cloud-init package in Ubuntu: Invalid Status in cloud-utils package in Ubuntu: New Status in subiquity package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: ~$ apt-cache rdepends --installed cloud-init cloud-init Reverse Depends: cloud-guest-utils ~$ apt-cache rdepends --installed cloud-guest-utils cloud-guest-utils Reverse Depends: |cloud-init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2034967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2009317] Re: All Snaps Broken After Release Upgrade
I can do that. Which logs would be most useful? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2009317 Title: All Snaps Broken After Release Upgrade Status in apparmor package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Status in apparmor source package in Jammy: Confirmed Status in ubuntu-release-upgrader source package in Jammy: Incomplete Status in apparmor source package in Kinetic: Confirmed Status in ubuntu-release-upgrader source package in Kinetic: Incomplete Bug description: isa~ lsb_release -rd No LSB modules are available. Description: Ubuntu Lunar Lobster (development branch) Release: 23.04 Expected behavior: == Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), they should also work after. Actual behavior: == Snaps worked before do-release-upgrade, NONE work after. Printed warning is useless. Debugging requires secondary device. This should be a trivial fix (re-enable apparmor service at the end of do-release-upgrade). isa~ firefox snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks Please make sure that the snapd.apparmor service is enabled and started. isa~ systemctl status snapd.apparmor ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; preset: enabled) Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago Main PID: 826 (code=exited, status=0/SUCCESS) CPU: 43.722s Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed internally by snapd. Notice: journal has been rotated since unit was started, output may be incomplete. It looks like during the release upgrade apparmor was disabled and needs to be re-enabled. isa~ systemctl status apparmor ○ apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ isa~ systemctl start apparmor Notes: == This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the same device. This does NOT happen on all devices (my other device didn't hit this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience - debugging requires a secondary device because Ubuntu browsers are snap-based. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts
Debdiff in the attached enables dhclient to execute dhclient with -sf /bin/true ** Patch added: "isc-dhcp-apparmor-scripts-disable-fix.debdiff" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+attachment/5654529/+files/isc-dhcp-apparmor-scripts-disable-fix.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2011628 Title: Apparmor Disallows Disabling Dhclient Scripts Status in isc-dhcp package in Ubuntu: New Bug description: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2011628] [NEW] Apparmor Disallows Disabling Dhclient Scripts
Public bug reported: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2011628 Title: Apparmor Disallows Disabling Dhclient Scripts Status in isc-dhcp package in Ubuntu: New Bug description: In some cases, it may be desirable to disable dhclient scripts. By default /sbin/dhclient-script is used, and some others are allowed by the apparmor profile. Without Apparmor, disabling hook scripts can be accomplished with flags -sf /bin/true, but with apparmor enabled this gets blocked: execve (/bin/true, ...): Permission denied Unfortunately dhclient doesn't appear to provide any other mechanism for disabling hook scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008149] [NEW] Bluetooth Audio Broken After Suspend
Public bug reported: Release: Description:Ubuntu 22.10 Release:22.10 Package Version: isa~ apt-cache policy bluez bluez: Installed: 5.65-0ubuntu1 Candidate: 5.65-0ubuntu1 Version table: *** 5.65-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Hardware: = Model: Apple Inc. MacBookPro9,2 isa~ lsusb | grep -i blue Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Kmods: == bluetooth 827392 54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm Symptom: Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know. I can test proposed fixes. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debug mode logs" https://bugs.launchpad.net/bugs/2008149/+attachment/5649257/+files/bluetooth.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2008149 Title: Bluetooth Audio Broken After Suspend Status in bluez package in Ubuntu: New Bug description: Release: Description: Ubuntu 22.10 Release: 22.10 Package Version: isa~ apt-cache policy bluez bluez: Installed: 5.65-0ubuntu1 Candidate: 5.65-0ubuntu1 Version table: *** 5.65-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Hardware: = Model: Apple Inc. MacBookPro9,2 isa~ lsusb | grep -i blue Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Kmods: == bluetooth 827392 54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm Symptom: Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know. I can test proposed fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2008149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1997124] Re: Netplan/Systemd/Cloud-init/Dbus Race
> Separately we really ought to port networkd from dbus communication to varlink such that it can be used safely on critical boot path. The rest of the Systemd critical components are already using varlink. +1 > did you mean to mark Ubuntu(Systemd) as affected? Yes, I'll update that thanks. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1997124 Title: Netplan/Systemd/Cloud-init/Dbus Race Status in cloud-init: New Status in systemd package in Ubuntu: New Bug description: Cloud-init is seeing intermittent failures while running `netplan apply`, which appears to be caused by a missing resource at the time of call. The symptom in cloud-init logs looks like: Running ['netplan', 'apply'] resulted in stderr output: Failed to connect system bus: No such file or directory I think that this error[1] is likely caused by cloud-init running netplan apply too early in boot process (before dbus is active). Today I stumbled upon this error which was hit in MAAS[2]. We have also hit it intermittently during tests (we didn't have a reproducer). Realizing that this may not be a cloud-init error, but possibly a dependency bug between dbus/systemd we decided to file this bug for broader visibility to other projects. I will follow up this initial report with some comments from our discussion earlier. [1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801 [2] https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1997124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871176] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Also experienced on an lxd vm when lvm2 is uninstalled and subsequently reinstalled. root@cloudinit-0721-232304wnvzml11:~# apt install lvm2 Reading package lists... Done Building dependency tree Reading state information... Done lvm2 is already the newest version (2.03.07-1ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor p reset: enabled) Active: inactive (dead) Docs: man:lvmpolld(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.4.0-1071-kvm W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays. W: mdadm: failed to auto-generate temporary mdadm.conf file. Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) root@cloudinit-0721-232304wnvzml11:~# echo $? 100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871176 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: hayden@t470s:~$ sudo apt-get install gnome-boxes [sudo] password for hayden: Reading package lists... Done Building dependency tree Reading state information... Done gnome-boxes is already the newest version (3.36.2-1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor preset: enabled) Active: active (exited) since Mon 2020-04-06 09:33:50 EDT; 4h 10min ago Docs: man:lvmpolld(8) Tasks: 0 (limit: 23811) Memory: 0B CGroup: /system.slice/lvm2-lvmpolld.service Apr 06 09:33:50 t470s systemd[1]: Starting LSB: LVM2 poll daemon... Apr 06 09:33:50 t470s systemd[1]: Started LSB: LVM2 poll daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu2) ... update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 Date: Mon Apr 6 13:38:10 2020 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933537] Re: add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos
This is a duplicate of LP#1862764 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1933537 Title: add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos Status in software-properties package in Ubuntu: New Bug description: PPAs are third party repositories. for security reasons, PGP keys for these must not be placed in /etc/apt/trusted.gpg.d, according to this document: https://wiki.debian.org/DebianRepository/UseThirdParty they should instead be saved to /usr/share/keyrings and the generated .list file for the repo added should refer to its particular key by using a [signed-by=/usr/share/keyrings/...] argument. this ensures that the downloaded PGP key will only be used to verify a particular repository and is not globally available to verify package lists of all configured repositories (as are all keys found in /etc/apt/trusted.gpg.d). please fix add-apt-repository accordingly. Ubuntu 20.04.2 LTS software-properties-common 0.98.9.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1933537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
