[Group.of.nepali.translators] [Bug 1771914] Re: release-upgrade-motd can't update message via apt proxy
This bug was fixed in the package update-manager - 1:16.04.16
---
update-manager (1:16.04.16) xenial; urgency=medium
* Use HTTPS for changelogs.ubuntu.com (LP: #1744318)
* Add support for HTTPS proxies; this breaks
UpdateManager.Core.utils.init_proxy()
API - the return value is now a dict, rather than a string (LP: #1771914).
-- Julian Andres Klode Tue, 20 Aug 2019 13:59:31
+0200
** Changed in: update-manager (Ubuntu Xenial)
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/1771914
Title:
release-upgrade-motd can't update message via apt proxy
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Xenial:
Fix Released
Status in update-manager source package in Bionic:
Fix Released
Bug description:
[Impact]
apt proxy settings are not applied to https urls, and thus the
release-upgrade-motd script fails, and upgrades from bionic to new versions
won't be detected either, if you need to use a proxy. This is a regression from
the 1:18.04.6 upload which switched changelogs.ubuntu.com from http to https.
[Test case]
Set acquire::http::proxy to a non-existing host, e.g.
http://invalid.invalid/, and check that the tool fails.
Do the same with acquire::https::proxy.
(Kind of a reverse check, since I don't have a proxy setup to test
against. If there's an actual proxy and otherwise, no internet, it can
be verified by setting the actual proxy and checking that it works
with it).
[Regression potential]
The fix changes the API of init_proxy() in UpdateManager/Core/utils.py to
make it return a dict with 'http' and 'https' members rather than just a
string. It seems the return value is only used by the test case, though, so
that should be fine.
Apart from that, it also allows https proxies now, since we're doing
https anyway, which means that a proxy setting ignored before now is
not. The same applies to the the new proxy variables used - they were
not used before, so things might fail that used to work - like you
specify an invalid https proxy but don't actually need one. Low risk,
though.
[Original bug report]
I have configured apt proxy in apt.conf.d and apt update and apt install can
work correctly. However, when I logged in system everyday, in the login
message, it says:
Failed to connect to https://changelogs.ubuntu.com/meta-release-lts.
Check your Internet connection or proxy settings
After further investigation, I found the the issue is caused in
package python3-update-manager:
python3-update-manager: /usr/lib/python3/dist-
packages/UpdateManager/Core/utils.py
In the init_proxy function of the python script, it only set a http
proxy by below code:
proxy_support = ProxyHandler({"http": proxy})
after changing the line to add https proxy, it can work:
proxy_support = ProxyHandler({"http": proxy, "https":proxy})
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1771914/+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 1744318] Re: changelogs.ubuntu.com should be using HTTPS
This bug was fixed in the package ubuntu-release-upgrader - 1:16.04.27 --- ubuntu-release-upgrader (1:16.04.27) xenial; urgency=medium * Use HTTPS for changelogs.ubuntu.com (LP: #1744318) * Run pre-build script to update mirror list, hold apt-btrfs-snapshot changes -- Julian Andres Klode Wed, 02 Oct 2019 16:08:25 +0200 ** Changed in: ubuntu-release-upgrader (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: update-manager (Ubuntu Xenial) 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/1744318 Title: changelogs.ubuntu.com should be using HTTPS Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Xenial: Fix Released Status in update-manager source package in Xenial: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Fix Released Status in update-manager source package in Bionic: Fix Released Bug description: [Impact] Although the packages listed in meta-release files on changelogs.ubuntu.com are signature-checked there doesn't appear to be any way to verify the meta-release files are valid so a man-in-the-middle could maliciously supply an alternate meta-release. meta-release files should be signed with the archive GPG key and/or delivered over HTTPS. [Test case] Block port 80 access to changelogs.ubuntu.com and check that do-release-upgrade still works [Regression potential] This breaks any clients behind a proxy where HTTPS (CONNECT on the proxy) is not allowed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744318/+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 1846069] Re: xenial/linux: 4.4.0-166.195 -proposed tracker
** Changed in: kernel-sru-workflow/automated-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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed - phase: Testing - phase-changed: Thursday, 03. October 2019 14:51 UTC + phase: Signoff + phase-changed: Thursday, 10. October 2019 21:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1846066 trusty/linux-lts-xenial: bug 1846067 xenial/linux-aws: bug 1846059 xenial/linux-fips: bug 1846065 xenial/linux-kvm: bug 1846060 xenial/linux-raspi2: bug 1846062 xenial/linux-snapdragon: bug 1846064 xenial/linux/caracalla-kernel: bug 1846054 xenial/linux/pc-kernel: bug 1846055 xenial/linux/stlouis-kernel: bug 1846057 variant: debs -- 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/1846069 Title: xenial/linux: 4.4.0-166.195 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Signoff phase-changed: Thursday, 10. October 2019 21:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1846066 trusty/linux-lts-xenial: bug 1846067 xenial/linux-aws: bug 1846059 xenial/linux-fips: bug 1846065 xenial/linux-kvm: bug 1846060 xenial/linux-raspi2: bug 1846062 xenial/linux-snapdragon: bug 1846064 xenial/linux/caracalla-kernel: bug 1846054 xenial/linux/pc-kernel: bug 1846055 xenial/linux/stlouis-kernel: bug 1846057 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846069/+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 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
This is an old bug in GRUB. This commit fixes it: http://git.savannah.gnu.org/cgit/grub.git/commit/?id=e20aa39ea4298011ba716087713cff26c6c52006 To test it, apply it to a GRUB source tree, compile it, install it, and then reinstall the bootloader with "sudo grub-install /dev/sda". ** Also affects: grub Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu) Status: New => Won't Fix ** Also affects: grub (Ubuntu) Importance: Undecided Status: New ** No longer affects: grub ** Also affects: grub (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux-gcp (Ubuntu) ** No longer affects: linux-gcp (Ubuntu Xenial) -- 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/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT Status in cloud-init: Won't Fix Status in grub package in Ubuntu: New Status in grub source package in Xenial: New Bug description: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. To test this out in a more slower fashion: 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 5) Issue rsize2fs /dev/sda1 again On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. I've tried starting from a Xenial instance and doing a do-release- upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+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 1838796] Re: TPM event log does not contain events measured after ExitBootServices
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux-azure (Ubuntu Bionic) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-azure (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) 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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-azure source package in Xenial: In Progress Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: In Progress Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe :
[Group.of.nepali.translators] [Bug 1846126] Re: xenial/linux-gcp: 4.15.0-1047.50 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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 kernel-stable-master-bug: 1846131 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 09. October 2019 14:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1846124 xenial/linux-gcp/gke-kernel: bug 1846125 variant: debs -- 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/1846126 Title: xenial/linux-gcp: 4.15.0-1047.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New 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: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed 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 kernel-stable-master-bug: 1846131 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Signoff phase-changed: Wednesday, 09. October 2019 14:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1846124 xenial/linux-gcp/gke-kernel: bug 1846125 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846126/+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 1637800] Re: add a motd script for news
This bug was fixed in the package base-files - 9.4ubuntu4.11 --- base-files (9.4ubuntu4.11) xenial; urgency=medium * update-motd.d/50-motd-news: add cloud_id to user-agent string (LP: #1840946) * d/postinst.in, d/postrm: add missing dh_systemd_enable pieces. This completes the fix for LP #1637800 * d/postinst.in: do not start the motd-news.service, as it won't be in an enabled state anyway, and the timer will run it when needed. This addresses the motd-news.service bit in comment #19 of #1637800. base-files (9.4ubuntu4.10) xenial; urgency=medium * Fix syntax error in new base-files postinst code. LP: #1836236. base-files (9.4ubuntu4.9) xenial; urgency=medium * Backport /etc/update-motd.d/50-motd-news, along with the systemd units that are used to keep the local cache file up-to-date. LP: #1637800 -- Andreas Hasenack Mon, 30 Sep 2019 10:31:01 -0300 ** Changed in: base-files (Ubuntu Xenial) 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/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+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 1840946] Re: Include cloud-id in user-agent string
This bug was fixed in the package base-files - 9.4ubuntu4.11 --- base-files (9.4ubuntu4.11) xenial; urgency=medium * update-motd.d/50-motd-news: add cloud_id to user-agent string (LP: #1840946) * d/postinst.in, d/postrm: add missing dh_systemd_enable pieces. This completes the fix for LP #1637800 * d/postinst.in: do not start the motd-news.service, as it won't be in an enabled state anyway, and the timer will run it when needed. This addresses the motd-news.service bit in comment #19 of #1637800. base-files (9.4ubuntu4.10) xenial; urgency=medium * Fix syntax error in new base-files postinst code. LP: #1836236. base-files (9.4ubuntu4.9) xenial; urgency=medium * Backport /etc/update-motd.d/50-motd-news, along with the systemd units that are used to keep the local cache file up-to-date. LP: #1637800 -- Andreas Hasenack Mon, 30 Sep 2019 10:31:01 -0300 ** Changed in: base-files (Ubuntu Xenial) 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/1840946 Title: Include cloud-id in user-agent string Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in base-files source package in Bionic: Fix Released Status in base-files source package in Disco: Fix Released Bug description: [Impact] We would like to include a cloud_id/$name parameter to the user-agent string that is sent to https://motd.ubuntu.com. This will allow the server part of motd.ubuntu.com to serve cloud-specific content if one is available. [Test Case] a) confirm that the motd message is still displayed: $ sudo sh /etc/update-motd.d/50-motd-news --force * Kata Containers are now fully integrated in Charmed Kubernetes 1.16! Yes, charms take the Krazy out of K8s Kata Kluster Konstruction. https://ubuntu.com/kubernetes/docs/release-notes b) confirm that cloud_id is set in the user-agent. This should be tested in lxd, gce, aws, and azure. Here is an example for lxd: $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl .*cloud_id/" + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- https://motd.ubuntu.com For each of the mentioned clouds, we expect cloud_id to be set to their short names: aws, gce, azure. For xenial, there is an extra test case: c) list the timers to confirm motd-news is active, and will run sometime in the next 12h following the installation of the updated package: $ systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2019-09-30 19:38:55 UTC 6h left n/a n/a motd-news.timer motd-news.service Mon 2019-09-30 22:45:13 UTC 9h left n/a n/a apt-daily.timer apt-daily.service Tue 2019-10-01 06:12:11 UTC 16h left n/a n/a apt-daily-upgrade.timer apt-daily-upgrade.service Tue 2019-10-01 13:11:41 UTC 23h left Mon 2019-09-30 13:11:41 UTC 14min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service [Regression Potential] This change adds a new parameter to the already existing user-agent string. This relies on the cloud-id tool from cloud-init. Even though it's considered trusted to some degree, it may be possible for some clouds to override their name in the data fed to cloud-init, which is what cloud-id parses. Therefore some precautions were taken when handling its contents: - set value to unknown if cloud-id fails, doesn't exist, or produce an empty value - sanitize the output of cloud-id, and truncate it to a maximum length - use a tempfile to store the intermediate output of cloud-id instead of a shell variable. One reason being avoiding storing a potentially large amount of data in a shell variable, and the other is to avoid mistakes when manipulating a shell variable that could contain shell metacharacters. [Other Info] For xenial, this is also finishing the fix for bug #1637800 which was stuck in the SRU queue due to it failing checks. Since the xenial package isn't using debhelper, manual dh snippets were added to the maintainer scripts, but they missed the dh_systemd_enable chunks. I'm also skipping starting motd-news.service, since the timer unit will handle that. This avoids an annoying error message about trying to start a unit that is not enabled. [Original Description] I'm preemptively filing this bug in case this isn't uploaded before the feature freeze. We would like to include a cloud_id/$name
[Group.of.nepali.translators] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
This bug was fixed in the package base-files - 9.4ubuntu4.11 --- base-files (9.4ubuntu4.11) xenial; urgency=medium * update-motd.d/50-motd-news: add cloud_id to user-agent string (LP: #1840946) * d/postinst.in, d/postrm: add missing dh_systemd_enable pieces. This completes the fix for LP #1637800 * d/postinst.in: do not start the motd-news.service, as it won't be in an enabled state anyway, and the timer will run it when needed. This addresses the motd-news.service bit in comment #19 of #1637800. base-files (9.4ubuntu4.10) xenial; urgency=medium * Fix syntax error in new base-files postinst code. LP: #1836236. base-files (9.4ubuntu4.9) xenial; urgency=medium * Backport /etc/update-motd.d/50-motd-news, along with the systemd units that are used to keep the local cache file up-to-date. LP: #1637800 -- Andreas Hasenack Mon, 30 Sep 2019 10:31:01 -0300 ** Changed in: base-files (Ubuntu Xenial) 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/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Invalid Status in base-files source package in Xenial: Fix Released Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+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 1840946] Re: Include cloud-id in user-agent string
This bug was fixed in the package base-files - 10.1ubuntu9.2 --- base-files (10.1ubuntu9.2) disco; urgency=medium * update-motd.d/50-motd-news: add cloud_id to user-agent string (LP: #1840946) -- Andreas Hasenack Fri, 27 Sep 2019 15:23:40 -0300 ** Changed in: base-files (Ubuntu Disco) 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/1840946 Title: Include cloud-id in user-agent string Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in base-files source package in Disco: Fix Released Bug description: [Impact] We would like to include a cloud_id/$name parameter to the user-agent string that is sent to https://motd.ubuntu.com. This will allow the server part of motd.ubuntu.com to serve cloud-specific content if one is available. [Test Case] a) confirm that the motd message is still displayed: $ sudo sh /etc/update-motd.d/50-motd-news --force * Kata Containers are now fully integrated in Charmed Kubernetes 1.16! Yes, charms take the Krazy out of K8s Kata Kluster Konstruction. https://ubuntu.com/kubernetes/docs/release-notes b) confirm that cloud_id is set in the user-agent. This should be tested in lxd, gce, aws, and azure. Here is an example for lxd: $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl .*cloud_id/" + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- https://motd.ubuntu.com For each of the mentioned clouds, we expect cloud_id to be set to their short names: aws, gce, azure. For xenial, there is an extra test case: c) list the timers to confirm motd-news is active, and will run sometime in the next 12h following the installation of the updated package: $ systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2019-09-30 19:38:55 UTC 6h left n/a n/a motd-news.timer motd-news.service Mon 2019-09-30 22:45:13 UTC 9h left n/a n/a apt-daily.timer apt-daily.service Tue 2019-10-01 06:12:11 UTC 16h left n/a n/a apt-daily-upgrade.timer apt-daily-upgrade.service Tue 2019-10-01 13:11:41 UTC 23h left Mon 2019-09-30 13:11:41 UTC 14min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service [Regression Potential] This change adds a new parameter to the already existing user-agent string. This relies on the cloud-id tool from cloud-init. Even though it's considered trusted to some degree, it may be possible for some clouds to override their name in the data fed to cloud-init, which is what cloud-id parses. Therefore some precautions were taken when handling its contents: - set value to unknown if cloud-id fails, doesn't exist, or produce an empty value - sanitize the output of cloud-id, and truncate it to a maximum length - use a tempfile to store the intermediate output of cloud-id instead of a shell variable. One reason being avoiding storing a potentially large amount of data in a shell variable, and the other is to avoid mistakes when manipulating a shell variable that could contain shell metacharacters. [Other Info] For xenial, this is also finishing the fix for bug #1637800 which was stuck in the SRU queue due to it failing checks. Since the xenial package isn't using debhelper, manual dh snippets were added to the maintainer scripts, but they missed the dh_systemd_enable chunks. I'm also skipping starting motd-news.service, since the timer unit will handle that. This avoids an annoying error message about trying to start a unit that is not enabled. [Original Description] I'm preemptively filing this bug in case this isn't uploaded before the feature freeze. We would like to include a cloud_id/$name parameter to the user-agent string that is sent to https://motd.ubuntu.com. This will allow the server part of motd.ubuntu.com to serve cloud-specific content if one is available. There is an MP for this already at https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git /base-files/+merge/371370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe :
[Group.of.nepali.translators] [Bug 1840946] Re: Include cloud-id in user-agent string
This bug was fixed in the package base-files - 10.1ubuntu2.7 --- base-files (10.1ubuntu2.7) bionic; urgency=medium * update-motd.d/50-motd-news: add cloud_id to user-agent string (LP: #1840946) -- Andreas Hasenack Fri, 27 Sep 2019 15:24:34 -0300 ** Changed in: base-files (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/1840946 Title: Include cloud-id in user-agent string Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in base-files source package in Disco: Fix Released Bug description: [Impact] We would like to include a cloud_id/$name parameter to the user-agent string that is sent to https://motd.ubuntu.com. This will allow the server part of motd.ubuntu.com to serve cloud-specific content if one is available. [Test Case] a) confirm that the motd message is still displayed: $ sudo sh /etc/update-motd.d/50-motd-news --force * Kata Containers are now fully integrated in Charmed Kubernetes 1.16! Yes, charms take the Krazy out of K8s Kata Kluster Konstruction. https://ubuntu.com/kubernetes/docs/release-notes b) confirm that cloud_id is set in the user-agent. This should be tested in lxd, gce, aws, and azure. Here is an example for lxd: $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl .*cloud_id/" + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- https://motd.ubuntu.com For each of the mentioned clouds, we expect cloud_id to be set to their short names: aws, gce, azure. For xenial, there is an extra test case: c) list the timers to confirm motd-news is active, and will run sometime in the next 12h following the installation of the updated package: $ systemctl list-timers NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2019-09-30 19:38:55 UTC 6h left n/a n/a motd-news.timer motd-news.service Mon 2019-09-30 22:45:13 UTC 9h left n/a n/a apt-daily.timer apt-daily.service Tue 2019-10-01 06:12:11 UTC 16h left n/a n/a apt-daily-upgrade.timer apt-daily-upgrade.service Tue 2019-10-01 13:11:41 UTC 23h left Mon 2019-09-30 13:11:41 UTC 14min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service [Regression Potential] This change adds a new parameter to the already existing user-agent string. This relies on the cloud-id tool from cloud-init. Even though it's considered trusted to some degree, it may be possible for some clouds to override their name in the data fed to cloud-init, which is what cloud-id parses. Therefore some precautions were taken when handling its contents: - set value to unknown if cloud-id fails, doesn't exist, or produce an empty value - sanitize the output of cloud-id, and truncate it to a maximum length - use a tempfile to store the intermediate output of cloud-id instead of a shell variable. One reason being avoiding storing a potentially large amount of data in a shell variable, and the other is to avoid mistakes when manipulating a shell variable that could contain shell metacharacters. [Other Info] For xenial, this is also finishing the fix for bug #1637800 which was stuck in the SRU queue due to it failing checks. Since the xenial package isn't using debhelper, manual dh snippets were added to the maintainer scripts, but they missed the dh_systemd_enable chunks. I'm also skipping starting motd-news.service, since the timer unit will handle that. This avoids an annoying error message about trying to start a unit that is not enabled. [Original Description] I'm preemptively filing this bug in case this isn't uploaded before the feature freeze. We would like to include a cloud_id/$name parameter to the user-agent string that is sent to https://motd.ubuntu.com. This will allow the server part of motd.ubuntu.com to serve cloud-specific content if one is available. There is an MP for this already at https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git /base-files/+merge/371370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe :
[Group.of.nepali.translators] [Bug 1847300] Re: [backport] magic-proxy: dump proxy log to stdout on failure
This bug was fixed in the package livecd-rootfs - 2.578.9 --- livecd-rootfs (2.578.9) disco; urgency=medium * magic-proxy: dump proxy log to stdout on failure (LP: #1847300) -- Robert C Jennings Tue, 08 Oct 2019 10:57:31 -0500 ** Changed in: livecd-rootfs (Ubuntu Disco) 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/1847300 Title: [backport] magic-proxy: dump proxy log to stdout on failure Status in livecd-rootfs package in Ubuntu: New Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Disco: Fix Released Bug description: [Impact] When we encounter a failure in 'lb binary' the launchpad builders can only surface the build output from stdout. If the binary hook failure implicates the archive we can not determine fault without the apt proxy log. Backporting the patch from eoan will dump the proxy log to stdout to aid in debugging these failures. [Test case] Run a build with a $REPO_SNAPSHOT_STAMP and a binary hook with 'exit 1'. The apt proxy log should end up on stdout. [Regression Potential] Nearly none. This dumps a file to stdout in the failure exit path; a failure at this stage does not change the outcome of the build. [Other Info] We are seeing issues today in builds that need this debug output in place, we would like to move this SRU through quickly. The code has been running in eoan for at least a week without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1847300/+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 1847300] Re: [backport] magic-proxy: dump proxy log to stdout on failure
This bug was fixed in the package livecd-rootfs - 2.525.31 --- livecd-rootfs (2.525.31) bionic; urgency=medium * magic-proxy: dump proxy log to stdout on failure (LP: #1847300) -- Robert C Jennings Tue, 08 Oct 2019 11:00:07 -0500 ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) 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/1847300 Title: [backport] magic-proxy: dump proxy log to stdout on failure Status in livecd-rootfs package in Ubuntu: New Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Disco: Fix Released Bug description: [Impact] When we encounter a failure in 'lb binary' the launchpad builders can only surface the build output from stdout. If the binary hook failure implicates the archive we can not determine fault without the apt proxy log. Backporting the patch from eoan will dump the proxy log to stdout to aid in debugging these failures. [Test case] Run a build with a $REPO_SNAPSHOT_STAMP and a binary hook with 'exit 1'. The apt proxy log should end up on stdout. [Regression Potential] Nearly none. This dumps a file to stdout in the failure exit path; a failure at this stage does not change the outcome of the build. [Other Info] We are seeing issues today in builds that need this debug output in place, we would like to move this SRU through quickly. The code has been running in eoan for at least a week without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1847300/+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 1846065] Re: xenial/linux-fips: 4.4.0-1023.28 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Invalid -- 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/1846065 Title: xenial/linux-fips: 4.4.0-1023.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: Fix Released 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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 kernel-stable-master-bug: 1846069 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Testing phase-changed: Friday, 04. October 2019 14:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846065/+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
