[Group.of.nepali.translators] [Bug 1947281] Re: xenial/linux-gcp: 4.15.0-1111.125~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - signed - main sru-review: - signed - main - meta kernel-stable-master-bug: 1947282 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Friday, 29. October 2021 20:26 UTC + phase: Holding before Promote to Updates + phase-changed: Thursday, 04. November 2021 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED + promote-to-updates: Pending -- snap not yet in candidate synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1947279 xenial/linux-gcp/gke-kernel: bug 1947280 variant: debs versions: main: 4.15.0-.125~16.04.1 meta: 4.15.0..112 signed: 4.15.0-.125~16.04.1 source: 4.15.0-.125~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1947281 Title: xenial/linux-gcp: 4.15.0-.125~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - signed - main sru-review: - signed - main - meta kernel-stable-master-bug: 1947282 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Thursday, 04. November 2021 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- snap not yet in candidate synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1947279 xenial/linux-gcp/gke-kernel: bug 1947280 variant: debs versions: main: 4.15.0-.125~16.04.1 meta: 4.15.0..112 signed: 4.15.0-.125~16.04.1 source: 4.15.0-.125~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1947281/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1686324] Re: usb hostdev passthrough generates the wrong apparmor rules
While clearing old bugs I found this one and priority for Xenila/Zesty backports never was important to anyone. Nowadays those are on ESM support and since there is a workaround (rule overrides) and this isn't a security issue I'll set Won't Fix for those. ** Changed in: libvirt (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: libvirt (Ubuntu Zesty) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1686324 Title: usb hostdev passthrough generates the wrong apparmor rules Status in libvirt package in Ubuntu: Fix Released Status in libvirt source package in Xenial: Won't Fix Status in libvirt source package in Zesty: Won't Fix Status in libvirt source package in Artful: Fix Released Bug description: [Impact] * USB Host devices fail to add statically * The reason is that libvirt has not yet initialized usb devices * Fix by back-porting small upstream change [Test Case] * Create a VM Guest (e.g. via uvtool) * Shut down the guest * virsh edit * Add a usb hostdev from your System (check lsusb for IDs) * See the original description below for XML examples * Starting the guest will create a wrong rule "/dev/bus/usb/000/000" rw, And due to that fails to start. [Regression Potential] * The change is small and only makes certain values available to libvirt * The only thing I could think of regressing is if that virHostdevFindUSBDevice would crash on some systems, but then it would fail later on in the lifecycle even without the patch - so we should be safe IMHO. [Other Info] * I waited to be accepted upstream to be more confident which is partially why this took so long but provides some extra confidence. --- Libvirt-aa-helper seems to have a bug when adding usb passthrough devices statically. On hotplug with: $ cat sandisk-usb.xml $ virsh attach-device z-test1 sandisk-usb.xml It generates correctly: "/dev/bus/usb/003/003" rw, But if adding the same XML part to the guest xml itself it generates: "/dev/bus/usb/000/000" rw, And as a follow on issue the guest start fails with: libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/003/003: Permission denied Due to: apparmor="DENIED" operation="open" profile="libvirt-adc578cb-905f-41fc-9be2-9fb81f6a6073" name="/dev/bus/usb/003/003" pid=22879 comm="qemu-system-x86" requested_mask="wr" denied_mask="wr" fsuid=123 ouid=123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1686324/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
I used 32bit boot-repair-disk iso yesterday to try fix a grub problem. Looks like it's built on unpatched Ubuntu 17.10. My bios is now corrupt and unable to boot from USB, worse grub wasn't fixed so my tablet is now a paperweight (maybe a powerbank, suppose it has some use. Fujitsu Q584 using InsydeH20 v5.0 bios. Can't boot anything so only fix appears to involve a lot of soldering on miniature components, not something I'd be confident doing. Really disappointed Canonical consider this problem solved and have not done more to remove unpatched Ubuntu from the wild. I've read through all the comments and I don't see any fix that would work in this circumstance. I know it's an old machine but was really responsive and usable from my very brief experience on Linux. I'm concerned others may try to revive old machines with Linux and suffer same fate. ** Also affects: boot-repair Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Boot-Repair: New Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed
[Group.of.nepali.translators] [Bug 1505670] Re: python exceptions bleeding into stdout
This bug was fixed in the package squid-deb-proxy -
0.8.15ubuntu0.21.04.1
---
squid-deb-proxy (0.8.15ubuntu0.21.04.1) hirsute; urgency=medium
* apt-avahi-discover: write errors to stderr instead
of stdout so that stdout can be captured correctly.
Thanks to . Note that this is
being fixed differently (stderr and not syslog)
in the stable releases. LP: #1505670.
-- Miriam España Acebal Tue, 05 Oct 2021
13:23:08 +0200
** Changed in: squid-deb-proxy (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1505670
Title:
python exceptions bleeding into stdout
Status in squid-deb-proxy package in Ubuntu:
Fix Released
Status in squid-deb-proxy source package in Trusty:
Won't Fix
Status in squid-deb-proxy source package in Xenial:
Won't Fix
Status in squid-deb-proxy source package in Bionic:
Fix Released
Status in squid-deb-proxy source package in Focal:
Fix Released
Status in squid-deb-proxy source package in Hirsute:
Fix Released
Status in squid-deb-proxy source package in Impish:
Fix Released
Bug description:
[Impact]
As @cell explains, the problem here is that the errors are going to
stdout, not to stderr. This means apt's Acquire::http::ProxyAutoDetect
is not able to figure out what the proxy URL is.
[Test Plan]
The idea is to create a VM with several interfaces, to cache them
plus to check configuration and do the discovery. Here you can see the
test for Focal, but it has been the same behaviour for Hirsute, Bionic
and Impish.
Note: In comment #22 there's a very straightforward test (Impish)
without the need for extra ifaces.
Steps to reproduce (thanks to @cpaelzer and @sergiodj):
#0
# On the test Host install apt-cacher-ng
# you need to do so before creating the guest VM to propagate
# and configure correctly when spawned
$ sudo apt install apt-cacher-ng
# 1
# On the Host, create the IPv4 addresses and the VM. Stop the VM to
# attach the ifaces and start again the VM to log in.
$ for i in 1 2 3 4; do lxc network create testnet${i}; done
$ lxc network list
$ lxc launch ubuntu-daily:focal test-bug1505670-focal --vm
$ lxc stop test-bug1505670-focal
$ for i in 1 2 3 4; do lxc network attach testnet${i}
test-bug1505670-focal; done
$ lxc start test-bug1505670-focal
$ lxc shell test-bug1505670-focal
# Now at the VM, install prereq packages
$ sudo apt update
$ sudo apt install avahi-utils squid-deb-proxy-client
#3
# check if all are interfaces are configured
$ ip a
# (you might need to edit netplan or E/N/I to e.g. dhcp on all of
them) to have the following content (check the names of your
interfaces from the 'ip a' command above and change them if needed):
$ vim /etc/netplan/50-cloud-init.yaml
network:
version: 2
renderer: networked
ethernet:
enp5s0:
dhcp4: true
enp6s0:
dhcp4: true
enp7s0:
dhcp4: true
enp8s0:
dhcp4: true
enp09s0:
dhcp4: true
#apply the changes to the ifaces:
$ sudo netplan apply
# 4
# avahi probes all ifaces
$ avahi-browse -kprtf _apt_proxy._tcp
+;enp8s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp7s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp6s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp6s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp5s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp5s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;lo;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
=;enp8s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;fd42:701b:b04:c7ab:216:3eff:feda:f1e7;3142;
=;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;10.8.60.155;3142;
=;enp7s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;fd42:3406:c5ba:899a:216:3eff:fecd:de74;3142;
=;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;10.232.244.137;3142;
=;enp6s0;IPv6;apt-cacher-ng\032proxy\032on\032te
[Group.of.nepali.translators] [Bug 1505670] Re: python exceptions bleeding into stdout
This bug was fixed in the package squid-deb-proxy -
0.8.15ubuntu0.20.04.1
---
squid-deb-proxy (0.8.15ubuntu0.20.04.1) focal; urgency=medium
* apt-avahi-discover: write errors to stderr instead
of stdout so that stdout can be captured correctly.
Thanks to . Note that this is
being fixed differently (stderr and not syslog)
in the stable releases. LP: #1505670.
-- Miriam España Acebal Thu, 14 Oct 2021
13:41:22 +0200
** Changed in: squid-deb-proxy (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: squid-deb-proxy (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1505670
Title:
python exceptions bleeding into stdout
Status in squid-deb-proxy package in Ubuntu:
Fix Released
Status in squid-deb-proxy source package in Trusty:
Won't Fix
Status in squid-deb-proxy source package in Xenial:
Won't Fix
Status in squid-deb-proxy source package in Bionic:
Fix Released
Status in squid-deb-proxy source package in Focal:
Fix Released
Status in squid-deb-proxy source package in Hirsute:
Fix Released
Status in squid-deb-proxy source package in Impish:
Fix Released
Bug description:
[Impact]
As @cell explains, the problem here is that the errors are going to
stdout, not to stderr. This means apt's Acquire::http::ProxyAutoDetect
is not able to figure out what the proxy URL is.
[Test Plan]
The idea is to create a VM with several interfaces, to cache them
plus to check configuration and do the discovery. Here you can see the
test for Focal, but it has been the same behaviour for Hirsute, Bionic
and Impish.
Note: In comment #22 there's a very straightforward test (Impish)
without the need for extra ifaces.
Steps to reproduce (thanks to @cpaelzer and @sergiodj):
#0
# On the test Host install apt-cacher-ng
# you need to do so before creating the guest VM to propagate
# and configure correctly when spawned
$ sudo apt install apt-cacher-ng
# 1
# On the Host, create the IPv4 addresses and the VM. Stop the VM to
# attach the ifaces and start again the VM to log in.
$ for i in 1 2 3 4; do lxc network create testnet${i}; done
$ lxc network list
$ lxc launch ubuntu-daily:focal test-bug1505670-focal --vm
$ lxc stop test-bug1505670-focal
$ for i in 1 2 3 4; do lxc network attach testnet${i}
test-bug1505670-focal; done
$ lxc start test-bug1505670-focal
$ lxc shell test-bug1505670-focal
# Now at the VM, install prereq packages
$ sudo apt update
$ sudo apt install avahi-utils squid-deb-proxy-client
#3
# check if all are interfaces are configured
$ ip a
# (you might need to edit netplan or E/N/I to e.g. dhcp on all of
them) to have the following content (check the names of your
interfaces from the 'ip a' command above and change them if needed):
$ vim /etc/netplan/50-cloud-init.yaml
network:
version: 2
renderer: networked
ethernet:
enp5s0:
dhcp4: true
enp6s0:
dhcp4: true
enp7s0:
dhcp4: true
enp8s0:
dhcp4: true
enp09s0:
dhcp4: true
#apply the changes to the ifaces:
$ sudo netplan apply
# 4
# avahi probes all ifaces
$ avahi-browse -kprtf _apt_proxy._tcp
+;enp8s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp7s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp6s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp6s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp5s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;enp5s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
+;lo;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local
=;enp8s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;fd42:701b:b04:c7ab:216:3eff:feda:f1e7;3142;
=;enp8s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;10.8.60.155;3142;
=;enp7s0;IPv6;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug1505670-focal.local;fd42:3406:c5ba:899a:216:3eff:fecd:de74;3142;
=;enp7s0;IPv4;apt-cacher-ng\032proxy\032on\032test-bug1505670-focal;_apt_proxy._tcp;local;test-bug150
[Group.of.nepali.translators] [Bug 1947292] Re: xenial/linux-hwe: 4.15.0-162.170~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Fix Released => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - main - meta - signed sru-review: - signed - meta - main kernel-stable-master-bug: 1947293 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Holding before Promote to Updates - phase-changed: Wednesday, 03. November 2021 16:26 UTC + phase: Testing + phase-changed: Thursday, 04. November 2021 21:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + regression-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-162.170~16.04.1 meta: 4.15.0.162.155 signed: 4.15.0-162.170~16.04.1 source: 4.15.0-162.170~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1947292 Title: xenial/linux-hwe: 4.15.0-162.170~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-hwe source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - main - meta - signed sru-review: - signed - meta - main kernel-stable-master-bug: 1947293 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Thursday, 04. November 2021 21:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid variant: debs versions: main: 4.15.0-162.170~16.04.1 meta: 4.15.0.162.155 signed: 4.15.0-162.170~16.04.1 source: 4.15.0-162.170~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1947292/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1947281] Re: xenial/linux-gcp: 4.15.0-1111.125~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Fix Released => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - signed - main sru-review: - signed - main - meta kernel-stable-master-bug: 1947282 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Updates - phase-changed: Thursday, 04. November 2021 09:10 UTC + phase: Testing + phase-changed: Thursday, 04. November 2021 21:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- snap not yet in candidate + regression-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1947279 xenial/linux-gcp/gke-kernel: bug 1947280 variant: debs versions: main: 4.15.0-.125~16.04.1 meta: 4.15.0..112 signed: 4.15.0-.125~16.04.1 source: 4.15.0-.125~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1947281 Title: xenial/linux-gcp: 4.15.0-.125~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - signed - main sru-review: - signed - main - meta kernel-stable-master-bug: 1947282 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 04. November 2021 21:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1947279 xenial/linux-gcp/gke-kernel: bug 1947280 variant: debs versions: main: 4.15.0-.125~16.04.1 meta: 4.15.0..112 signed: 4.15.0-.125~16.04.1 source: 4.15.0-.125~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1947281/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1944676] Re: Ubuntu ESM not working in WSL
This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1 --- ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium * d/tools.postinst: - consider cloud to be "none" on any cloud-id error - purge old ua-messaging.timer/service files - keep ua-timer.timer disabled if ua-messaging.timer was disabled by the user - properly configure both ubuntu-advantage-timer and ubuntu-advantage-licence-check logs * d/tools.postrm: - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs during purge * systemd: - remove ua-messaging.timer/service - add new ua-timer.timer that runs every 6 hours - add new ua-license_check.timer that runs every 5 minutes only if activated by ua-license-check.path * New upstream release 27.3 (LP: #1942929) - ros: + add beta support to enable ros and ros-updates + add support for "required services" so that esm-infra and esm-apps get auto-enabled when enabling ros or ros-updates + add support for "dependent services" so that user gets prompted to disable ros/ros-updates if they disable esm-infra/esm-apps - fips: + allow fips on GCP bionic now that optimized kernel is ready + disallow enabling fips on focal on clouds until cloud-optimized focal fips-certified kernel is ready (LP: #1939449, LP: #1939932) + print warning about generic fips kernel if cloud-id fails - cloud: + rely only on cloud-id to determine cloud type (LP: #1940131) + catch errors when determining cloud type (LP: #1938207, LP: #1944676) (GH: #1541) - azure: + bump IMDS API version to support Azure published images - cli: + collect-logs command that creates a tar file with debug-relevant logs and status info (GH: #463) + clean locks on exceptions more thoroughly to avoid false "Operation in progress" status messages + retain past service state after detach + shows better error message when a port value in a proxy is invalid - non-unicode locale support: + remove unicode-only characters from help file + don't print unicode-only characters in ua fix if non-utf8 locale (GH: #1463) - logrotate: + add logrotate functionality for ubuntu-advantage-timer.log. + Fix root:root logrotate permissions. - ua-timer.timer: + introduce a single systemd timer to handle ua recurring jobs + timer runs every 2 hours to support most frequent timer job + recurring job intervals are configurable in uaclient.conf + individual jobs are disabled if their interval is set to 0 - status job: + update ua status every 12 hours - messaging job: + update APT/MOTD ESM messaging every 6 hours - metering job: + disabled until infrastructure is ready + for attached machines only, periodically update contract server with status information for proper contract metering - ua-license-check.timer: + only runs on LTS GCP instances that are not attached + runs every 5 minutes to check if gcp instance has license required to auto-attach - logs: + fixes duplicate logging (GH: #553) - tests and support: + remove groovy integration tests + various improvements to integration tests -- Grant Orndorff Tue, 21 Sep 2021 09:02:06 -0400 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1944676 Title: Ubuntu ESM not working in WSL Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Hirsute: Fix Released Status in ubuntu-advantage-tools source package in Impish: Fix Released Bug description: [Impact] This bug impacts users which are running on environments where '/usr/bin/cloud-id' is present, but returns any error (even for valid reasons, like cloud-init being installed on the system, but disabled, for example). UA client will raise this error while trying to use this tool to detect the cloud. The solution to this problem is to rely only on cloud-id when trying to determine the cloud type, and assuming not on cloud when the command is not present or if it fails. https://github.com/canonical/ubuntu-advantage-client/commit/f968c46a686a8128af1ead85a4b86b9a1a84643f and https://github.com/canonical/ubuntu-advantage-client/commit/f6fbcee792cf42cc67e3ced02815b7d552dee19f [Test Case] To reproduce: Wit
[Group.of.nepali.translators] [Bug 1939932] Re: Ubuntu PRO Focal on AWS and Azure should not install the generic FIPS kernel via ubuntu-fips metapackage
This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1
---
ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium
* d/tools.postinst:
- consider cloud to be "none" on any cloud-id error
- purge old ua-messaging.timer/service files
- keep ua-timer.timer disabled if ua-messaging.timer was disabled by
the user
- properly configure both ubuntu-advantage-timer and
ubuntu-advantage-licence-check logs
* d/tools.postrm:
- remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
during purge
* systemd:
- remove ua-messaging.timer/service
- add new ua-timer.timer that runs every 6 hours
- add new ua-license_check.timer that runs every 5 minutes only if
activated by ua-license-check.path
* New upstream release 27.3 (LP: #1942929)
- ros:
+ add beta support to enable ros and ros-updates
+ add support for "required services" so that esm-infra and esm-apps
get auto-enabled when enabling ros or ros-updates
+ add support for "dependent services" so that user gets prompted to
disable ros/ros-updates if they disable esm-infra/esm-apps
- fips:
+ allow fips on GCP bionic now that optimized kernel is ready
+ disallow enabling fips on focal on clouds until cloud-optimized focal
fips-certified kernel is ready (LP: #1939449, LP: #1939932)
+ print warning about generic fips kernel if cloud-id fails
- cloud:
+ rely only on cloud-id to determine cloud type (LP: #1940131)
+ catch errors when determining cloud type
(LP: #1938207, LP: #1944676) (GH: #1541)
- azure:
+ bump IMDS API version to support Azure published images
- cli:
+ collect-logs command that creates a tar file with debug-relevant logs
and status info (GH: #463)
+ clean locks on exceptions more thoroughly to avoid false "Operation in
progress" status messages
+ retain past service state after detach
+ shows better error message when a port value in a proxy is invalid
- non-unicode locale support:
+ remove unicode-only characters from help file
+ don't print unicode-only characters in ua fix if non-utf8 locale
(GH: #1463)
- logrotate:
+ add logrotate functionality for ubuntu-advantage-timer.log.
+ Fix root:root logrotate permissions.
- ua-timer.timer:
+ introduce a single systemd timer to handle ua recurring jobs
+ timer runs every 2 hours to support most frequent timer job
+ recurring job intervals are configurable in uaclient.conf
+ individual jobs are disabled if their interval is set to 0
- status job:
+ update ua status every 12 hours
- messaging job:
+ update APT/MOTD ESM messaging every 6 hours
- metering job:
+ disabled until infrastructure is ready
+ for attached machines only, periodically update contract server with
status information for proper contract metering
- ua-license-check.timer:
+ only runs on LTS GCP instances that are not attached
+ runs every 5 minutes to check if gcp instance has license required to
auto-attach
- logs:
+ fixes duplicate logging (GH: #553)
- tests and support:
+ remove groovy integration tests
+ various improvements to integration tests
-- Grant Orndorff Tue, 21 Sep 2021
09:02:06 -0400
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1939932
Title:
Ubuntu PRO Focal on AWS and Azure should not install the generic FIPS
kernel via ubuntu-fips metapackage
Status in ubuntu-advantage-tools package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
Fix Released
Status in ubuntu-advantage-tools source package in Focal:
Fix Released
Status in ubuntu-advantage-tools source package in Hirsute:
Fix Released
Status in ubuntu-advantage-tools source package in Impish:
Fix Released
Bug description:
[Impact]
This bug impacts users on AWS or Azure, trying to enable FIPS/FIPS
updates on Focal images. Trying to install a non-cloud-optimized FIPS
kernel may lead to unwanted behavior on those clouds, including
inability to boot to the systems.
Although Focal has a FIPS certified kernel, the AWS adapted kernel is
not ready yet. There will be in the future a cloud-optimized version
of the FIPS kernel, and then users will be able to install it.
With the applied fix, UA will show a message saying that the kernel is
not available instead of showing any error. If the user really wants
to install FIPS, there is a feature override
("allow_
[Group.of.nepali.translators] [Bug 1938207] Re: ubuntu-advantage-tools.postinst and cloud-id are not robust against failure
This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1 --- ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium * d/tools.postinst: - consider cloud to be "none" on any cloud-id error - purge old ua-messaging.timer/service files - keep ua-timer.timer disabled if ua-messaging.timer was disabled by the user - properly configure both ubuntu-advantage-timer and ubuntu-advantage-licence-check logs * d/tools.postrm: - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs during purge * systemd: - remove ua-messaging.timer/service - add new ua-timer.timer that runs every 6 hours - add new ua-license_check.timer that runs every 5 minutes only if activated by ua-license-check.path * New upstream release 27.3 (LP: #1942929) - ros: + add beta support to enable ros and ros-updates + add support for "required services" so that esm-infra and esm-apps get auto-enabled when enabling ros or ros-updates + add support for "dependent services" so that user gets prompted to disable ros/ros-updates if they disable esm-infra/esm-apps - fips: + allow fips on GCP bionic now that optimized kernel is ready + disallow enabling fips on focal on clouds until cloud-optimized focal fips-certified kernel is ready (LP: #1939449, LP: #1939932) + print warning about generic fips kernel if cloud-id fails - cloud: + rely only on cloud-id to determine cloud type (LP: #1940131) + catch errors when determining cloud type (LP: #1938207, LP: #1944676) (GH: #1541) - azure: + bump IMDS API version to support Azure published images - cli: + collect-logs command that creates a tar file with debug-relevant logs and status info (GH: #463) + clean locks on exceptions more thoroughly to avoid false "Operation in progress" status messages + retain past service state after detach + shows better error message when a port value in a proxy is invalid - non-unicode locale support: + remove unicode-only characters from help file + don't print unicode-only characters in ua fix if non-utf8 locale (GH: #1463) - logrotate: + add logrotate functionality for ubuntu-advantage-timer.log. + Fix root:root logrotate permissions. - ua-timer.timer: + introduce a single systemd timer to handle ua recurring jobs + timer runs every 2 hours to support most frequent timer job + recurring job intervals are configurable in uaclient.conf + individual jobs are disabled if their interval is set to 0 - status job: + update ua status every 12 hours - messaging job: + update APT/MOTD ESM messaging every 6 hours - metering job: + disabled until infrastructure is ready + for attached machines only, periodically update contract server with status information for proper contract metering - ua-license-check.timer: + only runs on LTS GCP instances that are not attached + runs every 5 minutes to check if gcp instance has license required to auto-attach - logs: + fixes duplicate logging (GH: #553) - tests and support: + remove groovy integration tests + various improvements to integration tests -- Grant Orndorff Tue, 21 Sep 2021 09:02:06 -0400 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1938207 Title: ubuntu-advantage-tools.postinst and cloud-id are not robust against failure Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Hirsute: Fix Released Status in ubuntu-advantage-tools source package in Impish: Fix Released Bug description: [Impact] If cloud-id fails in a different way from what our postinst currently checks for, then the postinst script will fail, breaking whatever apt process was running. We fixed this by changing the line that calls cloud-id to cloud_id=$(cloud-id 2>/dev/null) || cloud_id="" The commit with this change is here: https://github.com/canonical/ubuntu-advantage- client/commit/8ac323b1f2e2031afa8018112d20479085c0e4f7 By doing this, any error in cloud-id will be handled by assuming we are not on a cloud. This is a safe assumption for the purposes of our postinst script. [Test Plan] You can verify that this problem is addressed in version 27.3 by running the
[Group.of.nepali.translators] [Bug 1940131] Re: sudo ua attach is not working
This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1 --- ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium * d/tools.postinst: - consider cloud to be "none" on any cloud-id error - purge old ua-messaging.timer/service files - keep ua-timer.timer disabled if ua-messaging.timer was disabled by the user - properly configure both ubuntu-advantage-timer and ubuntu-advantage-licence-check logs * d/tools.postrm: - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs during purge * systemd: - remove ua-messaging.timer/service - add new ua-timer.timer that runs every 6 hours - add new ua-license_check.timer that runs every 5 minutes only if activated by ua-license-check.path * New upstream release 27.3 (LP: #1942929) - ros: + add beta support to enable ros and ros-updates + add support for "required services" so that esm-infra and esm-apps get auto-enabled when enabling ros or ros-updates + add support for "dependent services" so that user gets prompted to disable ros/ros-updates if they disable esm-infra/esm-apps - fips: + allow fips on GCP bionic now that optimized kernel is ready + disallow enabling fips on focal on clouds until cloud-optimized focal fips-certified kernel is ready (LP: #1939449, LP: #1939932) + print warning about generic fips kernel if cloud-id fails - cloud: + rely only on cloud-id to determine cloud type (LP: #1940131) + catch errors when determining cloud type (LP: #1938207, LP: #1944676) (GH: #1541) - azure: + bump IMDS API version to support Azure published images - cli: + collect-logs command that creates a tar file with debug-relevant logs and status info (GH: #463) + clean locks on exceptions more thoroughly to avoid false "Operation in progress" status messages + retain past service state after detach + shows better error message when a port value in a proxy is invalid - non-unicode locale support: + remove unicode-only characters from help file + don't print unicode-only characters in ua fix if non-utf8 locale (GH: #1463) - logrotate: + add logrotate functionality for ubuntu-advantage-timer.log. + Fix root:root logrotate permissions. - ua-timer.timer: + introduce a single systemd timer to handle ua recurring jobs + timer runs every 2 hours to support most frequent timer job + recurring job intervals are configurable in uaclient.conf + individual jobs are disabled if their interval is set to 0 - status job: + update ua status every 12 hours - messaging job: + update APT/MOTD ESM messaging every 6 hours - metering job: + disabled until infrastructure is ready + for attached machines only, periodically update contract server with status information for proper contract metering - ua-license-check.timer: + only runs on LTS GCP instances that are not attached + runs every 5 minutes to check if gcp instance has license required to auto-attach - logs: + fixes duplicate logging (GH: #553) - tests and support: + remove groovy integration tests + various improvements to integration tests -- Grant Orndorff Tue, 21 Sep 2021 09:02:06 -0400 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1940131 Title: sudo ua attach is not working Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Hirsute: Fix Released Status in ubuntu-advantage-tools source package in Impish: Fix Released Bug description: [Impact] This bug impacts users which: - Do not have the '/usr/bin/cloud-id' command in their system, - Do have the '/var/lib/cloud/data/result.json' file in their system, and - Have a non-standard (by cloud-init definitions) content in the '/var/lib/cloud/data/result.json' file. This is an unusual situation, given that the presence of the 'result.json' file with the absence of the 'cloud-id' command is observed on official Trusty images, but from Xenial onwards 'cloud-id' should be there. Even in the case where the command is not there, the file generated by cloud-init will have the required information. Since we are doing the SRU process for Xenial onwards, the solution for those problems is to rely only o
[Group.of.nepali.translators] [Bug 1939449] Re: Ubuntu Pro UA fails to enable fips-updates on 20.04
This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1
---
ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium
* d/tools.postinst:
- consider cloud to be "none" on any cloud-id error
- purge old ua-messaging.timer/service files
- keep ua-timer.timer disabled if ua-messaging.timer was disabled by
the user
- properly configure both ubuntu-advantage-timer and
ubuntu-advantage-licence-check logs
* d/tools.postrm:
- remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs
during purge
* systemd:
- remove ua-messaging.timer/service
- add new ua-timer.timer that runs every 6 hours
- add new ua-license_check.timer that runs every 5 minutes only if
activated by ua-license-check.path
* New upstream release 27.3 (LP: #1942929)
- ros:
+ add beta support to enable ros and ros-updates
+ add support for "required services" so that esm-infra and esm-apps
get auto-enabled when enabling ros or ros-updates
+ add support for "dependent services" so that user gets prompted to
disable ros/ros-updates if they disable esm-infra/esm-apps
- fips:
+ allow fips on GCP bionic now that optimized kernel is ready
+ disallow enabling fips on focal on clouds until cloud-optimized focal
fips-certified kernel is ready (LP: #1939449, LP: #1939932)
+ print warning about generic fips kernel if cloud-id fails
- cloud:
+ rely only on cloud-id to determine cloud type (LP: #1940131)
+ catch errors when determining cloud type
(LP: #1938207, LP: #1944676) (GH: #1541)
- azure:
+ bump IMDS API version to support Azure published images
- cli:
+ collect-logs command that creates a tar file with debug-relevant logs
and status info (GH: #463)
+ clean locks on exceptions more thoroughly to avoid false "Operation in
progress" status messages
+ retain past service state after detach
+ shows better error message when a port value in a proxy is invalid
- non-unicode locale support:
+ remove unicode-only characters from help file
+ don't print unicode-only characters in ua fix if non-utf8 locale
(GH: #1463)
- logrotate:
+ add logrotate functionality for ubuntu-advantage-timer.log.
+ Fix root:root logrotate permissions.
- ua-timer.timer:
+ introduce a single systemd timer to handle ua recurring jobs
+ timer runs every 2 hours to support most frequent timer job
+ recurring job intervals are configurable in uaclient.conf
+ individual jobs are disabled if their interval is set to 0
- status job:
+ update ua status every 12 hours
- messaging job:
+ update APT/MOTD ESM messaging every 6 hours
- metering job:
+ disabled until infrastructure is ready
+ for attached machines only, periodically update contract server with
status information for proper contract metering
- ua-license-check.timer:
+ only runs on LTS GCP instances that are not attached
+ runs every 5 minutes to check if gcp instance has license required to
auto-attach
- logs:
+ fixes duplicate logging (GH: #553)
- tests and support:
+ remove groovy integration tests
+ various improvements to integration tests
-- Grant Orndorff Tue, 21 Sep 2021
09:02:06 -0400
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1939449
Title:
Ubuntu Pro UA fails to enable fips-updates on 20.04
Status in ubuntu-advantage-tools package in Ubuntu:
Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
Fix Released
Status in ubuntu-advantage-tools source package in Focal:
Fix Released
Status in ubuntu-advantage-tools source package in Hirsute:
Fix Released
Status in ubuntu-advantage-tools source package in Impish:
Fix Released
Bug description:
[Impact]
This bug impacts users on AWS, trying to enable FIPS/FIPS updates on
Focal images. There is a missing package, 'ubuntu-aws-fips', which
causes the installation to fail.
This package is missing because, although Focal has a FIPS certified
kernel, the AWS adapted kernel is not ready yet. There will be in the
future a cloud-optimized version of the FIPS kernel, and then users
will be able to install it.
With the applied fix, UA will show a message saying that the kernel is
not available instead of showing an error. If the user really wants to
install FIPS, there is a feature override
("allow_default_fips_metapackage_on_focal_cloud") which will install
the default kernel.
[Te
[Group.of.nepali.translators] [Bug 1942929] Re: [SRU] ubuntu-advantage-tools (27.2.2 -> 27.3) Xenial, Bionic, Focal, Hirsute
This bug was fixed in the package ubuntu-advantage-tools - 27.3~21.10.1 --- ubuntu-advantage-tools (27.3~21.10.1) impish; urgency=medium * d/tools.postinst: - consider cloud to be "none" on any cloud-id error - purge old ua-messaging.timer/service files - keep ua-timer.timer disabled if ua-messaging.timer was disabled by the user - properly configure both ubuntu-advantage-timer and ubuntu-advantage-licence-check logs * d/tools.postrm: - remove ubuntu-advantage-timer and ubuntu-advantage-license-check logs during purge * systemd: - remove ua-messaging.timer/service - add new ua-timer.timer that runs every 6 hours - add new ua-license_check.timer that runs every 5 minutes only if activated by ua-license-check.path * New upstream release 27.3 (LP: #1942929) - ros: + add beta support to enable ros and ros-updates + add support for "required services" so that esm-infra and esm-apps get auto-enabled when enabling ros or ros-updates + add support for "dependent services" so that user gets prompted to disable ros/ros-updates if they disable esm-infra/esm-apps - fips: + allow fips on GCP bionic now that optimized kernel is ready + disallow enabling fips on focal on clouds until cloud-optimized focal fips-certified kernel is ready (LP: #1939449, LP: #1939932) + print warning about generic fips kernel if cloud-id fails - cloud: + rely only on cloud-id to determine cloud type (LP: #1940131) + catch errors when determining cloud type (LP: #1938207, LP: #1944676) (GH: #1541) - azure: + bump IMDS API version to support Azure published images - cli: + collect-logs command that creates a tar file with debug-relevant logs and status info (GH: #463) + clean locks on exceptions more thoroughly to avoid false "Operation in progress" status messages + retain past service state after detach + shows better error message when a port value in a proxy is invalid - non-unicode locale support: + remove unicode-only characters from help file + don't print unicode-only characters in ua fix if non-utf8 locale (GH: #1463) - logrotate: + add logrotate functionality for ubuntu-advantage-timer.log. + Fix root:root logrotate permissions. - ua-timer.timer: + introduce a single systemd timer to handle ua recurring jobs + timer runs every 2 hours to support most frequent timer job + recurring job intervals are configurable in uaclient.conf + individual jobs are disabled if their interval is set to 0 - status job: + update ua status every 12 hours - messaging job: + update APT/MOTD ESM messaging every 6 hours - metering job: + disabled until infrastructure is ready + for attached machines only, periodically update contract server with status information for proper contract metering - ua-license-check.timer: + only runs on LTS GCP instances that are not attached + runs every 5 minutes to check if gcp instance has license required to auto-attach - logs: + fixes duplicate logging (GH: #553) - tests and support: + remove groovy integration tests + various improvements to integration tests -- Grant Orndorff Tue, 21 Sep 2021 09:02:06 -0400 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1942929 Title: [SRU] ubuntu-advantage-tools (27.2.2 -> 27.3) Xenial, Bionic, Focal, Hirsute Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Hirsute: Fix Released Status in ubuntu-advantage-tools source package in Impish: Fix Released Bug description: [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * more robust error handling when determining the cloud we're on LP: #1940131 LP: #1938207 LP: #1944676 * disallows fips on focal aws/azure LP: #1939449 LP: #1939932 * adds/changes to ua-related recurring jobs: - change in frequency to existing job: updates the apt and motd esm update messaging: every 6 hours - new job: updates the contract details and status: every 12 hours - new job: ONLY ON GCP (implemented as separate timer that is only activated on GCP LTS when not attached)
[Group.of.nepali.translators] [Bug 1947281] Re: xenial/linux-gcp: 4.15.0-1111.125~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - signed - main sru-review: - signed - main - meta kernel-stable-master-bug: 1947282 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Thursday, 04. November 2021 21:53 UTC + phase: Holding before Promote to Updates + phase-changed: Friday, 05. November 2021 03:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED + promote-to-updates: Pending -- snap not yet in candidate synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1947279 xenial/linux-gcp/gke-kernel: bug 1947280 variant: debs versions: main: 4.15.0-.125~16.04.1 meta: 4.15.0..112 signed: 4.15.0-.125~16.04.1 source: 4.15.0-.125~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1947281 Title: xenial/linux-gcp: 4.15.0-.125~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - meta - signed - main sru-review: - signed - main - meta kernel-stable-master-bug: 1947282 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Updates phase-changed: Friday, 05. November 2021 03:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- snap not yet in candidate synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-gcp/gcp-kernel: bug 1947279 xenial/linux-gcp/gke-kernel: bug 1947280 variant: debs versions: main: 4.15.0-.125~16.04.1 meta: 4.15.0..112 signed: 4.15.0-.125~16.04.1 source: 4.15.0-.125~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1947281/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1947273] Re: xenial/linux-azure: 4.15.0-1126.139~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - signed - meta - main sru-review: - meta - main - signed kernel-stable-master-bug: 1947275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Testing - phase-changed: Wednesday, 27. October 2021 02:25 UTC + phase: Holding before Promote to Updates + phase-changed: Friday, 05. November 2021 03:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED + promote-to-updates: Pending -- snap not yet in candidate synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-azure/azure-kernel: bug 1947272 variant: debs versions: main: 4.15.0-1126.139~16.04.1 meta: 4.15.0.1126.117 signed: 4.15.0-1126.139~16.04.1 source: 4.15.0-1126.139~16.04.1 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1947273 Title: xenial/linux-azure: 4.15.0-1126.139~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 1 delta: promote-to-proposed: - signed - meta - main sru-review: - meta - main - signed kernel-stable-master-bug: 1947275 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Updates phase-changed: Friday, 05. November 2021 03:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- snap not yet in candidate synthetic: :promote-to-as-proposed: Invalid trackers: xenial/linux-azure/azure-kernel: bug 1947272 variant: debs versions: main: 4.15.0-1126.139~16.04.1 meta: 4.15.0.1126.117 signed: 4.15.0-1126.139~16.04.1 source: 4.15.0-1126.139~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1947273/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
