[Group.of.nepali.translators] [Bug 1877176] [NEW] 64-char hostname causes dhcp server to reject lease
Public bug reported: [impact] a systemd with a 64-character hostname (the maximum hostname length for Linux) will cause a dhcp server to reject its dhcp lease due to passing the invalid hostname in the dhcp lease request. [test case] $ cat /etc/systemd/network/10-ens3.network [Match] Name=ens3 [Network] DHCP=yes set hostname to 64-char name, e.g.: $ sudo hostnamectl set-hostname a123456789b123456789c123456789d123456789e123456789f123456789g123 restart networkd: $ sudo systemctl restart systemd-networkd check logs: root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error' May 06 19:01:30 a123456789b123456789c123456789d123456789e123456789f123456789g123 systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument [scope] this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which is included in Bionic and later. This is needed only for Xenial. [other info] this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to continue networkd dhcp even if the hostname is invalid, however the older code in Xenial doesn't correctly detect the invalid hostname, so this additional patch is needed. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Xenial) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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/1877176 Title: 64-char hostname causes dhcp server to reject lease Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: [impact] a systemd with a 64-character hostname (the maximum hostname length for Linux) will cause a dhcp server to reject its dhcp lease due to passing the invalid hostname in the dhcp lease request. [test case] $ cat /etc/systemd/network/10-ens3.network [Match] Name=ens3 [Network] DHCP=yes set hostname to 64-char name, e.g.: $ sudo hostnamectl set-hostname a123456789b123456789c123456789d123456789e123456789f123456789g123 restart networkd: $ sudo systemctl restart systemd-networkd check logs: root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error' May 06 19:01:30 a123456789b123456789c123456789d123456789e123456789f123456789g123 systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument [scope] this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which is included in Bionic and later. This is needed only for Xenial. [other info] this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to continue networkd dhcp even if the hostname is invalid, however the older code in Xenial doesn't correctly detect the invalid hostname, so this additional patch is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877176/+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 1867673] Re: [SRU] awscli not kept up to date
Sponsored for focal, eoan, bionic and xenial. Note to SRU team: as mentioned in the bug description, this upload requires a new python-botocore. Those have been uploaded to the Unapproved queues as well and need to be accepted before considering these uploads here. ** Also affects: awscli (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: awscli (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: awscli (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: awscli (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: awscli (Ubuntu) Status: New => 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/1867673 Title: [SRU] awscli not kept up to date Status in awscli package in Ubuntu: Fix Released Status in awscli source package in Xenial: New Status in awscli source package in Bionic: New Status in awscli source package in Eoan: New Status in awscli source package in Focal: New Bug description: [Original Bug Description] awscli is not kept up to date, and so new AWS features are not available. The AWS pip installation method is unaudited and unsigned, and is not a production ready solution to the out-of-date problem. The awscli package needs to be kept up to date and available on all supported Ubuntu OSes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: awscli (not installed) ProcVersionSignature: Ubuntu 4.4.0-1100.111-aws 4.4.203 Uname: Linux 4.4.0-1100-aws x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Mar 16 19:36:32 2020 Ec2AMI: ami-a8d2d7ce Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1a Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: awscli UpgradeStatus: No upgrade log present (probably fresh install) [[ SRU Request Template ]] [Impact] * the awscli package is out of date to varying degrees across supported Ubuntu releases * old versions of awscli lack critical functionality for modern AWS cloud features. For example, several `aws eks` commands are unavailable and/or unsupported prior to version 1.18.17 [1]. * An updated awscli package will allow Xenial and Bionic, in particular, to access modern AWS functionality from the archive. [Test Case] * on any ubuntu release without groovy-proposed enabled: `apt-get install awscli` and attempt `aws eks update-kubeconfig`. * This is functionality described in the AWS EKS getting started guide [1] as requiring version 1.18.17 or later [1], and is part of the documented web-console path to using Ubuntu (or any distro) on EKS. * On the version of awscli in bionic (1.14.44), the `eks` subcommand is not available. * On eoan or focal, this command may not correctly update the user's kubeconfig file depending on the configuration of their AWS EKS cluster (k8s version, cluster options, etc). * The latest version of this package is part of acceptance criteria of AWS cloud images for Ubuntu CPC and cloud partners. [Regression Potential] * users of ubuntu and awscli who have scripting or automation reliant on outdated versions of awscli are likely to see some form of breakage insofar as AWS has been willing to break functionality of older versions. * The latest version of awscli (1.18.47) lists botocore 1.15.47 as a dependency; at the time of this description the version of python- botocore in the archive does not meet this requirement [2] -- package builds or installation could fail if this dependency is not correctly resolved. * Any Ubuntu image builds which preinstall this package and/or use it in boot scripts may break depending on their expectations. [Other Info] * The Hardware Enablement exception likely applies here, as updating this package version will enable using functionality of the AWS cloud which are impossible to use with the versions of the cli currently in the archive. [1] https://docs.aws.amazon.com/eks/latest/userguide/getting-started-console.html [2] https://bugs.launchpad.net/ubuntu/+source/python-botocore/+bug/1875485 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awscli/+bug/1867673/+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 1874795] Re: xenial/linux-cascade: 4.4.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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 -- kernel-stable-master-bug: 1874804 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade - phase: Ready for Packaging - phase-changed: Saturday, 25. April 2020 00:54 UTC + phase: Packaging + phase-changed: Wednesday, 06. May 2020 08:21 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- tag not published and package not + uploaded + prepare-package-meta: Pending -- tag not published and package not + uploaded + prepare-package-signed: Pending -- tag not published and package not + uploaded trackers: xenial/linux-cascade/cascade-kernel: bug 1874794 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/1874795 Title: xenial/linux-cascade: 4.4.0-1018.20 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 -- kernel-stable-master-bug: 1874804 packages: main: linux-cascade meta: linux-meta-cascade signed: linux-signed-cascade phase: Packaging phase-changed: Wednesday, 06. May 2020 08:21 UTC reason: prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded prepare-package-signed: Pending -- tag not published and package not uploaded trackers: xenial/linux-cascade/cascade-kernel: bug 1874794 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874795/+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
