[Bug 1970422] Re: awk warnings running prometheus-node-exporter-apt.service
** Description changed: + [Impact] + This bug has minimal impact to users. Warnings are being thrown by the service in its journal; but that seems to be the only issue -- valid results are still being returned by the prometheus collector in the number of packages that need updates for each repository; along with node_reboot_required. + + The bug fix is to clean up the regex to avoid the warnings. + + [Test Plan] + 1) Run /usr/share/prometheus-node-exporter-collectors/apt.sh + 2) Validate that it returns without awk warnings. + + [Where problems could occur] + - An invalid regex might cause repository stats to be returned in the wrong format for parsing by prometheus. + - Invalid regex would still show warnings or errors in awk. + + --- + Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-06 (140 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Package: prometheus-node-exporter 0.18.1+ds-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Tags: focal Uname: Linux 5.4.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.cron.daily.apport: [deleted] ** Description changed: [Impact] This bug has minimal impact to users. Warnings are being thrown by the service in its journal; but that seems to be the only issue -- valid results are still being returned by the prometheus collector in the number of packages that need updates for each repository; along with node_reboot_required. The bug fix is to clean up the regex to avoid the warnings. + This is not applicable elsewhere than in focal; later releases have + stopped installing the service and associated script. + [Test Plan] 1) Run /usr/share/prometheus-node-exporter-collectors/apt.sh 2) Validate that it returns without awk warnings. - [Where problems could occur] + [Where problems could occur] - An invalid regex might cause repository stats to be returned in the wrong format for parsing by prometheus. - Invalid regex would still show warnings or errors in awk. --- Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-06 (140 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Package: prometheus-node-exporter 0.18.1+ds-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Tags: focal Uname: Linux 5.4.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.cron.daily.apport: [deleted] ** Changed in: prometheus-node-exporter (Ubuntu) Status: New => Fix Released ** Also affects: prometheus-node-exporter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: prometheus-node-exporter (Ubuntu Focal) Status: New => Triaged ** Changed in: prometheus-node-exporter (Ubuntu Focal) Importance: Undecided => Low ** Changed in: prometheus-node-exporter (Ubuntu Focal) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions
[Bug 1970422] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583973/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583972/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] HookError_ubuntu.txt
apport information ** Attachment added: "HookError_ubuntu.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583971/+files/HookError_ubuntu.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583970/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] [NEW] awk warnings running prometheus-node-exporter-apt.service
Public bug reported: Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-06 (140 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Package: prometheus-node-exporter 0.18.1+ds-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Tags: focal Uname: Linux 5.4.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: prometheus-node-exporter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-12-06 (140 days ago) + InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) + Package: prometheus-node-exporter 0.18.1+ds-2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 + Tags: focal + Uname: Linux 5.4.0-96-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Description changed: + [Impact] + Any user attempting to tab-complete from "umount /dev/" when running the bash shell. + + [Test cases] Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined - $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined + + + [Regression potential] + Since it is limited to a single file (/usr/share/bash-completion/completions/umount) and affects only it, as well as given that it currently does not work, I estimate this as a low risk change. Things to look out for as a regression would be if another previously-working completion would fail to work (ie. what if mount stops completing correctly, and works again if the fix is backed out?). + + --- + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: - + InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: bash-completion (Ubuntu Focal) Status: Incomplete => Invalid ** Also affects: util-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gawk (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: mawk (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: bash-completion (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: bash-completion (Ubuntu Eoan) Status: New => Invalid ** No longer affects: gawk (Ubuntu) ** No longer affects: mawk (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786699] Re: grub-install command line options incompatible with Debian
I have an issue with leaving cruft around instead of actively fixing whatever depends on old behavior; months from now, or even years, we'll still have this switch around that does nothing -- that's more confusing for users than actively moving forward. That said, I'll defer to Colin and add the no-op. Are you saying that you otherwise have no issues with the idea of this patch and would consider including it in the Debian package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786699 Title: grub-install command line options incompatible with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852772] Re: test_updates_interval fails on focal
** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852772 Title: test_updates_interval fails on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid
tcmu is a high-impact target that will handle storage requests and potentially allow an attacker to intercept data. I'm concerned by the fact the Debian maintainer felt they had to disable -Werror to make things work on 32-bit; even if that's not necessarily out main focus: it points to potential issues in the code, code that is not necessarily very portable or that might be hard to maintain in the future. I'll let the Security Team give their opinion on it and decide. ** Changed in: tcmu (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) ** Changed in: tcmu (Ubuntu) Status: In Progress => New ** Changed in: python-rtslib-fb (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854362 Title: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid
urwid should have security review. Packaging for it looks fine, but it does handle input, present UI that is used in core places for the OS (such as in the installer, even though that's a snap...) ** Changed in: urwid (Ubuntu) Status: In Progress => New ** Changed in: urwid (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) ** Changed in: tcmu (Ubuntu) Status: New => In Progress ** Changed in: tcmu (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854362 Title: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
That's not /really/ helpful anyway. You'd have installed an extra application, for a wholly unrelated issue, and still have to set the profile to A2DP yourself. Alistair, there are messages in your logs that seem to point to a firmware issue: Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Furthermore, I see some slightly unusual messages that point to an issue with the firmware (usually) as well: Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 It's possible the hardware gets confused by losing the connection that was initially there. I realize this might not be /so/ helpful, but have you also tried with another model of bluetooth headphones, assuming you have something available? Please see if you can attach the full contents of /var/log/syslog after reproducing the issue (with a different model or with the usual Sonys); once you've made sure that it doesn't contain sensitive data. I'd need to know when you started each attempt so we can see exactly how the system reacts to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852772] Re: test_updates_interval fails on focal
I see no objection at all; that fix looks obviously correct and does fix the test. ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Corey Bryant (corey.bryant) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852772 Title: test_updates_interval fails on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid
** Changed in: urwid (Ubuntu) Status: New => In Progress ** Changed in: urwid (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854362 Title: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851064] Re: [SRU] Update WALinuxAgent to 2.2.44
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851064 Title: [SRU] Update WALinuxAgent to 2.2.44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1851064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
There are multiple reports of chainload working again with the fix uploaded to eoan-proposed; marking as verification-done for Eoan with 2.04-1ubuntu12.1 ** Tags removed: id-5d978799ba24715c5ddcabc5 verification-needed verification-needed-eoan ** Tags added: id-5d978799ba24715c5ddcabc verification-done-eoan ** Tags removed: id-5d978799ba24715c5ddcabc ** Tags added: id-5d978799ba24715c5ddcabc5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838323] Re: Support Japanese new era "令和 (Reiwa)"
** Description changed: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] Unicode data include REIWA like it includes HEISEI. Reverse-build- depends need a rebuild to include the new data, followed by the following tests to make sure the data is taken into account. + 1) Rebuild reverse-depends of unicode-data; check that they build fine + (ie. no regressions due to unicode-data changes): + + Reverse-Build-Depends + = + * console-data + * courier-unicode + * cyrus-imapd + * fntsample + * fonttools + * gucharmap + * ibus + * julia + * libxmlada + * node-unicode-data + * node-unicode-property-aliases + * node-unicode-property-aliases-ecmascript + * node-unicode-property-value-aliases + * node-unicode-property-value-aliases-ecmascript + * node-unicode-tr51 + * re2 + * safeclib + * slang2 + * utf8proc + * wcwidth + * wine + * wine-development + + + 2) Using gucharmap, verify that the SQUARE ERA NAME REIWA glyph point exists (there may not be a glyph associated as that is font-dependent. + == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - - SQUARE ERA NAME HEISEI: ㍻ - - SQUARE ERA NAME REIWA: 令和 (in a single glyph) + - SQUARE ERA NAME HEISEI: ㍻ + - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. Use fonts-noto-cjk to display the glyph. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838323 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unicode-data/+bug/1838323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847458] Re: EFI chainloader no longer uses shim lock protocol
** Changed in: grub2 (Ubuntu) Status: Incomplete => Invalid ** Changed in: grub2 (Ubuntu Eoan) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847458 Title: EFI chainloader no longer uses shim lock protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
Are the systems getting this set up for dual-booting at all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847458] Re: EFI chainloader no longer uses shim lock protocol
The code does look like it will chainload via shim: linuxefi_secure_validate() runs, checks that the image is valid against firmware stores and the MokList. Then grub_cmd_chainloader -> (grub_linuxefi_secure_validate() find the image valid) -> grub_secureboot_chainloader_boot() -> handle_image() [ read image header, identify relocations, find entry point, etc.] -> efi_call_2 (entry point) -> Image is started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847458 Title: EFI chainloader no longer uses shim lock protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848892] Re: "error: Unknown TPM error." after upgrading to grub 2.04
Removed block-proposed tag after doing one last smoketest to make sure grub was booting fine. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848892 Title: "error: Unknown TPM error." after upgrading to grub 2.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848892] Re: "error: Unknown TPM error." after upgrading to grub 2.04
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848892 Title: "error: Unknown TPM error." after upgrading to grub 2.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840941] Re: kdump fails to start with secure boot enabled
Should be done very soon; we're waiting for the shim review board to review, then it can be submitted to Microsoft for signing. Expect about a week turnaround time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840941 Title: kdump fails to start with secure boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1840941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848892] Re: "error: Unknown TPM error." after upgrading to grub 2.04
** Description changed: + [Impact] + Some specific system (listed in upstream thread at https://lists.gnu.org/archive/html/grub-devel/2019-10/msg00104.html) + + Mostly ASUS systems, but also reported on some Dell systems. + + The affected systems are used to boot in UEFI mode and will fail to + write measurements to the possible onboard TPM, causing failure to boot. + + + [Test case] + 1) Boot affected system to Ubuntu + 2) Verify that the system boots successfully to Ubuntu, without "unknown TPM error" messages. + + [Regression potential] + Low risk of regression, as this changes the current behavior only to avoid failing to boot when such errors are encountered, instead switching the behavior to writing debug messages (if debugging is enabled only) in such cases. Further work may be needed later to correct or mitigate these errors if TPM measurements are needed to work on the affected systems, as such measurements would otherwise be incomplete. + + --- + After upgrading to eoan today (via `do-release-upgrade -d`), my laptop failed to boot into the OS. I got the grub 2.04 screen (showing only Ubuntu), but selecting that gave me about 20 lines of "error: Unknown TPM error.", followed by "error: you need to load the kernel first" and no way to proceed/recover. Advanced options didn't work either. Dropping into the grub console and writing a simple command like `set root=(hd1,gpt5)` failed again with a TPM error. It goes without saying that booting had worked before with disco/grub 2.02. As a workaround, I eventually managed to boot using an eoan live CD, chroot'ed into my system, added the `disco main` repo, and forcefully downgraded to disco's 2.02. After reinstalling grub to the efi partition, booting finally worked again (with grub 2.02). lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy grub-efi grub-efi: - Installed: 2.02+dfsg1-12ubuntu2 - Candidate: 2.04-1ubuntu12 - Version table: - 2.04-1ubuntu12 500 - 500 http://ubuntu.inode.at/ubuntu eoan/main amd64 Packages - *** 2.02+dfsg1-12ubuntu2 500 - 500 http://ubuntu.inode.at/ubuntu disco/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.02+dfsg1-12ubuntu2 + Candidate: 2.04-1ubuntu12 + Version table: + 2.04-1ubuntu12 500 + 500 http://ubuntu.inode.at/ubuntu eoan/main amd64 Packages + *** 2.02+dfsg1-12ubuntu2 500 + 500 http://ubuntu.inode.at/ubuntu disco/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub-efi 2.02+dfsg1-12ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 19 23:20:07 2019 InstallationDate: Installed on 2017-03-05 (958 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: grub2 UpgradeStatus: Upgraded to eoan on 2019-10-19 (0 days ago) ** Changed in: grub2 (Ubuntu Eoan) Status: New => Triaged ** Changed in: grub2 (Ubuntu Eoan) Importance: Undecided => High ** Changed in: grub2 (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848892 Title: "error: Unknown TPM error." after upgrading to grub 2.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
** Description changed: + [Impact] + Dual-boot users who have somehow had shim uninstalled from their system / Secure Boot disabled. + + [Test case] + (system with dual-boot setup for Ubuntu and Windows) + 1) uninstall shim/shim-signed from the system + 2) Run 'sudo grub-install -v'; ensure grubx64.efi is installed as the ubuntu bootentry (check 'sudo efibootmgr -v') + 3) Reboot. + 4) In system firmware, ensure Secure Boot is disabled. + 5) Attempt to start Windows from the Grub menu. + + Verify that Windows is chainloaded from Grub successfully; without + returning to the GRUB menu or restarting the whole system. + + [Regression potential] + Minimal; this is returning the state of the code paths for linuxefi validation back to how they were in GRUB 2.02; the extra check for the Secure Boot state is unnecessary at that point since it will be run again later when validating the images. This affects all validation code paths on UEFI but the net effect of reverting that change should be nil due to the duplication of code that already exists. + + --- + On a dual boot computer with Windows 10 Pro and Ubuntu 19.10, since a month, Grub was unable to boot Windows 10. Hitting the Windows entry line give me a 0.1s black screen and get me back to Grub Menu. sudo update-grub give me : Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.3.0-10-generic Found initrd image: /boot/initrd.img-5.3.0-10-generic Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub-efi-amd64 2.04-1ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 08:01:05 2019 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: grub2 UpgradeStatus: Upgraded to eoan on 2018-11-14 (314 days ago) ** Changed in: grub2 (Ubuntu) Status: Incomplete => In Progress ** Changed in: grub2 (Ubuntu Eoan) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
It has nothing to do with whether the file handle is closed or not; this is just confusing code because of how it's built. Shim is supposed to be installed by the installer when you set up the system in UEFI mode; this is done for you by the installer, and isn't a dependency of grub because grub does not require shim to work; but things *will* work better with shim installed. So, I strongly recommend anyone running into such issues make sure it is installed on their system, as it is supposed to be. Now, after tracing more of the code, it looks like the issue is that grub_load_and_start_image() is insufficient to complete the boot process in handle_image()... You get the image loaded, but StartImage is never called, which would explain why you're seeing things go back to the menu. Now, I don't think it's worth digging more into this code path, since if SB is disabled then shim_verify should be letting images work, unvalidated but accepted; so it would otherwise not get run. I'll go ahead and drop the extra check for SB state in linuxefi_secure_validate(). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848892] Re: "error: Unknown TPM error." after upgrading to grub 2.04
I've already submitted a possible fix upstream for this issue (well, at least something that will stop this breaking, and give us more information to debug and fix it more permanently): https://lists.gnu.org/archive/html/grub-devel/2019-10/msg00103.html There isn't concensus there just yet, but I will prepare the SRU for this today, and I think this is a good candidate for releasing quicker than the usual 7 day waiting period in the -proposed repository. This means I'll still need help from people to give us debug information once the patched version of GRUB is available so we can better understand what was going wrong exactly. In the meantime, the best solution is to: - Get to the GRUB menu - Highlight the boot entry you wanted to run and hit E (for edit) - At the top of the entry, add "rmmod tpm" - Hit Ctrl-X or F10 to run the edited entry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848892 Title: "error: Unknown TPM error." after upgrading to grub 2.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
No; this patch is wrong. For starters, you really ought to have shim installed, and that is the primary cause for such failures -- somehow your install is incomplete, and shim was removed either because the package was removed, or through the use of boot-repair (IIRC it replaces shim with using grub directly, which is not supported). Then, the code for the chainloader already is supposed to handle Secure Boot being off -- if it's disabled, the linuxefi_secure_validate() function sees that and returns 1 (image is deemed valid, since SB is disabled). Then we run grub_secureboot_chainloader_boot(), which will execute handle_image(), which should immediately check read_header() and find out, again, whether Secure Boot is enabled and/or if shim is available; returning with whatever status was retrieved reading the header for the binary that is to be chainloaded. I'd expect that if Secure Boot is not enabled, you would again have a return code of 0 there, and move on to using the normal chainload behavior of load_image and start_image. Please, if you're running into this issue, try stopping at the grub menu, and edit the chainload entry to add: set debug="chain" At the top, taking a screenshot or video of the boot process that you can then attach here. We really need to know if this is caused by one unusually built binary, or what precisely is going on before making any patches to GRUB. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850699] [NEW] Please remove net-tools from bind9 Depends (replaced by iproute2)
Public bug reported:
net-tools has been replaced by iproute2; so uses of ifconfig should be
replaced with ip ('ip link' or 'ip address').
Similarly, netstat is replaced by ss, and route is replaced by ip ('ip
route').
bind9 has already updated the uses of ifconfig (in ifconfig.sh) to be
able to detect that 'ip' is available and use that instead.
Let's finish this transition and stop depending on 'net-tools' and
pulling that in main via bind9.
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850699
Title:
Please remove net-tools from bind9 Depends (replaced by iproute2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1850699/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850538] [NEW] Please remove ubuntu-core-meta from the archive
Public bug reported: Hi, As far as I can tell, the ubuntu-core-meta metapackage and the binary packages it builds: - ubuntu-core-libs - ubuntu-core-libs-dev Are no longer in use by snapcraft, the core snap or any other consumers; and is out of date with that is considered the accepted list of packages that defines a developer system or the core dependencies for building snaps. Please remove it from the Ubuntu archive. ** Affects: ubuntu-core-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850538 Title: Please remove ubuntu-core-meta from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-core-meta/+bug/1850538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
This does not appear to be a new issue; but it is newly visible due to the changes in 2.04: we've now upgraded to a new major release of GRUB, and the modules are now no longer compatible with previous releases. In other words, if you're running into this issue, your system was most likely already broken, possibly for a long while, even if it was not immediately obvious -- somehow the files on disk under /boot are no longer in sync with the copy of the bootloader installed to the MBR, or in the ESP if you're in UEFI mode. Even though I am not sure what the actual cause of this, one possible explanation of this is modification of the system at some point in the past. For example, if /boot isn't mounted, listed in /etc/fstab; or /boot/efi in the case of UEFI. It is possible this is a side-effect of use of boot-repair tools. It's hard to know, but for now the precise cause is unknown and we will do more testing to figure out how this can happen. In any case, right now the best thing to do to repair is to boot from a Live image (USB or CD-ROM), and follow the steps in https://help.ubuntu.com/community/Grub2/Installing#via_ChRoot to repair GRUB by hand, or reinstall. There is additional information about this in the Debian bug report as well, here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931896 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671951] Re: networkd should allow configuring IPV6 MTU
Thanks. Let's put both tasks as Triaged again then, since it's obviously not fixed in disco and bionic. I don't think this qualifies as a regression though, since the feature was never available before. It's just not finished since the systemd side of this isn't complete. ** Changed in: systemd (Ubuntu Bionic) Status: Fix Released => Triaged ** Changed in: systemd (Ubuntu Disco) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849863] Re: shim-signed does not boot on Lenovo Yoga C630 WOS with enabled Secure Boot
What if you set SHIM_VERBOSE in firmware, using 'sudo mokutil --set- verbosity true' after booting with just grub? There should be debug messages showing up on screen to tell what is going on in shim in this case, and having those will help in debugging the issue. ** Changed in: shim (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849863 Title: shim-signed does not boot on Lenovo Yoga C630 WOS with enabled Secure Boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1849863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848880] Re: Server 18.04.3 OEM Install option doesn't work
The fact that there is no oem-config-prepare / OEM mode on the live- server image is a known thing; I don't think that has been implemented at all in subiquity yet. However, you really should have has oem-config-prepare available at the end of an OEM install from the server image; I'll investigate why that wasn't the case, first by trying to reproduce the issue. ** Changed in: debian-installer (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848880 Title: Server 18.04.3 OEM Install option doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1848880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849560] Re: Please revise the files installed in /etc/
** Tags added: writable-etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849560 Title: Please revise the files installed in /etc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1849560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849560] [NEW] Please revise the files installed in /etc/
Public bug reported: openssh-server and openssh-client install various files under /etc: /etc/ssh/* /etc/systemd/system/sshd.service Please see if these files can be moved elsewhere, in accordance with FHS: /etc should only contain files writable by the system administrator, and in Ubuntu Core 20 we should aim to have no writable files in /etc (as it will be included in images, avoid conflict resolution on upgrades). At a glance, it looks like /etc/systemd/system/sshd.service could be moved to /lib/systemd/system, and many of the files in /etc/ssh do have suitable locations elsewhere on the system, such as /var/lib/ for generated keys, /usr/share/ for default SSH configurations, etc.) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849560 Title: Please revise the files installed in /etc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1849560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849554] Re: Please move cache files to a different location
** Tags added: writable-etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849554 Title: Please move cache files to a different location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1849554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849559] [NEW] /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location
Public bug reported: The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong location. It is a system-wide default config for dbus, and as such probably should be in /usr/share/dbus-1/system.d instead; like most other DBus definitions installed on a typical system. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: writable-etc ** Tags added: writable-etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849559 Title: /etc/dbus-1/system.d/wpa_supplicant.conf is in wrong location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1849559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849557] [NEW] Please revise files in /etc/cloud tree
Public bug reported: On a typical install of an Ubuntu system, and in particular on a Ubuntu Core system, there are various files under /etc/cloud. Most of these files (especially on UC) appear to be default files that are unmodified, and are furthermore bind-mounted such that they may be writable (Ubuntu Core-specific). Please revise the files in /etc/cloud. If the files are defaults that are otherwise used unmodified on systems, they probably should live in a tree under /usr/share, which is the commonly used location for system defaults and other architecture-independent files. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: writable-etc ** Tags added: writable-etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849557 Title: Please revise files in /etc/cloud tree To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1849557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849554] [NEW] Please move cache files to a different location
Public bug reported: /etc/apparmor.d/cache is currently used to keep cache files for apparmor. Unfortunately, these files are in a location that is inconsistent with FHS guidelines for cache. Moreover, /etc is not a core path for Ubuntu Core 20, which means it is planned to not be writable; and to come directly from images. According to the FHS, the best location for apparmor cache files should be in a hierarchy under /var/cache. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: writable-etc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849554 Title: Please move cache files to a different location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1849554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
This bug is *not* a duplicate of 1839317; since we're not looking at ARM-based systems here. Could you please update your grub-efi-amd64 and grub-efi-amd64-signed packages (well, make sure your system is fully up to date), then run: sudo grub-install -v And include the output here. Not all the failures here are for the same causes: Joseph Maillardet (jokx), it looks like the packages are not all installed correctly, though I am not sure why (grub-install will tell); so you are booting GRUB directly, not through shim, so Secure Boot is being skipped in fun ways. This means chainloading Windows from GRUB is unlikely to work. Ivan, it sounds like your Windows no longer has a bootloader -- otherwise you should still see "Windows Boot Manager" work to boot Windows. If you see GRUB again, then it means something went missing on disk, in which case, per my comment #6, we would need to see what is on disk under /boot/efi. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964331] Re: Ubiquity chooses which drive to install to with no user input
I really don't think this is ubiquity's fault; more aiming to grub- installer, the d-i component we call as part of ubiquity. And yes, it's not at all a new issue, but something that's been difficult to handle for a number of years. Install happens properly, but in some circumstances, grub-probe / grub-installer will pick a different drive on which to install the bootloader. ** Package changed: ubiquity (Ubuntu) => grub-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964331 Title: Ubiquity chooses which drive to install to with no user input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/964331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
If you use F8 or F12 (or whatever hotkey to get the firmware's boot menu); can you then run "Windows Boot Manager" and successfully start Windows? How was the installation done? Could you please describe how the disk was partitioned for dual-booting, and the steps taked in the installer? At this moment, I am unable to reproduce the failure. Here, dual-booting Windows works fine. ** Changed in: grub2 (Ubuntu Eoan) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848142] Re: package shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Immediately after installation and rebooting into the installed system, are there any files in /var/lib/shim-signed/mok ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848142 Title: package shim-signed 1.39+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1848142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964331] Re: Ubiquity chooses which drive to install to with no user input
There's clearly something odd happening then, because I am unable to reproduce this on various hardware; installing from USB as I normally do. How are the drives partitioned to begin with? I wonder if something is keeping grub from using the hard-drive on which it installed (as one certainly rightfully would expect it to). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964331 Title: Ubiquity chooses which drive to install to with no user input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/964331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825528] Re: package shim-signed 1.33.1~16.04.5+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Setting back to Incomplete: it appears that /boot/efi is not mounted, we're trying to figure out why not. Furthermore, the files installed there are not up to date (probably because they were instaleld to the mountpoint, not to the real location), and SecureBoot is disabled on the system. ** Changed in: shim-signed (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825528 Title: package shim-signed 1.33.1~16.04.5+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1825528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847458] Re: EFI chainloader no longer uses shim lock protocol
After further discussion with Chris; seems like this might have been a misunderstanding, looking at two different source trees for the software. Chris; can you please confirm whether we've reached consensus on the state of the chainloader code for SB? From my read, the patches look to be properly applied, and chainloading Windows certainly works for me here. ** Changed in: grub2 (Ubuntu Eoan) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847458 Title: EFI chainloader no longer uses shim lock protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847806] Re: eoan: ppc64el install on pseries-eoan VM fails to install
I'm not sure what to think about this failure; what's clear is it's not 'ubiquity', because we're dealing with debian-installer, but I'm not sure what component. In fact, it looks more subtle than this, some sort of more obscure failure: Oct 11 18:42:06 base-installer: 'Ubuntu-Server 19.10 _Eoan Ermine_ - Beta ppc64el (20191011)' Oct 11 18:42:06 base-installer: Copying package lists... Oct 11 18:42:08 base-installer: Illegal instruction Oct 11 18:42:08 kernel: [ 782.792307] find[10970]: illegal instruction (4) at 77a45c98baa0 nip 77a45c98baa0 lr 77a45c98cf00 code 1 in libc-2.30.so[77a45c93+21] Oct 11 18:42:08 kernel: [ 782.793461] find[10970]: code: fb81ffe0 fba1ffe8 fbc1fff0 fbe1fff8 f821ffa1 7c7d1b78 7c9f2378 812d8f98 Oct 11 18:42:08 kernel: [ 782.793531] find[10970]: code: 7cbc2b78 7cdb3378 75290080 41820344 7c1e0066 7bde07a0 2c3ffc02 Oct 11 18:42:08 base-installer: gpgv: Signature made Fri Oct 11 06:47:32 2019 UTC Oct 11 18:42:08 base-installer: Oct 11 18:42:08 base-installer: gpgv:using RSA key D94AA3F0EFE21092 Oct 11 18:42:08 base-installer: Oct 11 18:42:08 base-installer: gpgv: Can't check signature: No public key Oct 11 18:42:08 base-installer: Oct 11 18:42:08 base-installer: Sub-process apt-key returned an error code (2) Oct 11 18:42:08 base-installer: ^MReading Package Indexes... 0%^M Oct 11 18:42:10 base-installer: ^MReading Package Indexes... Error!^M Oct 11 18:42:10 base-installer: Oct 11 18:42:10 base-installer: Writing new source list There are various instances of 'Illegal instructions' in syslog and errors we really shouldn't be seeing. What type of CPU configured to virtualize ppc64el? The exact -cpu option in use might be the culprit here. ** Package changed: ubiquity (Ubuntu) => debian-installer (Ubuntu) ** Changed in: debian-installer (Ubuntu) Importance: Medium => Undecided ** Changed in: debian-installer (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847806 Title: eoan: ppc64el install on pseries-eoan VM fails to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1847806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847721] Re: Always create the ESP
Yes; this will furthermore require work in grub-installer, partman-auto, and partman-efi. ** Also affects: partman-efi (Ubuntu) Importance: Undecided Status: New ** Changed in: partman-efi (Ubuntu) Status: New => In Progress ** Changed in: partman-efi (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: partman-efi (Ubuntu) Importance: Undecided => Medium ** Changed in: ubiquity (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847721 Title: Always create the ESP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-efi/+bug/1847721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846509] Re: networkd doesn't take into account search domain received by DHCP
I could reproduce this trivially; a simple netplan config: network: version: 2 renderer: networkd ethernets: eth0: dhcp: yes Will show that my domain "cyphermox.net" here is not passed from DHCP in networkd to resolved (and does not show in /run/systemd/resolve/stub- resolv.conf or resolv.conf), whereas if I switch the renderer to "NetworkManager", I can then see both ~. and "cyphermox.net" in search domains when running 'systemd-resolve --status'. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846509 Title: networkd doesn't take into account search domain received by DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842511] Re: Backport DBus support to 16.04
As long as any call of 'netplan apply' does not outright fail, that's good, as this was a comment based on the changes to checking if "SNAP" is set in the environment. 'netplan apply' was run as part of the autopkgtests, it does not fail when SNAP environment is missing, and running the dbus Apply command also runs successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842511 Title: Backport DBus support to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1842511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842511] Re: Backport DBus support to 16.04
The automatically identified test failures are actually limitations of
the test infrastructure: on s390x and armhf (and arm64), wifi is not
available and this leads to the tests erroring out.
Verification-done for xenial:
ubuntu@ip-172-30-0-137:~$ sudo apt install nplan
sudo: unable to resolve host ip-172-30-0-137
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
network-manager | wpasupplicant
The following NEW packages will be installed:
nplan
0 upgraded, 1 newly installed, 0 to remove and 81 not upgraded.
Need to get 44.0 kB of archives.
After this operation, 151 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 nplan
amd64 0.32~16.04.7 [44.0 kB]
Fetched 44.0 kB in 0s (118 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "en_US.UTF-8",
LANG = "fr_CA.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Selecting previously unselected package nplan.
(Reading database ... 51363 files and directories currently installed.)
Preparing to unpack .../nplan_0.32~16.04.7_amd64.deb ...
Unpacking nplan (0.32~16.04.7) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.4) ...
Setting up nplan (0.32~16.04.7) ...
ubuntu@ip-172-30-0-137:~$ dbus-send --print-reply --system --type=method_call
--dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Apply
Error org.freedesktop.DBus.Error.AccessDenied: Access to
io.netplan.Netplan.Apply() not permitted.
ubuntu@ip-172-30-0-137:~$ sudo dbus-send --print-reply --system
--type=method_call --dest=io.netplan.Netplan /io/netplan/Netplan
io.netplan.Netplan.Apply
sudo: unable to resolve host ip-172-30-0-137
method return time=1570043146.220599 sender=:1.9 -> destination=:1.10 serial=6
reply_serial=2
boolean true
ubuntu@ip-172-30-0-137:~$
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842511
Title:
Backport DBus support to 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1842511/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840832] Re: Update to netplan.io 0.98 release
Autopkgtests have been run for both bionic and disco (attached, see description), all are successful and were so without requiring to be re- run. Individual bugs have been verified for bionic and disco, despite not being labeled for disco due to the reupload Brian did. Marking verification-done for bionic and disco, as it looks like all verification steps have been done and have passed. ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840832 Title: Update to netplan.io 0.98 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1840832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840832] Re: Update to netplan.io 0.98 release
** Description changed: [Impact] This release contains 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: - - Added new "feature flags" to identify new features - - Added support for "use-domains" for DHCP overrides - - Added support for setting IPv6 MTU Bytes (LP: #1671951) - - Added a DBus interface to query and run 'netplan apply' via other apps - - Various build system fixes - - Improved validation for bonding modes - - Added support for "hash:" for hashed 802.1x passwords (LP: #1819831) - - Tolerate devices without a /sys path (LP: #1810043) - - Fix incorrect separator for networkd with ARP IP targets (LP: #1829264) + - Added new "feature flags" to identify new features + - Added support for "use-domains" for DHCP overrides + - Added support for setting IPv6 MTU Bytes (LP: #1671951) + - Added a DBus interface to query and run 'netplan apply' via other apps + - Various build system fixes + - Improved validation for bonding modes + - Added support for "hash:" for hashed 802.1x passwords (LP: #1819831) + - Tolerate devices without a /sys path (LP: #1810043) + - Fix incorrect separator for networkd with ARP IP targets (LP: #1829264) See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. = Per-release, per-arch test artifacts = - tbd + All successful test runs for bionic; disco, all architectures + + http://people.ubuntu.com/~cyphermox/netplan/bionic_amd64_log + http://people.ubuntu.com/~cyphermox/netplan/bionic_arm64_log + http://people.ubuntu.com/~cyphermox/netplan/bionic_armhf_log + http://people.ubuntu.com/~cyphermox/netplan/bionic_i386_log + http://people.ubuntu.com/~cyphermox/netplan/bionic_ppc64el_log + http://people.ubuntu.com/~cyphermox/netplan/bionic_s390x_log + http://people.ubuntu.com/~cyphermox/netplan/disco_amd64_log + http://people.ubuntu.com/~cyphermox/netplan/disco_arm64_log + http://people.ubuntu.com/~cyphermox/netplan/disco_armhf_log + http://people.ubuntu.com/~cyphermox/netplan/disco_i386_log + http://people.ubuntu.com/~cyphermox/netplan/disco_ppc64el_log + http://people.ubuntu.com/~cyphermox/netplan/disco_s390x_log [Discussion] This addresses in priority an important issue with integration of netplan with openvswitch; where devices are hard to bring up to hand over to openvswitch: behavior was changed such that as soon as a device is listed in netplan config (even without an IP), it gets brought online by the networkd renderer. This is consistent with the idea of having only configured interfaces touched by netplan; if the name of the itnerface appears in netplan YAML, it gets configured (albeit without IP). [Changelog] 9ea105b Drop NETPLAN_VERSION not in spec for feature flags 2f282a0 Fix typo in doc 402390f Really fix test_bond_arp_targets_many_lp1829264: can't read() the same thing twice d0b93e3 Fix order of parameters for arp_ip_targets bug test; assertIn wants expected, output 61eb382 Add feature flags for new use-domains and ipv6 mtubytes features 1662819 Make the DBus 'NoSuchCommand' test less dependent on versions of DBus b1de740 Add test for DBus Info method ed17088 Drop -renderer check in info tests, fails because we don't list renderers c13ef8d Make more small fixes to Makefile to cleanup doubled-up slashes 97f5a50 Drop netplan-features flags for NM and networkd renderers for now d60072a Drop dead files for C Python module version info 8ba9afe io.netplan.Netplan.service.in: add assumed apparmor label f39f2be Add a 'netplan info' command (feature-flags spec) 5d22e9d Add support for UseDomains override to DHCP 76bbf79 Bonding mode validation d068d9d document ipv6-mtu d93b6c1 write IPv6MTUBytes to the .network file 8878a6f support for parsing ipv6-mtu on all netdev types 67872af .gitignore: ignore the dbus generated svc unit file 0231f99 tests/dbus: add tests for apply in a snap using dbus 147a4bf cli/apply: use dbus if inside a snap 0c8e5fe make output more deterministic and fix tests 95305a1 doc: clarify that bonding
[Bug 1671951] Re: networkd should allow configuring IPV6 MTU
Verification-done on disco:
ubuntu@ip-172-30-0-243:~$ lsb_release -cs
disco
ubuntu@ip-172-30-0-243:~$ dpkg -l netplan.io systemd | grep ii
ii netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network
configuration abstraction for various backends
ii systemd240-6ubuntu5.7amd64system and service manager
ubuntu@ip-172-30-0-243:~$ sudo netplan apply
ubuntu@ip-172-30-0-243:~$ ip link
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu qdisc fq_codel state UP
mode DEFAULT group default qlen 1000
link/ether 06:92:5b:c9:b5:3d brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-30-0-243:~$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routableconfigured
2 links listed.
ubuntu@ip-172-30-0-243:~$ sysctl net.ipv6.conf.eth0.mtu
net.ipv6.conf.eth0.mtu = 5634
ubuntu@ip-172-30-0-243:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
match:
macaddress: 06:92:5b:c9:b5:3d
set-name: eth0
ipv6-mtu: 5634
mtu:
dhcp6: true
dhcp4-overrides:
use-mtu: false
dhcp6-overrides:
use-mtu: false
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671951] Re: networkd should allow configuring IPV6 MTU
Verification-done on bionic:
ubuntu@ip-172-30-0-140:/run/systemd/network$ lsb_release -cs
bionic
ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l netplan.io | grep ii
ii netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network
configuration abstraction for various backends
ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l systemd | grep ii
ii systemd237-3ubuntu10.31 amd64system and service manager
ubuntu@ip-172-30-0-140:/run/systemd/network$ cat
/etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
dhcp4: true
match:
macaddress: 06:e0:25:2e:08:ef
set-name: eth0
ipv6-mtu: 5634
mtu:
dhcp6: true
dhcp4-overrides:
use-mtu: false
dhcp6-overrides:
use-mtu: false
ubuntu@ip-172-30-0-140:/run/systemd/network$ sudo netplan apply
ubuntu@ip-172-30-0-140:/run/systemd/network$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether routableconfigured
2 links listed.
ubuntu@ip-172-30-0-140:/run/systemd/network$ sysctl net.ipv6.conf.eth0.mtu
net.ipv6.conf.eth0.mtu = 5634
ubuntu@ip-172-30-0-140:/run/systemd/network$ ip link
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu qdisc fq_codel state UP
mode DEFAULT group default qlen 1000
link/ether 06:e0:25:2e:08:ef brd ff:ff:ff:ff:ff:ff
ubuntu@ip-172-30-0-140:/run/systemd/network$
** Tags removed: verification-needed verification-needed-bionic zesty
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829264] Re: incorrect separator for multiple ARP IP targets
Verification-done on bionic: ubuntu@ubuntu-XPS-15-9570:~$ lsb_release -cs bionic ubuntu@ubuntu-XPS-15-9570:/sys/class/net/bond0/bonding$ dpkg -l netplan.io | grep ii ii netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network configuration abstraction for various backend ubuntu@ubuntu-XPS-15-9570:~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: networkd wifis: wlp59s0: access-points: cyphermox-secure: auth: [REDACTED] #dhcp4: yes bonds: bond0: interfaces: [ wlp59s0 ] dhcp4: yes parameters: arp-ip-targets: [ 10.3.0.1, 10.3.1.155 ] arp-interval: 2s mode: active-backup ubuntu@ubuntu-XPS-15-9570:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp59s0: mtu 1500 qdisc noqueue master bond0 state UP group default qlen 1000 link/ether d2:52:7d:ad:79:49 brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether d2:52:7d:ad:79:49 brd ff:ff:ff:ff:ff:ff inet 10.3.1.244/22 brd 10.3.3.255 scope global dynamic bond0 valid_lft 14346sec preferred_lft 14346sec inet6 fe80::d052:7dff:fead:7949/64 scope link valid_lft forever preferred_lft forever ubuntu@ubuntu-XPS-15-9570:~$ cd /sys/class/net/bond0/bonding/ ubuntu@ubuntu-XPS-15-9570:/sys/class/net/bond0/bonding$ cat mode active-backup 1 ubuntu@ubuntu-XPS-15-9570:/sys/class/net/bond0/bonding$ cat arp_interval 2000 ubuntu@ubuntu-XPS-15-9570:/sys/class/net/bond0/bonding$ cat arp_ip_target 10.3.1.155 10.3.0.1 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829264 Title: incorrect separator for multiple ARP IP targets To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1829264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829264] Re: incorrect separator for multiple ARP IP targets
Verification-done for disco: ubuntu@oddish:~$ lsb_release -cs disco ubuntu@oddish:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network configuration abstraction for various backends ubuntu@oddish:~$ cat /etc/netplan/01-network-manager-all.yaml network: version: 2 renderer: networkd wifis: wlp58s0: access-points: cyphermox-secure: auth: [REDACTED\] #dhcp4: yes bonds: bond0: interfaces: [ wlp58s0 ] dhcp4: yes parameters: arp-ip-targets: [ 10.3.0.1, 10.3.1.155 ] arp-interval: 2s mode: active-backup ubuntu@oddish:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp58s0: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether fa:a1:43:45:b8:0f brd ff:ff:ff:ff:ff:ff 3: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether fa:a1:43:45:b8:0f brd ff:ff:ff:ff:ff:ff inet 10.3.1.245/22 brd 10.3.3.255 scope global dynamic bond0 valid_lft 14355sec preferred_lft 14355sec inet6 fe80::f8a1:43ff:fe45:b80f/64 scope link valid_lft forever preferred_lft forever ubuntu@oddish:~$ cd /sys/class/net/bond0/bonding/ ubuntu@oddish:/sys/class/net/bond0/bonding$ cat mode active-backup 1 ubuntu@oddish:/sys/class/net/bond0/bonding$ cat arp_interval 2000 ubuntu@oddish:/sys/class/net/bond0/bonding$ cat arp_ip_target 10.3.1.155 10.3.0.1 ** Tags removed: verification-needed ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829264 Title: incorrect separator for multiple ARP IP targets To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1829264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819831] Re: broken generation of wpa config for hashed passwords
Verification-done on bionic: ubuntu@ubuntu-XPS-15-9570:~$ lsb_release -cs bionic ubuntu@ubuntu-XPS-15-9570:~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: networkd wifis: wlp59s0: access-points: cyphermox-secure: auth: key-management: eap method: peap identity: [redacted] password: hash:[redacted] dhcp4: yes ubuntu@ubuntu-XPS-15-9570:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp59s0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 9c:b6:d0:bc:7e:e5 brd ff:ff:ff:ff:ff:ff inet 10.3.1.195/22 brd 10.3.3.255 scope global dynamic wlp59s0 valid_lft 14372sec preferred_lft 14372sec inet6 fe80::9eb6:d0ff:febc:7ee5/64 scope link valid_lft forever preferred_lft forever ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819831 Title: broken generation of wpa config for hashed passwords To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1819831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810043] Re: netplan apply fails if NIC alias exists
Verification-done on disco as well: After applying the update I can successfully run 'netplan apply' on a system on which a label exists; this would otherwise fail even if the interface isn't mentioned in YAML: ubuntu@oddish:~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager ubuntu@oddish:~$ ip addr show wlp58s0 2: wlp58s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 44:85:00:1d:8f:df brd ff:ff:ff:ff:ff:ff inet 10.3.1.243/22 brd 10.3.3.255 scope global dynamic noprefixroute wlp58s0 valid_lft 14118sec preferred_lft 14118sec inet 192.168.0.1/24 scope global wlp58s0:0 valid_lft forever preferred_lft forever inet6 2001:470:b0cc::78b/128 scope global dynamic noprefixroute valid_lft 28528sec preferred_lft 6928sec inet6 fe80::3070:bc33:a203:cbc3/64 scope link noprefixroute valid_lft forever preferred_lft forever Before: ubuntu@oddish:~$ sudo netplan apply Traceback (most recent call last): File "/usr/sbin/netplan", line 23, in netplan.main() File "/usr/share/netplan/netplan/cli/core.py", line 50, in main self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 43, in run self.run_command() File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command self.func() File "/usr/share/netplan/netplan/cli/commands/apply.py", line 106, in command_apply stderr=subprocess.DEVNULL) File "/usr/lib/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/wlp58s0:0']' returned non-zero exit status 1. After: ubuntu@oddish:~$ sudo netplan apply [prompt returns with no error] ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810043 Title: netplan apply fails if NIC alias exists To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1810043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819831] Re: broken generation of wpa config for hashed passwords
Verification-done on disco: ubuntu@oddish:~$ lsb_release -cs disco ubuntu@oddish:~$ cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: networkd wifis: wlp58s0: access-points: cyphermox.net: password: hash:[redacted] dhcp4: yes ubuntu@oddish:~$ ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wlp58s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 44:85:00:1d:8f:df brd ff:ff:ff:ff:ff:ff inet 10.3.1.243/22 brd 10.3.3.255 scope global dynamic wlp58s0 valid_lft 14345sec preferred_lft 14345sec ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819831 Title: broken generation of wpa config for hashed passwords To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1819831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842511] Re: Backport DBus support to 16.04
Fix Released in eoan (where netplan is 'netplan.io'); Won't Fix for the netplan.io xenial task, since the name of the source package is 'nplan' there. ** Changed in: netplan.io (Ubuntu) Status: New => Fix Released ** Changed in: netplan.io (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842511 Title: Backport DBus support to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1842511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612906] Re: cryptsetup does not support ZFS
** Tags removed: rls-y-incoming ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612906 Title: cryptsetup does not support ZFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1612906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591427] Re: option to deactivate automatic updates leads people to believe that security updates will be disabled too
This has been fixed for a while; APT::Periodic::Unattended-Upgrade is set to 0 if you pick No automatic updates; this is how we want things to be. In the installer, the other option is to "install security updates automatically". ** Changed in: pkgsel (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591427 Title: option to deactivate automatic updates leads people to believe that security updates will be disabled too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkgsel/+bug/1591427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 927636] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
** Tags removed: rls-y-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/927636 Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct() To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611256] Re: X to Y upgrade fails with gconf2 depends on python3:any; however: Package python3 is not configured yet.
** Tags removed: rls-y-incoming ** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611256 Title: X to Y upgrade fails with gconf2 depends on python3:any; however: Package python3 is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/1611256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366546] Re: Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
** Tags removed: rls-y-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366546 Title: Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1366546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723390] Re: lxd containers have become degraded
** Tags removed: rls-aa-incoming ** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723390 Title: lxd containers have become degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721839] Re: [REGRESSION] Services asked for by UDEV do not get triggered
Is this still an issue on supported releases? ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Tags removed: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721839 Title: [REGRESSION] Services asked for by UDEV do not get triggered To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1721839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844626] [NEW] Please remove compiz-plugins-experimental from eoan-proposed
Public bug reported: Please remove compiz-plugins-experimental 2:0.8.16-2 All architectures are in Dependency wait; compiz-plugins-experimental is waiting on the whole compiz stack with 2:0.8.16-2. Past feature-freeze and DI freeze, this is unlikely to land right now and may be re-synced later together with the other compiz packages. ** Affects: compiz-plugins-experimental (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844626 Title: Please remove compiz-plugins-experimental from eoan-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-experimental/+bug/1844626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844553] [NEW] Please remove node-prismjs from eoan-proposed
Public bug reported: Please remove node-prismjs from eoan-proposed - it's blocked on non-existing node-clipboard - has an RC bug in Debian on that subject, - only in unstable and blocked there for >200 days ** Affects: node-prismjs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844553 Title: Please remove node-prismjs from eoan-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-prismjs/+bug/1844553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799977] Re: [MIR] gssdp
I can't find who promoted this package to main; but it is there right now, and it seems it also was in previous releases. Closing as Fix Released based on the ack from Seb128 thatit would be subscribed to by desktop-bugs. ** Changed in: gssdp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
So with my PPA version, what do you have in /run/usb_modeswitch/current_cfg then? I suspect the program is crashing, I probably made a small mistake in the patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842511] Re: Backport DBus support to 16.04
** Description changed: + [Impact] + Snapd will want to make use of the DBus support to call on netplan to apply network configuration changes live, when asked by snap applications. + + [Test case] + Run the following command: + $ dbus-send --print-reply --system --type=method_call --dest=io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan.Apply + + You should expect to see a response like this: + + method return time=1567801560.502553 sender=:1.1712 -> destination=:1.1714 serial=6 reply_serial=2 +boolean true + + Which means the command was run; netplan configuration was applied. + + Check that any changes to the netplan YAML were applied to the + interfaces. + + [Regression potential] + Pay close attention to the behavior of the 'netplan apply' command, which has had to be slightly changed to behave correctly when run in the context of snaps (when the SNAP environment variable is set). Any issues there would have to be considered as potential regressions from the update. Regression potential is very low because the changes are limitted to ensuring there; that 'netplan apply' does the right thing in calling the dbus methods when they should, which will then run the command correctly. + Other changes are limited to providing the new netplan-dbus binary, which is self-contained. + + --- + Please backport the DBus feature in netplan to Ubuntu 16.04's version of netplan. netplan is used on Core 16; DBus support would be used by snapd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842511 Title: Backport DBus support to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1842511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842921] Re: [MIR] libio-async-loop-epoll-perl, liblinux-epoll-perl (lintian dependencies)
MIR approved for both libio-async-loop-epoll-perl and liblinux-epoll- perl. Both have a subscriber, and I did a cursory review of the code. These perl packages are well maintained by the Debian Perl team and the packaging is simple. I'm approving these as per the usual process: Perl packages are well maintained in Debian, low maintenance burden when included in main in Ubuntu. ** Changed in: libio-async-loop-epoll-perl (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: liblinux-epoll-perl (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842921 Title: [MIR] libio-async-loop-epoll-perl, liblinux-epoll-perl (lintian dependencies) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libio-async-loop-epoll-perl/+bug/1842921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Rather than pasting just a single error line, please include the full debug log for running usb-modeswitch. You can do that by modifying /etc/usb_modeswitch.conf: EnableLogging=1 And looking under /var/log/ for the log file written by usb-modeswitch after it has run. Having the full file means we know exactly what happens as usb- modeswitch tries to probe the device, it will be much easier to figure out what goes wrong and why. The "Could not read attribute" might not be fatal by itself; something else is likely making it impossible to figure out what type of device exactly it is and whether it is in the right mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842511] [NEW] Backport DBus support to 16.04
Public bug reported: Please backport the DBus feature in netplan to Ubuntu 16.04's version of netplan. netplan is used on Core 16; DBus support would be used by snapd. ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842511 Title: Backport DBus support to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1842511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842134] Re: Please remove link-grammar from the archive
Well, if it was a matter of never having been tested on 32-bits, that's something we can also address by removing the builds for 32-bits. The specific errors are here; when running autopkgtests which try to rebuild the package and run unit tests: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/armhf/l/link-grammar/20190902_090536_925cc@/log.gz Or simply here, at build time: https://launchpadlibrarian.net/438576953 /buildlog_ubuntu-eoan-armhf.link-grammar_5.6.2-1ubuntu1_BUILDING.txt.gz Specifically, the issues for armhf are with linking: /bin/bash ../../libtool --tag=CXX --mode=link g++ -D_DEFAULT_SOURCE -std=c++11 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall -version-info 11:2:6 -export-dynamic -no-undefined -export-symbols ./link-grammar-java.def -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o liblink-grammar-java.la -rpath /usr/lib/arm-linux-gnueabihf jni-client.lo ../../link-grammar/liblink-grammar.la -lhunspell-1.7 -lminisat -lm libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf/crti.o /usr/lib/gcc/arm-linux-gnueabihf/9/crtbeginS.o .libs/jni-client.o -Wl,-rpath -Wl,/<>/link-grammar/.libs -Wl,--as-needed ../../link-grammar/.libs/liblink-grammar.so -lhunspell-1.7 -lminisat -L/usr/lib/gcc/arm-linux-gnueabihf/9 -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../../../lib -L/lib/arm-linux-gnueabihf -L/lib/../lib -L/usr/lib/arm-linux-gnueabihf -L/usr/lib/../lib -L/usr/lib/gcc/arm-linux-gnueabihf/9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/arm-linux-gnueabihf/9/crtendS.o /usr/lib/gcc/arm-linux-gnueabihf/9/../../../arm-linux-gnueabihf/crtn.o -g -O2 -fstack-protector-strong -O3 -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-soname -Wl,liblink-grammar-java.so.5 -Wl,-retain-symbols-file -Wl,./link-grammar-java.def -o .libs/liblink-grammar-java.so.5.6.2 /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 7362 >= 3462 for section `.strtab' /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 17702 >= 3462 for section `.strtab' /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 4297 >= 3462 for section `.strtab' /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 11253 >= 3462 for section `.strtab' /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 14316 >= 3462 for section `.strtab' /usr/bin/ld: ../../link-grammar/.libs/liblink-grammar.so: invalid string offset 19556 >= 3462 for section `.strtab' [...] I'm happy to drop the i386 and armhf architectures from the package though, if that's the best solution. ** Summary changed: - Please remove link-grammar from the archive + Tests / linking errors on i386 and armhf ** Description changed: link-grammar is blocking migration of some packages from eoan-proposed, and has been for a number of days: sqlite3 (3.29.0-1 to 3.29.0-2) in proposed for 14 days Regressions link-grammar/5.6.2-1ubuntu1: armhf (log, history), i386 (log, history) python3.7 (3.7.4-2ubuntu1 to 3.7.4-3) in proposed for 8 days Regressions link-grammar/5.6.2-1ubuntu1: armhf (log, history), i386 (log, history) - - I've made a reasonable effort of fixing it (including upstream fixes, etc.), but it's still blocking due to autopkgtests failing, and the mode of failure (linkage errors in armhf, test failures in i386) make me expect that the package might not serve its purpose on these architectures at all, even if tests were to be skipped. + I've made a reasonable effort of fixing it (including upstream fixes, + etc.), but it's still blocking due to autopkgtests failing, and the mode + of failure (linkage errors in armhf, test failures in i386) make me + expect that the package might not serve its purpose on these + architectures at all, even if tests were to be skipped. On Debian, the package is orphaned, in need of a maintainer. The version in Ubuntu is the same as the one uploaded to Debian unstable; plus my attempt at fixing the package (which also fixed the original FTBFS of the current version in Debian unstable). - - As such, I expect it will in time be removed from Debian. - - link-grammar has no important reverse-depends: - - ╰─ reverse-depends link-grammar - Reverse-Recommends - == - * science-linguistics - - Please remove link-grammar source and its binaries from the archive in - eoan. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842134 Title: Tests / linking errors on i386 and armhf To manage notifications about this bug go to:
[Bug 1841595] Re: [MIR] tpm2-tss
Yes, those probably should be addressed. I don't necessarily do all the work on these packages though; but I might have time next week to look at them, and prepare a proper new release (with the testing that should go with). Mario, let's see if we can block out just a bit of time to do this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841595 Title: [MIR] tpm2-tss To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tss/+bug/1841595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842134] [NEW] Please remove link-grammar from the archive
Public bug reported: link-grammar is blocking migration of some packages from eoan-proposed, and has been for a number of days: sqlite3 (3.29.0-1 to 3.29.0-2) in proposed for 14 days Regressions link-grammar/5.6.2-1ubuntu1: armhf (log, history), i386 (log, history) python3.7 (3.7.4-2ubuntu1 to 3.7.4-3) in proposed for 8 days Regressions link-grammar/5.6.2-1ubuntu1: armhf (log, history), i386 (log, history) I've made a reasonable effort of fixing it (including upstream fixes, etc.), but it's still blocking due to autopkgtests failing, and the mode of failure (linkage errors in armhf, test failures in i386) make me expect that the package might not serve its purpose on these architectures at all, even if tests were to be skipped. On Debian, the package is orphaned, in need of a maintainer. The version in Ubuntu is the same as the one uploaded to Debian unstable; plus my attempt at fixing the package (which also fixed the original FTBFS of the current version in Debian unstable). As such, I expect it will in time be removed from Debian. link-grammar has no important reverse-depends: ╰─ reverse-depends link-grammar Reverse-Recommends == * science-linguistics Please remove link-grammar source and its binaries from the archive in eoan. ** Affects: link-grammar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842134 Title: Please remove link-grammar from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/link-grammar/+bug/1842134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829264] Re: incorrect separator for multiple ARP IP targets
** Description changed:
+ [Impact]
+ Users of netplan who need to configure multiple values for ARP IP targets.
+
+ [Test case]
+ Write a valid configuration for a bond with multiple ARP IP targets:
+
+ network:
+ version: 2
+ renderer: networkd
+ bond:
+ bd0:
+ [...]
+ parameters:
+ arp-ip-targets: [ 192.168.3.56, 192.168.3.59 ]
+
+ Verify that the configuration is sucessfully applied, and shows up in
+ the /sys filesystem for the affected device:
+
+ /sys/class/net/bd0/bonding/arp_ip_targets
+
+ [Regression potential]
+ This affects only this particular value and generating a valid configuration
file for the networkd renderer. The existing configuration file generation is
/invalid/, but working as the bad value is ignored by systemd-networkd. This
changes the generation of the configuration file only, to write the proper
sequence of values for ARPIPTargets=.
+
+ ---
+
https://github.com/CanonicalLtd/netplan/blob/ea47bd4e1c5319b1a624ea61c843ee96e7c128da/src/networkd.c#L208
The separator used to add multiple ARP IP targets for the networkd
renderer is ",".
Unfortunately, networkd doesn't allow that, but rather expects
whitespace:
(in config_parse_arp_ip_target_address():)
[...]
- for (;;) {
- [...]
- r = extract_first_word(, , NULL, 0);
+ for (;;) {
+ [...]
+ r = extract_first_word(, , NULL, 0);
extract_first_word's third parameter is const char *separators; where
NULL is handled like so (src/basic/extract-word.c:37):
- if (!separators)
- separators = WHITESPACE;
+ if (!separators)
+ separators = WHITESPACE;
Finally:
src/basic/string-util.h:#define WHITESPACE" \t\n\r"
So; it doesn't handle commas for the list, just whitespace; so let's
give it whitespace please :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829264
Title:
incorrect separator for multiple ARP IP targets
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1829264/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819831] Re: broken generation of wpa config for hashed passwords
** Description changed: + [Impact] + netplan users configuring a wireless connection; who would like to use password hashes for the password (ie. they might not know the real password, etc.) + + [Test case] + Write configuration for netplan wireless interface: + + network: + version: 2 + wifis: + wlan0: + access-points: + MyAccessPoint: + password: hash:83d…0b11 + + Verify that the wireless network can be succesfully connected to. + + [Regression Potential] + This has a minimal risk of regression. Passwords do not typically include "hash:" as first characters, and if so may be escaped via quoting. This does not otherwise affect any other feature of netplan, and is limited to allowing users to use the commonly accepted format of hashed passwords to pass to the renderer, for connecting to wifi. + + --- + Have a look at the netplan.io config file at https://gist.github.com/fluffy/e2a202a0816299d519dabf7bbed2f7bb for 802.1 auth for a wired network. This will generate a wpa config file at /run/netplan/wpa-enp4s0.conf that has password="hash:83d…0b11" However, this is not correct. It should not have the quotes and should look like password=hash:83d…0b11 The quotes cause the wpa_suppicant to not detect this is a hashed password and instead think it is a normal password that starts with hash: This is an important bug because at Cisco we can not store our passwords unhashed on disk and our production network requires 802.1x auth. I think this is simple to fix and I'm glad to send a PR or any other information that helps fix it. Thank you for looking at this, Cullen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819831 Title: broken generation of wpa config for hashed passwords To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1819831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810043] Re: netplan apply fails if NIC alias exists
** Description changed: - # netplan apply + [Impact] + Running 'netplan apply' when an interface has an alias/label defined for it. + + [Test case] + On a system which has a label set for an interface: + ip addr add 192.168.0.1/24 dev eth0 label eth0:0 + + 1) run 'netplan apply' + 2) verify that the configuration for netplan can be applied without errors. + + [Regression potential] + This has minimal risk, and only adds an extra check for a subprocess call that will otherwise fail, but is safely skipped. Avoid crashing in netplan when the files required to run 'net_setup_link' are not available, as the rest of the process will already run net_setup_link for the "master" interface which will have its own files in /sys/class/net. + + --- + + + # netplan apply Traceback (most recent call last): - File "/usr/sbin/netplan", line 23, in - netplan.main() - File "/usr/share/netplan/netplan/cli/core.py", line 50, in main - self.run_command() - File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command - self.func() - File "/usr/share/netplan/netplan/cli/commands/apply.py", line 43, in run - self.run_command() - File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command - self.func() - File "/usr/share/netplan/netplan/cli/commands/apply.py", line 93, in command_apply - stderr=subprocess.DEVNULL) - File "/usr/lib/python3.6/subprocess.py", line 291, in check_call - raise CalledProcessError(retcode, cmd) + File "/usr/sbin/netplan", line 23, in + netplan.main() + File "/usr/share/netplan/netplan/cli/core.py", line 50, in main + self.run_command() + File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command + self.func() + File "/usr/share/netplan/netplan/cli/commands/apply.py", line 43, in run + self.run_command() + File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command + self.func() + File "/usr/share/netplan/netplan/cli/commands/apply.py", line 93, in command_apply + stderr=subprocess.DEVNULL) + File "/usr/lib/python3.6/subprocess.py", line 291, in check_call + raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/eth0:0']' returned non-zero exit status 4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810043 Title: netplan apply fails if NIC alias exists To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1810043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671951] Re: networkd should allow configuring IPV6 MTU
** Description changed: + = netplan.io = + + [Impact] + + * IPv6 traffic failing to send/receive due to incompatible/low MTU + setting. Specifically, IPv6 traffic may have higher MTU requirements + than IPv4 traffic and thus may need to be overridden and/or set to a + higher value than IPv6 traffic. + + [Test Case] + * Apply a netplan configuration that specifices ipv6-mtu: + + network: + version: 2 + ethernets: + eth0: + dhcp4: true + dhcp6: true + ipv6-mtu: 6000 + + * Check that MTU bytes, is at least IPv6MTUBytes on the interface: + + $ sysctl net.ipv6.conf.eth0.mtu + net.ipv6.conf.eth0.mtu = 6000 + + [Regression Potential] + + * This is a future compatible backport of an additional keyword not + used by default. It may result in MTU change to a higher value, which + should not cause loss of connectivity. + + [Other Info] + + * Original bug report below + + = end of netplan.io = + = systemd = [Impact] - * IPv6 traffic failing to send/receive due to incompatible/low MTU + * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] - * Use IPv6MTUBytes= setting in a .network unit - * Restart systemd-network - * Check that there no error messages / warnings about not-recognizing this option - * Check that MTU bytes, is at least IPv6MTUBytes on the interface + * Use IPv6MTUBytes= setting in a .network unit + * Restart systemd-network + * Check that there no error messages / warnings about not-recognizing this option + * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] - * This is a future compatible backport of an additional keyword not + * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] - - * Original bug report below + + * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Please describe the problem here, rather than in forum posts. It's not helpful to have to go through various pages and posts from different people, with information that is potentially irrelevant to the bug. To compound to the situation, pastebins have disappeared by now. Please include all the debugging information you can here, and a clear description of the problem, and then it should be relatively easy to fix the bug. ** Changed in: usb-modeswitch (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840832] Re: Update to netplan.io 0.98 release
** Also affects: netplan.io (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840832 Title: Update to netplan.io 0.98 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1840832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837934] Re: There is no warning to remove install media when rebooting
Is this tested in VirtualBox or on hardware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837934 Title: There is no warning to remove install media when rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1837934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840832] [NEW] Update to netplan.io 0.98 release
Public bug reported: [Impact] This release contains 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: - Added new "feature flags" to identify new features - Added support for "use-domains" for DHCP overrides - Added support for setting IPv6 MTU Bytes (LP: #1671951) - Added a DBus interface to query and run 'netplan apply' via other apps - Various build system fixes - Improved validation for bonding modes - Added support for "hash:" for hashed 802.1x passwords (LP: #1819831) - Tolerate devices without a /sys path (LP: #1810043) - Fix incorrect separator for networkd with ARP IP targets (LP: #1829264) See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. = Per-release, per-arch test artifacts = tbd [Discussion] This addresses in priority an important issue with integration of netplan with openvswitch; where devices are hard to bring up to hand over to openvswitch: behavior was changed such that as soon as a device is listed in netplan config (even without an IP), it gets brought online by the networkd renderer. This is consistent with the idea of having only configured interfaces touched by netplan; if the name of the itnerface appears in netplan YAML, it gets configured (albeit without IP). [Changelog] 9ea105b Drop NETPLAN_VERSION not in spec for feature flags 2f282a0 Fix typo in doc 402390f Really fix test_bond_arp_targets_many_lp1829264: can't read() the same thing twice d0b93e3 Fix order of parameters for arp_ip_targets bug test; assertIn wants expected, output 61eb382 Add feature flags for new use-domains and ipv6 mtubytes features 1662819 Make the DBus 'NoSuchCommand' test less dependent on versions of DBus b1de740 Add test for DBus Info method ed17088 Drop -renderer check in info tests, fails because we don't list renderers c13ef8d Make more small fixes to Makefile to cleanup doubled-up slashes 97f5a50 Drop netplan-features flags for NM and networkd renderers for now d60072a Drop dead files for C Python module version info 8ba9afe io.netplan.Netplan.service.in: add assumed apparmor label f39f2be Add a 'netplan info' command (feature-flags spec) 5d22e9d Add support for UseDomains override to DHCP 76bbf79 Bonding mode validation d068d9d document ipv6-mtu d93b6c1 write IPv6MTUBytes to the .network file 8878a6f support for parsing ipv6-mtu on all netdev types 67872af .gitignore: ignore the dbus generated svc unit file 0231f99 tests/dbus: add tests for apply in a snap using dbus 147a4bf cli/apply: use dbus if inside a snap 0c8e5fe make output more deterministic and fix tests 95305a1 doc: clarify that bonding parameters up/down-delay only apply to miimon monitoring 178ab45 Makefile: add tests/generator/*.py to PYCODE 5c0d66c Honor LDFLAGS when linking the generator be2a3a1 Stylistic change. b5faf4a Add tests for the new hash: password support. 2f159b9 fix indentation d9767fb Support hashed passwords for 802.1x 495263a tests: rework dbus test to work with older python versions 2d60fae add dbus based "netplan apply" interface 7a1127f Tolerate devices without a /sys path ee94ec1 Fix incorrect separator for networkd with ARP IP targets (LP: #1829264) ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840832 Title: Update to netplan.io 0.98 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1840832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810043] Re: netplan apply fails if NIC alias exists
** Changed in: netplan Status: Fix Committed => Fix Released ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810043 Title: netplan apply fails if NIC alias exists To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1810043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832404] Re: sit tunnel should not require the local param
Are we sure that not include "local:" does the right thing with systemd- networkd? I can't say that I saw any code that hinted towards the fact that it would be figured out automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832404 Title: sit tunnel should not require the local param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1832404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1671951] Re: networkd should allow configuring IPV6 MTU
** Changed in: netplan.io (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1671951 Title: networkd should allow configuring IPV6 MTU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819831] Re: broken generation of wpa config for hashed passwords
** Changed in: netplan Status: Triaged => Fix Released ** Changed in: netplan.io (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819831 Title: broken generation of wpa config for hashed passwords To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1819831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836695] Re: Netplan ignores static routes when using DHCP
Since netplan only does writing configuration to be consumed by the backends like systemd, this would actually be a systemd bug; reassigning. I thought that worked though, in some setups, especially with use- routes: false as it was being done in the config above. Nevertheless, it needs investigation. I expect we could see the routes are being installed, then ripped out after systemd-networkd gets an address from DHCP. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan Status: New => Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836695 Title: Netplan ignores static routes when using DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1836695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786489] Re: [MIR] rygel
Current state appears to be that Desktop Team should look into the Recommends (gstreamer plugins-ugly), and someone have a review of the XML parser options (as pointed out in the security review, specifically for NOENT and RECOVER... maybe NONET should be added?). ** Changed in: rygel (Ubuntu) Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786489 Title: [MIR] rygel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/1786489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746629] Re: [MIR] libbluray
I will review this now; but I expect it might need security review as well. ** Changed in: libbluray (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746629 Title: [MIR] libbluray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbluray/+bug/1746629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840352] [NEW] renderers are not listed in netplan feature flags
Public bug reported: 'netplan info' can list features that have been added to netplan in recent versions. However, it does not list renderers. Should we list them? Does it make sense to? How do we think having the list of renderers exposed would actually change the behavior of things like cloud-init in the real world? ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840352 Title: renderers are not listed in netplan feature flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1840352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838989] Re: [MIR] libnftnl: dependency of iptables
There was a previous MIR approved, and as per the usual process we do not require a new MIR bug and review if the package was in Main before and we can point to the previous MIR bug. This package is fine to promote back to main. ** Changed in: libnftnl (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838989 Title: [MIR] libnftnl: dependency of iptables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnftnl/+bug/1838989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838322] Re: Support Japanese new era "令和 (Reiwa)"
** Also affects: icu (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838322 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1838322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
