[Bug 1800668] Re: Clarify MAC and MTU setting requirements
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1800668 Title: Clarify MAC and MTU setting requirements To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1800668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804861] Re: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1804861 Title: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1804861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799487] Re: Support for sit (ipv6) tunnels
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1799487 Title: Support for sit (ipv6) tunnels To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1799487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800669] Re: Various documentation fixes
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1800669 Title: Various documentation fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1800669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807273] Re: netplan not respecting mtu
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1807273 Title: netplan not respecting mtu To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1807273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1811868 Title: networkd/NetworkManager are not re-started on netplan apply when config files are removed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817655] Re: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco)
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1817655 Title: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817660] Re: test_terminal.TestTerminal tests fail when run a second time
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1817660 Title: test_terminal.TestTerminal tests fail when run a second time To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: Cannot enable IPv6 privacy extensions
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** 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/1750392 Title: Cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739578] Re: Missing support for WPA2 Enterprise
This is still verification-done for bionic; re-upload was to skip some failing tunnel tests due to a difference in kernel behavior. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** 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/1739578 Title: Missing support for WPA2 Enterprise To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1739578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805490] Re: Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required."
** Changed in: grub2-signed (Ubuntu Disco) Status: Incomplete => Triaged ** Tags removed: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805490 Title: Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1805490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820226] Re: [MIR] twitter-bootstrap3 as dependency of mailman3
Couldn't this simply work with libjs-bootstrap4? Seems like using bootstrap4 would be a net improvement anyway, especially sicne it then wouldn't be encumbered by the open CVEs. For me; it's a tentative ACK for the MIR provided the Security Team also ACKs it. I'm not looking for a full code-review -- I did that, nothing jumps out (but yeah, sure, XSS CVEs); but I think we ought to have a formal decision from the security team as to whether they are fine with this as-is; or as I think, that it would be *much* preferable to use twitter-bootstrap4. ** Changed in: twitter-bootstrap3 (Ubuntu) Status: New => In Progress ** Changed in: twitter-bootstrap3 (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Server (ubuntu-server) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820226 Title: [MIR] twitter-bootstrap3 as dependency of mailman3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/twitter-bootstrap3/+bug/1820226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824213] [NEW] GRUB_HIDDEN_TIMEOUT still referred to in postinst scripts despite change to GRUB_TIMEOUT_STYLE=hidden
Public bug reported: We've moved to using GRUB_TIMEOUT_STYLE=hidden in /etc/default/grub, but debian/postinst.in still references GRUB_HIDDEN_TIMEOUT variable and attempts to set that in conffile handling: case @PACKAGE@ in grub-pc) apply_conf_tweaks "$conf_files" merge_debconf_into_conf GRUB_TIMEOUT grub-pc/timeout apply_conf_tweaks "$conf_files" sed_conf 's/^(GRUB_TIMEOUT=)"([0-9][0-9]*)"/\1\2/' db_get grub-pc/hidden_timeout if [ "$RET" = false ]; then apply_conf_tweaks "$conf_files" sed_conf 's/^GRUB_HIDDEN_TIMEOUT=/#&/' fi ;; This may lead to confusion in grub's conffile handling and in the resulting /etc/default/grub, potentially leading to unnecessary debconf/ucf prompts for conffile changes. ** Affects: grub2 (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/1824213 Title: GRUB_HIDDEN_TIMEOUT still referred to in postinst scripts despite change to GRUB_TIMEOUT_STYLE=hidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1824213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823259] Re: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings
Okay, I wonder if this could be because GRUB_CMDLINE_LINUX_DEFAULT was commented out earlier, and there's another entry with the value and we're maybe not catching this appropriately? I will try to reproduce this setup here, with the file attachments we have I should be able to have a closer reproducer than before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823259 Title: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823259] Re: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings
** Changed in: grub2 (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823259 Title: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822007] Re: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP
** Changed in: grub2 (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822007 Title: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1822007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823979] [NEW] Replace use of chown in maintainer scripts
Public bug reported: >From Seth's security review: TL;dr: please see if we could replace the use of chown -R with something else. """ I reviewed heat-dashboard version 1.4.0-0ubuntu1 as checked into cosmic. This shouldn't be considered a full audit but rather a quick gauge of maintainability. heat-dashboard is a web interface to the heat openstack orchestration tool, which can help spin up repeatable instances of guests and networks. - No CVEs in our database - Huge list of build-depends, long enough I'll skip pasting it here - pre/post inst/rm scripts mostly automatically added, but there is a section to "compress the JS and CSS"[1] that also uses a recursive chown. This is dangerous on many kernels. - No init scripts - No systemd units - No dbus services - No setuid - No binaries in PATH - No sudo fragments - No udev rules - There are some tests but I didn't see their results in the logs - No cron jobs - lintian failure in the build logs[2] - No processes spawned - No file IO - Minimal logging, looked fine - No environment use - No privileged functions - Random numbers are generated in Javascript for some reason; using safe sources before falling back to unsafe sources - OpenStack settings OPENSTACK_SSL_NO_VERIFY and OPENSTACK_SSL_CACERT can configure TLS verification and trust root - No temp files - Extensive networking via django; a handful of inspected methods looked properly defensive - No WebKit - No PolicyKit I also found and reported a potential problem with incorrectly escaped URLs: https://storyboard.openstack.org/#!/story/2004454 I can't tell if this would break anything important or not. Security team ACK for promoting heat-dashboard to main. I'd like to see the chown -R removed but don't know what to suggest in its place. Thanks [1]: Note especially the 'chown -R' command; on kernels that follow hardlinks from one uid to another, this can allow horizon to gain ownership of any other files on the filesystem. if [ "$1" = "configure" ] ; then # Compress the JS and CSS with python-compressor and python-lesscpy python /usr/share/openstack-dashboard/manage.py collectstatic --clear --noinput python /usr/share/openstack-dashboard/manage.py compress --force if [ -f '/var/lib/openstack-dashboard/secret-key/.secret_key_store' ]; then rm -f /var/lib/openstack-dashboard/secret-key/.secret_key_store fi if [ -d /var/lib/openstack-dashboard ]; then chown -R horizon:horizon /var/lib/openstack-dashboard fi fi [2]: E: heat-dashboard source: source-is-missing xstatic/pkg/js_yaml/data/js-yaml.js line length is 846 characters (>512) E: heat-dashboard source: source-is-missing heat_dashboard/static/dashboard/project/heat_dashboard/template_generator/js/libs/angular-material.js line length is 1539 characters (>512) W: python-heat-dashboard: priority-extra-is-replaced-by-priority-optional W: python-heat-dashboard: maintainer-script-should-not-use-recursive-chown-or-chmod postinst:13 W: python3-heat-dashboard: priority-extra-is-replaced-by-priority-optional W: python3-heat-dashboard: maintainer-script-should-not-use-recursive-chown-or-chmod postinst:13 W: heat-dashboard-common: priority-extra-is-replaced-by-priority-optional E: heat-dashboard-common: python-package-missing-depends-on-python """ ** Affects: heat-dashboard (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/1823979 Title: Replace use of chown in maintainer scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat-dashboard/+bug/1823979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750576] Re: [MIR] heat-dashboard
Thanks. MIR approved. ** Changed in: heat-dashboard (Ubuntu) Status: Incomplete => 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/1750576 Title: [MIR] heat-dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat-dashboard/+bug/1750576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820195] Re: [MIR] glewlwyd as dependency of mailman3
Sounds like what you want is b). If all we need is the font, then also why is a font bundled with an OAUTH server? For all intents and purposes, it should be more or less easy to split out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820195 Title: [MIR] glewlwyd as dependency of mailman3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glewlwyd/+bug/1820195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775427] Re: [MIR] mailman3 to replace mailman, or drop mailman to universe and off server iso
Setting mailman to Triaged; let's get this off the "New MIRs" list -- it's not new, just not completed yet. mailman3's status nicely captures this. ** Changed in: mailman (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/1775427 Title: [MIR] mailman3 to replace mailman, or drop mailman to universe and off server iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1775427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation
Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821867 Title: network interface is down after post-install reboot of a default disco installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815691] Re: disk not detected on an Intel NUC7i5BNHXF
Given the options shown in firmware and switching to AHCI fixes things as per xnox's comments; this is squarely a "kernel" issue -- one we can't really fix in ubiquity in any case. The kernel side, to support this new RAID or "Intel RST" mode comes with its own set of problems, but I'll let the kernel team deal with that. It's complicated. Reassigning to linux. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu Disco) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815691 Title: disk not detected on an Intel NUC7i5BNHXF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801629] Re: direct dependencies of ubiquity should not be autoremovable
Julian verified this as not reproducing on disco now, with the livecd- rootfs change. Closing the ubiquity task as invalid. ** Changed in: ubiquity (Ubuntu Disco) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801629 Title: direct dependencies of ubiquity should not be autoremovable To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1801629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823259] Re: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings
Could you please run: sudo debconf-show grub-pc sudo debconf-show grub-efi-amd64 I've attempted to reproduce this; by first downgrading to a previous version, changing settings in /etc/default/grub, and proceeding with the upgrade, but no matter what I do, the changes do remain in /etc/default/grub. I've tried simply setting i915.modeset=1, but also reverting again (so i915.modeset=1 is present in debconf to begin with) and adding another entry to be in GRUB_LINUX_CMDLINE_DEFAULT; and also the same with GRUB_LINUX_CMDLINE. As far as I call tell, the update works correctly, so we need to look if there's anything special in the debconf database in case that would affect the behavior. Note for developers: the ucf code is only in grub-pc.postinst or grub- efi-amd64.postinst; so this affects those packages rather than grub(2?)-common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823259 Title: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819014] Re: wpa starts too late causing delay at boot
Verification-done for cosmic: With a netplan config setting up only wireless: network: version: 2 renderer: networkd wifis: wlan0: dhcp4: yes dhcp6: yes access-points: cyphermox.net: password: [redacted] The system appears to come up properly in relatively short time; definitely less than the previously visible 2mn to bring up with wifi. ubuntu@ubuntu:~$ uptime 18:22:31 up 1 min, 1 user, load average: 2.44, 1.08, 0.40 ubuntu@ubuntu:~$ systemd-analyze time Startup finished in 55.346s (userspace) graphical.target reached after 42.780s in userspace ubuntu@ubuntu:~$ systemd-analyze blame | grep wait-online 57ms systemd-networkd-wait-online.service ubuntu@ubuntu:~$ systemd-analyze blame | grep netplan ubuntu@ubuntu:~$ systemd-analyze blame | grep wpa 57ms wpa_supplicant.service ubuntu@ubuntu:~$ 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: eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether b8:27:eb:1b:f5:e2 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:27:eb:4e:a0:b7 brd ff:ff:ff:ff:ff:ff inet 10.3.1.227/22 brd 10.3.3.255 scope global dynamic wlan0 valid_lft 14288sec preferred_lft 14288sec inet6 2001:470:b0cc::78f/128 scope global dynamic noprefixroute valid_lft 28688sec preferred_lft 17888sec inet6 fe80::ba27:ebff:fe4e:a0b7/64 scope link valid_lft forever preferred_lft forever ubuntu@ubuntu:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.2 arm64YAML network configuration abstraction for various backends ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819014 Title: wpa starts too late causing delay at boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1819014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739578] Re: Missing support for WPA2 Enterprise
Verification-done on cosmic: ubuntu@ubuntu:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.2 arm64YAML network configuration abstraction for various backends ubuntu@ubuntu:~$ grep -A 20 wifis /etc/netplan/50-cloud-init.yaml wifis: wlan0: dhcp4: yes dhcp6: yes access-points: cyphermox-secure: auth: key-management: eap method: ttls identity: mtrudel password: *** ubuntu@ubuntu:~$ ip addr show dev wlan0 3: wlan0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether b8:27:eb:4e:a0:b7 brd ff:ff:ff:ff:ff:ff inet 10.3.1.227/22 brd 10.3.3.255 scope global dynamic wlan0 valid_lft 8666sec preferred_lft 8666sec inet6 fe80::ba27:ebff:fe4e:a0b7/64 scope link valid_lft forever preferred_lft forever ubuntu@ubuntu:~$ sudo wpa_cli wpa_cli v2.6 Copyright (c) 2004-2016, Jouni Malinen and contributors This software may be distributed under the terms of the BSD license. See README for more details. Selected interface 'p2p-dev-wlan0' Interactive mode > interface wlan0 Connected to interface 'wlan0. > status bssid=fe:ec:da:3b:dd:85 freq=2437 ssid=cyphermox-secure id=0 mode=station pairwise_cipher=CCMP group_cipher=CCMP key_mgmt=WPA2/IEEE 802.1X/EAP wpa_state=COMPLETED ip_address=10.3.1.227 p2p_device_address=66:48:1c:a0:fa:96 address=b8:27:eb:4e:a0:b7 Supplicant PAE state=AUTHENTICATED suppPortStatus=Authorized EAP state=SUCCESS selectedMethod=21 (EAP-TTLS) eap_tls_version=TLSv1 EAP TLS cipher=ECDHE-RSA-AES256-SHA tls_session_reused=0 EAP-TTLSv0 Phase2 method=EAP-MD5 eap_session_id=15854365a85f10fad12458a1474efdfc2861f716b3e9ddf86bdfc9bfef4f26d5485ca4d04cae14dc97d4265e000507ff4231b34bcb5c7ad02ff16a337cd69c8a74 uuid=04ac78d8-7822-50ee-9519-6a739c6bc7b4 ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739578 Title: Missing support for WPA2 Enterprise To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1739578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739578] Re: Missing support for WPA2 Enterprise
Verification-done on bionic: ubuntu@ubuntu-XPS-13-9350:/etc/netplan$ dpkg -l netplan.io | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--=== ii netplan.io 0.96-0ubuntu0.18.04.2 amd64YAML network configuration abstraction for various backends ubuntu@ubuntu-XPS-13-9350:/etc/netplan$ cat netplan.yaml network: version: 2 renderer: networkd wifis: wlp58s0: access-points: cyphermox-secure: auth: key-management: eap password: ** method: peap identity: mtrudel dhcp4: yes ubuntu@ubuntu-XPS-13-9350:/etc/netplan$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 wlp58s0 wlan routableconfigured 2 links listed. ubuntu@ubuntu-XPS-13-9350:/etc/netplan$ sudo wpa_cli [...] > interface wlp58s0 Connected to interface 'wlp58s0. > status bssid=fe:ec:da:3c:dd:85 freq=5785 ssid=cyphermox-secure id=0 mode=station pairwise_cipher=CCMP group_cipher=CCMP key_mgmt=WPA2/IEEE 802.1X/EAP wpa_state=COMPLETED ip_address=10.3.1.222 p2p_device_address=44:85:00:1d:8f:e0 address=44:85:00:1d:8f:df Supplicant PAE state=AUTHENTICATED suppPortStatus=Authorized EAP state=SUCCESS selectedMethod=25 (EAP-PEAP) eap_tls_version=TLSv1 EAP TLS cipher=ECDHE-RSA-AES256-SHA tls_session_reused=0 EAP-PEAPv0 Phase2 method=MSCHAPV2 eap_session_id=19f0e2954987468e732c6c9f2c09005ac6dff6ea8614d1abc82a03824d92cc9b625ca3b58a6cd56025e2bee8cd856bd57cff338e54150cace810df93d0b7a4 uuid=16d5a610-234c-5373-945a-25b6dcd082fc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739578 Title: Missing support for WPA2 Enterprise To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1739578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799487] Re: Support for sit (ipv6) tunnels
Verification done for cosmic: ubuntu@test-netplan-cosmic:~$ cat /etc/netplan/50-cloud-init.yaml | grep -A 10 'tunnels' tunnels: he-ipv6: mode: sit remote: xxx.xxx.xxx.xxx local: xxx.xxx.xxx.xxx addresses: - "2001:xxx:xx:xxx::2/64" gateway6: "2001:xxx:xx:xxx::1" ubuntu@test-netplan-cosmic:~$ ip -6 addr 1: lo: mtu 65536 state UNKNOWN qlen 1000 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 state UP qlen 1000 inet6 fe80::f816:3eff:fed1:a358/64 scope link valid_lft forever preferred_lft forever 4: he-ipv6@NONE: mtu 1480 state UNKNOWN qlen 1000 inet6 2001:xxx:xx:xxx::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::3627:b7f0/64 scope link valid_lft forever preferred_lft forever ubuntu@test-netplan-cosmic:~$ ping6 2620:119:35::35 PING 2620:119:35::35(2620:119:35::35) 56 data bytes 64 bytes from 2620:119:35::35: icmp_seq=1 ttl=61 time=19.5 ms 64 bytes from 2620:119:35::35: icmp_seq=2 ttl=61 time=17.4 ms 64 bytes from 2620:119:35::35: icmp_seq=3 ttl=61 time=17.1 ms 64 bytes from 2620:119:35::35: icmp_seq=4 ttl=61 time=17.3 ms ^C --- 2620:119:35::35 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 8ms rtt min/avg/max/mdev = 17.129/17.821/19.477/0.964 ms ubuntu@test-netplan-cosmic:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.2 amd64YAML network configuration abstraction for various backends ubuntu@test-netplan-cosmic:~$ ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799487 Title: Support for sit (ipv6) tunnels To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1799487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817660] Re: test_terminal.TestTerminal tests fail when run a second time
Verification-done on bionic for netplan.io: netplan.io: Installed: 0.96-0ubuntu0.18.04.2 Candidate: 0.96-0ubuntu0.18.04.2 Version table: *** 0.96-0ubuntu0.18.04.2 500 -1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.40.1~18.04.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 0.36.1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Retrieving the source for netplan.io (apt-get source netplan.io); and running 'make check' twice; the tests all pass whereas on previous source (for 0.40.1~18.04.4) it would repeatably fail the second time 'make check' is run. ** 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/1817660 Title: test_terminal.TestTerminal tests fail when run a second time To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817660] Re: test_terminal.TestTerminal tests fail when run a second time
Verification-done on cosmic for netplan.io: ubuntu@civil-eft:~$ apt-cache policy netplan.io netplan.io: Installed: 0.96-0ubuntu0.18.10.2 Candidate: 0.96-0ubuntu0.18.10.2 Version table: *** 0.96-0ubuntu0.18.10.2 500 -1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.40.2.2 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 0.40.2 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages Retrieving the source for netplan.io (apt-get source netplan.io); and running 'make check' twice; the tests all pass whereas on previous source (0.40.2.2) it would repeatably fail the second time 'make check' is run. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817660 Title: test_terminal.TestTerminal tests fail when run a second time To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817655] Re: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco)
Verification-done for bionic: Changing the renderer to NetworkManager still leads to a working system with live connections, even with the NetworkManager files now having a .nmconnection extension: ubuntu@just-boa:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.04.2 amd64YAML network configuration abstraction for various backends ubuntu@just-boa:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp2s1 ether routableunmanaged 3 enp2s2 ether degradedunmanaged 3 links listed. ubuntu@just-boa:~$ nmcli enp2s1: connected to netplan-enp2s1 "Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (QEMU Virtual Machine)" ethernet (8139cp), 52:54:00:BC:B0:18, hw, mtu 1500 ip4 default, ip6 default inet4 10.3.21.29/20 route4 10.3.16.0/20 route4 0.0.0.0/0 inet6 2001:470:b171::5/48 inet6 fe80::5054:ff:febc:b018/64 route6 ff00::/8 route6 2001:470:b171::/48 route6 fe80::/64 route6 ::/0 enp2s2: connected to netplan-enp2s2 "Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (QEMU Virtual Machine)" ethernet (8139cp), 52:54:00:59:A3:52, hw, mtu 1500 inet4 169.254.41.37/16 route4 224.0.0.0/4 route4 169.254.0.0/16 inet6 fe80::5054:ff:fe59:a352/64 route6 ff00::/8 route6 fe80::/64 lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 DNS configuration: servers: 10.3.21.25 149.56.20.136 interface: enp2s1 Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles. Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details. ubuntu@just-boa:~$ sudo ls -l /run/NetworkManager/system-connections/ total 8 -rw--- 1 root root 353 Apr 2 16:18 netplan-enp2s1.nmconnection -rw--- 1 root root 168 Apr 2 16:18 netplan-enp2s2.nmconnection ** 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/1817655 Title: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817655] Re: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco)
Verification-done for cosmic: With the changes and NetworkManager connection files now having a .nmconnection, the network still comes up and the system is still reachable, with the renderer value in netplan yaml changed to 'NetworkManager'. ubuntu@civil-eft:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.2 amd64YAML network configuration abstraction for various backends ubuntu@civil-eft:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 ens4 ether routableunmanaged 2 links listed. ubuntu@civil-eft:~$ nmcli | cat ens4: connected to netplan-ens4 "Red Hat Virtio" ethernet (virtio_net), 52:54:00:02:E0:E0, hw, mtu 1500 ip4 default, ip6 default inet4 10.3.21.28/20 route4 10.3.16.0/20 route4 0.0.0.0/0 inet6 2001:470:b171::4/48 inet6 fe80::5054:ff:fe02:e0e0/64 route6 2001:470:b171::/48 route6 ff00::/8 route6 fe80::/64 route6 ::/0 lo: unmanaged "lo" loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536 DNS configuration: servers: 149.56.20.136 domains: cloud.cyphermox.net interface: ens4 servers: 2001:470:b171::1 domains: cloud.cyphermox.net interface: ens4 Use "nmcli device show" to get complete information about known devices and "nmcli connection show" to get an overview on active connection profiles. Consult nmcli(1) and nmcli-examples(5) manual pages for complete usage details. ubuntu@civil-eft:~$ sudo ls -l /run/NetworkManager/system-connections/ total 4 -rw--- 1 root root 360 Apr 2 16:18 netplan-ens4.nmconnection ubuntu@civil-eft:~$ ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817655 Title: NetworkManager renderer broken on NM version 1.15.2 or later (Ubuntu 19.04 Disco) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed
Setting back to verification-done: Alfonso already verified this same SRU; no changes with the new revision in -proposed. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811868 Title: networkd/NetworkManager are not re-started on netplan apply when config files are removed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800669] Re: Various documentation fixes
Resetting to verification-done since these are for documentation changes with no difference in the new revision in -proposed. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800669 Title: Various documentation fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1800669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800668] Re: Clarify MAC and MTU setting requirements
This hasn't changed with the new revision in -proposed; re-setting to verification-done. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800668 Title: Clarify MAC and MTU setting requirements To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1800668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800670] Re: Improve error reporting to give clearer messages and context
Setting back to verification-done; this is still verified for bionic and cosmic (no change with new revision in -proposed). ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800670 Title: Improve error reporting to give clearer messages and context To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1800670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802322] Re: [regression] netplan apply is not idempotent and fails trying to rename a bond member interface
This hasn't changed in bionic and cosmic; previously released SRU which is again included in the changelog for this backport. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802322 Title: [regression] netplan apply is not idempotent and fails trying to rename a bond member interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1802322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804861] Re: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied
Setting verification-done tags for bionic and cosmic missing after verification in comment #27. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804861 Title: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1804861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770082] Re: systemd-networkd not renaming devices on boot
No need to re-test these; it's already been included in bionic/cosmic and bug comments are a side-effect of the changelogs for the upload with this backport. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799487] Re: Support for sit (ipv6) tunnels
Still verification-done on bionic; this hasn't changed with the new revision in -proposed. ** 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/1799487 Title: Support for sit (ipv6) tunnels To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1799487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub
Verification-done for cosmic: ubuntu@noted-fish:~$ dpkg -l grub\* | grep ii ii grub-common 2.02+dfsg1-5ubuntu8.3 amd64GRand Unified Bootloader (common files) ii grub-efi-amd642.02+dfsg1-5ubuntu8.3 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin2.02+dfsg1-5ubuntu8.3 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) ii grub-efi-amd64-signed 1.110.3+2.02+dfsg1-5ubuntu8.3 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed) ii grub2-common 2.02+dfsg1-5ubuntu8.3 amd64GRand Unified Bootloader (common files for version 2) As for bionic; with the new version, there are no conffile prompts for the same grub.cfg manipulations that would have normally resulted from a prompt. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic ** Description changed: [Impact] All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot) [Test case] == Upgrade prompting == 0) Install Ubuntu - 1) Modify /etc/default/grub.cfg options - 2) Copy /etc/default/grub.cfg to /var/lib/grub/ucf/grub.previous - 3) Update grub to the new package + 1) Modify /usr/share/grub/default/grub options + 2) Run 'sudo apt install --reinstall grub-pc ((or grub-efi-amd64)) Verify that the user IS prompted to approve grub.cfg changes due to changes in the template coming from the process. == User-specified changes == 0) Install Ubuntu 1) Modify /etc/default/grub.cfg options 2) Update grub to the new package Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg. == Post-deployment upgrades on MAAS-controlled system == 0) Deploy a system using MAAS 1) Update grub to the new package Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg. [Regression potential] Pay attention to prompting behavior on grub updates as well as any failure to update the grub* packages. Prompting should be limited to the cases where the grub2 source package has changed the contents for the default provided grub.cfg; and on MAAS-controlled systems, the local modifications have changed in some way from the original copy of grub2 installed on the system. --- Binary package hint: grub-pc This concerns grub-pc 1.98-1ubuntu5 in Lucid beta1 (upgrading from 1.98-1ubuntu4). I have a locally modified /etc/default/grub file. When I upgraded to this version of grub-pc, I got the "A new version of configuration file /etc/default/grub is available, but the version installed currently has been locally modified. What do you want to do about modified configuration file grub?" question. The problem is, when I look at the diff, it just shows the differences between my file, and the way it was originally. In other words, the upgraded package does not include any updates to this file; its "pristine" copy of /etc/default/grub is the same as the previous version's. So I shouldn't even be getting a conffile prompt in the first place---as far as the administrator is concerned, nothing has changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787630] Re: [FFe] Include HTTP support in pre-build GRUB module
Thanks Blake! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787630 Title: [FFe] Include HTTP support in pre-build GRUB module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1787630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub
Verification-done on bionic: ubuntu@brave-elf:~$ dpkg -l grub\* | grep ii ii grub-common 2.02-2ubuntu8.13 amd64GRand Unified Bootloader (common files) ii grub-gfxpayload-lists 0.7 amd64GRUB gfxpayload blacklist ii grub-pc 2.02-2ubuntu8.13 amd64GRand Unified Bootloader, version 2 (PC/BIOS version) ii grub-pc-bin 2.02-2ubuntu8.13 amd64GRand Unified Bootloader, version 2 (PC/BIOS binaries) ii grub2-common 2.02-2ubuntu8.13 amd64GRand Unified Bootloader (common files for version 2) With the new version, the changes that previously triggered a conffile prompt now no longer do; using changes made manually to the grub.cfg file or using the reproducer script provided by Scott. ** 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/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820898] Re: grub in xenial fails to read pc-linux 4.15 kernel snap
Verification-done on xenial: ubuntu@profound-donkey:~$ snap download pc-kernel --channel 18 Fetching snap "pc-kernel" Fetching assertions for "pc-kernel" Install the snap with: snap ack pc-kernel_192.assert snap install pc-kernel_192.snap ubuntu@profound-donkey:~$ grub-fstest pc-kernel_192.snap crc /vmlinuz 441609b6 ubuntu@profound-donkey:~$ dpkg -l grub\* | grep ii ii grub-common 2.02~beta2-36ubuntu3.21 amd64GRand Unified Bootloader (common files) ii grub-efi-amd642.02~beta2-36ubuntu3.21 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin2.02~beta2-36ubuntu3.21 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) ii grub-efi-amd64-signed 1.66.21+2.02~beta2-36ubuntu3.21 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed) ii grub2-common 2.02~beta2-36ubuntu3.21 amd64GRand Unified Bootloader (common files for version 2) grub behaves as expected given the grub-fstest test case provided. ** 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/1820898 Title: grub in xenial fails to read pc-linux 4.15 kernel snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1820898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401532] Re: GRUB's Secure Boot implementation loads unsigned kernel without warning
Verification-done on trusty: ubuntu@dashing-moccasin:~$ apt-cache policy grub-efi-amd64-signed grub-efi-amd64-signed: Installed: 1.34.20+2.02~beta2-9ubuntu1.17 Candidate: 1.34.20+2.02~beta2-9ubuntu1.17 Package pin: 1.34.20+2.02~beta2-9ubuntu1.17 Version table: *** 1.34.20+2.02~beta2-9ubuntu1.17 500 -1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.34.18+2.02~beta2-9ubuntu1.16 500 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.34.7+2.02~beta2-9ubuntu1.6 500 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.34+2.02~beta2-9 500 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ubuntu@dashing-moccasin:~$ apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.02~beta2-9ubuntu1.17 Candidate: 2.02~beta2-9ubuntu1.17 Package pin: 2.02~beta2-9ubuntu1.17 Version table: *** 2.02~beta2-9ubuntu1.17 500 -1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.02~beta2-9ubuntu1.16 500 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 2.02~beta2-9ubuntu1.6 500 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.02~beta2-9 500 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Verified that now the kernel signature is correctly enforced by grub, and if no kernel is signed / signed by a trusted key, the upgrade will correctly be failed to avoid leaving the system unbootable. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401532 Title: GRUB's Secure Boot implementation loads unsigned kernel without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789918] Re: grub2 signed kernel enforcement doesn't check on upgrade that signatures are from trusted keys
Verification-done on trusty: ubuntu@dashing-moccasin:~$ apt-cache policy grub-efi-amd64-signed grub-efi-amd64-signed: Installed: 1.34.20+2.02~beta2-9ubuntu1.17 Candidate: 1.34.20+2.02~beta2-9ubuntu1.17 Package pin: 1.34.20+2.02~beta2-9ubuntu1.17 Version table: *** 1.34.20+2.02~beta2-9ubuntu1.17 500 -1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.34.18+2.02~beta2-9ubuntu1.16 500 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 1.34.7+2.02~beta2-9ubuntu1.6 500 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 1.34+2.02~beta2-9 500 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ubuntu@dashing-moccasin:~$ apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.02~beta2-9ubuntu1.17 Candidate: 2.02~beta2-9ubuntu1.17 Package pin: 2.02~beta2-9ubuntu1.17 Version table: *** 2.02~beta2-9ubuntu1.17 500 -1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.02~beta2-9ubuntu1.16 500 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 2.02~beta2-9ubuntu1.6 500 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 2.02~beta2-9 500 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Verified that now the kernel signature is correctly enforced by grub, and if no kernel is signed / signed by a trusted key, the upgrade will correctly be failed to avoid leaving the system unbootable. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789918 Title: grub2 signed kernel enforcement doesn't check on upgrade that signatures are from trusted keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1789918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818929] Re: shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1) package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: sub-processo script
** Description changed: + [Impact] + Upgrades with shim-signed when only partial upgrades are done. + + [Test case] + 1) Install new system, with no updates + 2) Run 'sudo apt-get update' + 3) Run 'sudo apt-get install shim-signed' + 4) Verify that sbsigntool is also updated to the new version. + + [Regression potential] + Minimal; this simply adds a prerequisite package version for running 'kmodsign' on systems when installing DKMS modules that need to be self-signed. If sbsigntool is already installed and at the right version, or if kmodsign is not required, this makes no difference on the system. + + --- + + Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 1 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Mar 6 21:18:20 2019 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-20160624-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 EFITables: - Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: efi: EFI v2.40 by American Megatrends - Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: efi: ACPI=0xa8603000 ACPI 2.0=0xa8603000 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0xa92a9018 - Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: esrt: Reserving ESRT space from 0xa92a9018 to 0xa92a9050. - Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: Secure boot MOKSBState disabled + Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: efi: EFI v2.40 by American Megatrends + Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: efi: ACPI=0xa8603000 ACPI 2.0=0xa8603000 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0xa92a9018 + Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: esrt: Reserving ESRT space from 0xa92a9018 to 0xa92a9050. + Mar 06 20:22:54 taina-Inspiron-15-3567 kernel: Secure boot MOKSBState disabled ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 127 InstallationDate: Installed on 2018-11-22 (104 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MokSBStateRT: 7 0 0 0 1 RelatedPackageVersions: - dpkg 1.18.4ubuntu1 - apt 1.2.26 + dpkg 1.18.4ubuntu1 + apt 1.2.26 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 127 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818929 Title: shim-signed: missing versioned dep on sbsigntool (>= 0.6-0ubuntu10.1) package shim-signed 1.33.1~16.04.4+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1818929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401532] Re: GRUB's Secure Boot implementation loads unsigned kernel without warning
Verification-failed on trusty: ii grub-common 2.02~beta2-9ubuntu1.17 amd64GRand Unified Bootloader (common files) ii grub-efi-amd64 2.02~beta2-9ubuntu1.17 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin 2.02~beta2-9ubuntu1.17 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) ii grub-efi-amd64-signed 1.34.19+2.02~beta2-9ubuntu1.17 amd64GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed) ii grub-legacy-ec2 0.7.5-0ubuntu1.23 all Handles update-grub for ec2 instances ii grub-pc-bin 2.02~beta2-9ubuntu1.17 amd64GRand Unified Bootloader, version 2 (PC/BIOS binaries) ii grub2-common2.02~beta2-9ubuntu1.17 amd64GRand Unified Bootloader (common files for version 2) Kernel signatures are correctly enforced, but a postinst check is missing in grub2-signed to check signatures before applying the next update (missing in grub2-signed 1.34.19) ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty ** Tags removed: verification-done-trusty ** Tags added: verification-failed-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401532 Title: GRUB's Secure Boot implementation loads unsigned kernel without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789918] Re: grub2 signed kernel enforcement doesn't check on upgrade that signatures are from trusted keys
Verification-done on trusty: ii grub-common 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader (common files) ii grub-efi-amd64 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) ii grub-efi-amd64-signed 1.34.19+2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed) ii grub-legacy-ec2 0.7.5-0ubuntu1.23 all Handles update-grub for ec2 instances ii grub-pc-bin 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader, version 2 (PC/BIOS binaries) ii grub2-common 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader (common files for version 2) Kernel signatures are correctly enforced, but a postinst check is missing in grub2-signed to check signatures before applying the next update (missing in grub2-signed 1.34.19) ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789918 Title: grub2 signed kernel enforcement doesn't check on upgrade that signatures are from trusted keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1789918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822007] Re: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP
As a first step I'd look into whether grub is able to correctly get an IP from DHCP. I wonder if the client class string confuses it. Could you please take packet captures of the boot attempt? We could then have a look at the whole thing and compare with grub code to see what happens? ** Changed in: grub2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: grub2 (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/1822007 Title: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1822007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807273] Re: netplan not respecting mtu
Verification-done for cosmic, using netplan.io 0.96-0ubuntu0.18.10.2:
As for the above test, I set up a new AWS instance (t2.micro); and
applied the configuration (first trying to just set mtu: 1500; then
using dhcp4-overrides: { use-mtu: false }).
ubuntu@ip-172-30-0-81:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.10.2 amd64YAML network
configuration abstraction for various backends
ubuntu@ip-172-30-0-81:~$ sudo netplan --debug apply
** (generate:2737): DEBUG: 16:39:55.688: Processing input file
/etc/netplan/50-cloud-init.yaml..
** (generate:2737): DEBUG: 16:39:55.689: starting new processing pass
** (generate:2737): DEBUG: 16:39:55.689: Generating output files..
** (generate:2737): DEBUG: 16:39:55.689: NetworkManager: definition eth0 is not
for us (backend 1)
(generate:2737): GLib-DEBUG: 16:39:55.689: posix_spawn avoided (fd close
requested)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
eth0:
dhcp4: true
dhcp4-overrides:
use-mtu: false
match:
macaddress: 06:9d:85:76:e2:b2
mtu: 1500
set-name: eth0
vlans: {}
wifis: {}
DEBUG:Skipping non-physical interface: lo
DEBUG:device eth0 operstate is up, not changing
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for eth0
ubuntu@ip-172-30-0-81:~$ 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 1500 qdisc fq_codel state UP
mode DEFAULT group default qlen 1000
link/ether 06:9d:85:76:e2:b2 brd ff:ff:ff:ff:ff:ff
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807273
Title:
netplan not respecting mtu
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1807273/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807273] Re: netplan not respecting mtu
Verification-done on bionic with netplan.io 0.96-0ubuntu0.18.04.2:
I set up a new AWS instance (t2.micro in this case); and applied a
similar setup (attempting to just set mtu: 1500, that doesn't work, then
using the new dhcp4-overrides feature). Forcing UseMTU=false makes the
MTU apply to the interface.
ubuntu@ip-172-30-0-14:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.04.2 amd64YAML network
configuration abstraction for various backends
ubuntu@ip-172-30-0-14:~$ sudo netplan --debug apply
** (generate:2138): DEBUG: 16:30:02.609: Processing input file
/etc/netplan/50-cloud-init.yaml..
** (generate:2138): DEBUG: 16:30:02.609: starting new processing pass
** (generate:2138): DEBUG: 16:30:02.609: Generating output files..
** (generate:2138): DEBUG: 16:30:02.609: NetworkManager: definition eth0 is not
for us (backend 1)
DEBUG:netplan generated networkd configuration changed, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:eth0 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
eth0:
dhcp4: true
dhcp4-overrides:
use-mtu: false
match:
macaddress: 06:84:40:e0:fd:7c
mtu: 1500
set-name: eth0
vlans: {}
wifis: {}
DEBUG:Skipping non-physical interface: lo
DEBUG:device eth0 operstate is up, not changing
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for eth0
ubuntu@ip-172-30-0-14:~$ 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 1500 qdisc fq_codel state UP
mode DEFAULT group default qlen 1000
link/ether 06:84:40:e0:fd:7c brd ff:ff:ff:ff:ff:ff
** 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/1807273
Title:
netplan not respecting mtu
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1807273/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804861] Re: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied
Verification done with bionic and cosmic; using the following config: network: version: 2 ethernets: ens4: match: macaddress: 52:54:00:ea:e6:7a mtu: 9000 ens7: match: macaddress: 52:54:00:d7:62:4c mtu: 9000 bonds: bond0: interfaces: - ens4 - ens7 mtu: 9000 addresses: - 10.3.16.3/20 gateway4: 10.3.16.1 vlans: bond0.804: link: bond0 id: 804 addresses: - 10.99.99.24/24 mtu: 1500 bond0.8: link: bond0 id: 8 addresses: - 10.8.99.24/24 mtu: 1500 ubuntu@apt-snail:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.04.2 amd64YAML network configuration abstraction for various backends ubuntu@apt-snail:~$ 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: ens4: mtu 9000 qdisc fq_codel master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 36:72:e5:93:2d:bb brd ff:ff:ff:ff:ff:ff 3: ens7: mtu 9000 qdisc fq_codel master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 36:72:e5:93:2d:bb brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 36:72:e5:93:2d:bb brd ff:ff:ff:ff:ff:ff 5: bond0.804@bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 36:72:e5:93:2d:bb brd ff:ff:ff:ff:ff:ff 6: bond0.8@bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 36:72:e5:93:2d:bb brd ff:ff:ff:ff:ff:ff ubuntu@humble-cattle:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.2 amd64YAML network configuration abstraction for various backends ubuntu@humble-cattle:~$ 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: ens4: mtu 9000 qdisc fq_codel master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 62:61:81:9d:a9:6d brd ff:ff:ff:ff:ff:ff 3: ens7: mtu 9000 qdisc fq_codel master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 62:61:81:9d:a9:6d brd ff:ff:ff:ff:ff:ff 4: bond0: mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 62:61:81:9d:a9:6d brd ff:ff:ff:ff:ff:ff 5: bond0.8@bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 62:61:81:9d:a9:6d brd ff:ff:ff:ff:ff:ff 6: bond0.804@bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 62:61:81:9d:a9:6d brd ff:ff:ff:ff:ff:ff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804861 Title: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1804861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750392] Re: Cannot enable IPv6 privacy extensions
Verification done for both bionic and cosmic: ubuntu@test-netplan-bionic:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.04.2 amd64YAML network configuration abstraction for various backends ubuntu@test-netplan-bionic:~$ sudo sysctl -a | grep tempaddr sysctl: reading key "net.ipv6.conf.all.stable_secret" net.ipv6.conf.all.use_tempaddr = 0 sysctl: reading key "net.ipv6.conf.default.stable_secret" net.ipv6.conf.default.use_tempaddr = 0 sysctl: reading key "net.ipv6.conf.ens3.stable_secret" net.ipv6.conf.ens3.use_tempaddr = 2 sysctl: reading key "net.ipv6.conf.lo.stable_secret" net.ipv6.conf.lo.use_tempaddr = -1 ubuntu@test-netplan-cosmic:~$ sudo dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.2 amd64YAML network configuration abstraction for various backends ubuntu@test-netplan-cosmic:~$ sudo sysctl -a | grep tempaddr net.ipv6.conf.all.use_tempaddr = 0 net.ipv6.conf.default.use_tempaddr = 0 net.ipv6.conf.ens3.use_tempaddr = 2 net.ipv6.conf.lo.use_tempaddr = -1 ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic ** 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/1750392 Title: Cannot enable IPv6 privacy extensions To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1750392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
Yes, that does explain it. /run/netplan/.yaml is written automatically by initramfs- tools when booting with a remote root (ie. iscsi); so this does check out: for example, 'critical' is required in that case, otherwise as soon as someone runs 'netplan apply' the network will go down and you might have filesystem errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Ubuntu-QC] Ubuntu Dual boot EFI SSD
On Wed, Mar 6, 2019 at 9:57 PM Daniel Ducharme wrote: > > Bonsoir, > > Je vous reviens parce que j'ai tenté une approche... mais je crains > d'aller plus loin. > [...] > Est-ce que l'un d'entre vous a une solution ? Il semblerait que mon > SSD soit en "legacy inherited", mais je ne sais pas trop ce que ça > veut dire.. > Bonjour Daniel, Il vous faudrait entrer dans le programme de configuration du micrologiciel (BIOS) (appuyer sur Entrée au démarrage, quand le logo Lenovo apparaît, puis démarrer l'utilitaire Setup en appuyant sur F1). Prenez note de la configuration initiale, car vous pouvez changer ces options sans aucun effet sur ce qui est sur le disque dur: en d'autres mots, si ca ne fonctionne pas, vous pouvez remettre les options comme elles était et Windows fonctionnera toujours... Vous pourrez ensuite changer le mode dans la section "Startup". Il y a là une option "UEFI/Legacy Boot" que vous voulez probablement voir à "UEFI Boot Only". De plus, vous voudrez sans doute changer "CSM Support" à "No". Windows devrait pouvoir démarrer quand même (s'il est bien installé en UEFI), et une clé Ubuntu fonctionnerait également pour commencer l'installation. Pour ce qui est de "legacy inherited", je n'ai jamais vu ce genre d'option dans le micrologiciel de Lenovo. D'où ca vient? Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu...@gmail.com 4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1 -- Ubuntu-quebec mailing list Ubuntu-quebec@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-quebec
[Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation
** Description changed: + [Impact] + Minimal installs using netplan to configure the network. + + [Test case] + 1) Install Ubuntu minimal server / cloud image + 2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary. + 3) Run 'sudo netplan apply'. Verify that the network comes up correctly. + 4) Reboot. + 5) Verify that the network comes up properly. + + [Regression potential] + Minimal; this reverts changes in a package that was never released to -updates, only available as SRU in -proposed and on the devel release. This only applies to the order in which systemd-networkd is enabled when used as a renderer for netplan configuration, to start in multi-user.target instead of the "correct", but inefficient "network-online.target" as the latter may not be depended upon in minimal installs. + + --- + After doing a default disco installation on s390x using the beta ISO image aka daily from March 26th and the post-install reboot the system restarts aka reipls (in z/VM in this case) but the interface is not brought up. Hence no remote connections are possible. The ip cmd shows: - ip a + ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group defaul - t 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 + t 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: enc600: mtu 1500 qdisc noop state DOWN group default ql - en 1000 - link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff + en 1000 + link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff The netplan yaml file looks fine: - cat /etc/netplan/*.yaml + cat /etc/netplan/*.yaml # This file describes the network interfaces available on your system - # For more information, see netplan(5). - network: - version: 2 - renderer: networkd - ethernets: - enc600: - addresses: ¬ 10.245.236.27/24 | - gateway4: 10.245.236.1 - nameservers: - search: ¬ canonical.com | - addresses: - - "10.245.236.1" + # For more information, see netplan(5). + network: + version: 2 + renderer: networkd + ethernets: + enc600: + addresses: ¬ 10.245.236.27/24 | + gateway4: 10.245.236.1 + nameservers: + search: ¬ canonical.com | + addresses: + - "10.245.236.1" Using ip to bring the interface up doesn't help: buntu§hwe0007:ß$ sudo ip link set enc600 up sudo ip link set enc600 up ubuntu§hwe0007:ß$ ip addr show enc600 - ip addr show enc600 + ip addr show enc600 2: enc600: mtu 1500 qdisc fq_codel state UP gr - oup default qlen 1000 - link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff - inet6 fe80::28:bff:fe00:15/64 scope link -valid_lft forever preferred_lft forever + oup default qlen 1000 + link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff + inet6 fe80::28:bff:fe00:15/64 scope link + valid_lft forever preferred_lft forever ubuntu§hwe0007:ß$ But finally executing netplan apply does help: sudo netplan apply --dryrun - sudo netplan apply --dryrun + sudo netplan apply --dryrun ubuntu§hwe0007:ß$ sudo netplan apply - sudo netplan apply + sudo netplan apply ubuntu§hwe0007:ß$ ip addr show enc600 - ip addr show enc600 + ip addr show enc600 2: enc600: mtu 1500 qdisc fq_codel state UP gr - oup default qlen 1000 - link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff - inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600 -valid_lft forever preferred_lft forever - inet6 fe80::28:bff:fe00:15/64 scope link -valid_lft forever preferred_lft forever - ubuntu§hwe0007:ß$ + oup default qlen 1000 + link/ether 02:28:0b:00:00:15 brd ff:ff:ff:ff:ff:ff + inet 10.245.236.27/24 brd 10.245.236.255 scope global enc600 + valid_lft forever preferred_lft forever + inet6 fe80::28:bff:fe00:15/64 scope link + valid_lft forever preferred_lft forever + ubuntu§hwe0007:ß$ (Sorry for the partly duplicate lines and some strange characters, but this is due to the fact that I copied the output from the console that requires a 3270 terminal emulation) ** 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/1821867 Title: network interface is down after post-install reboot of a default disco installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions -- ubuntu-bugs
[Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
I also forgot to mention another entry I see in some of the configs:
set-name: ens3
If you do not need to explicitly rename the interfaces yourself to a
different name, I would avoid setting this at all. It *may* be being set
automatically by cloud-init (if that's in use, but the configs provided
do not look like generated configs from cloud-init).
I'm curious to see how this behaves with the most simple netplan
configuration possible; if you still see renaming issues in that case
from the kernel -- as those would be renaming done completely outside of
netplan and further direct our debugging to systemd-network / systemd-
udev instead.
In short; how much of the issues are you seeing when the only netplan
config on the systems is /etc/netplan/01-netcfg.yaml (the one generated
by debian-installer)?
Judging from the original description, I'd say you still get renaming
issues, specifically any new device with the MAC is attempted to be
named "ens3" because of the udev rules:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="ba:fb:9f:12:2f:02", NAME="ens3"
This part should not vary whether there are statically assigned
addresses or not; but it's also questionable whether or not it is useful
to write it in the first place: systemd-udev should already be following
ifnames policy to name the device appropriately (this should be true in
all scenarios, this is only marginally useful for /renaming/ (when set-
name: is specified) or setting MTU and such low-level options).
Finally, could you please also provide us with the output of:
sudo udevadm info /sys/class/net/ens4 (or rename4, depending on how it ends up
being named).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820929
Title:
netplan should consider adding more udev attribute for exact matching
of failover 3-netdev interfaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
All of these values should be coming directly from the netplan YAML. Are all of these options required? I see: match: macaddress: # Do you need to match the interface in this case? Is it sufficient to match by name if only ens3 is being configured? Also: dhcp-identifier: mac # This should only be required for clients who do not have control over their DHCP server, and thus can't use the DUID to set reservations and instead must use the MAC address to get a "static" IP from DHCP. I would recommend not setting this if it can be avoided. Also: critical: true # This is only required for systems booting off the network to reach their root filesystem. It will control whether the DHCP IP is released / regained when systemd-networkd restarts. Again, I would recommend not setting this if it's not required; DHCP leases lifetimes should ensure you will get the same address again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821867] Re: network interface is down after post-install reboot of a default disco installation
This seems quite likely to be an issue with netplan; I've had a similar report on UC18; where systemd-networkd isn't started. Turns out netplan moved the enablement of systemd-netwrokd to network- online.target; but unfortunately there may be no service or target depending on that. I'll revert the change to put systemd-networkd back under multi-user.target. ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => Critical ** Changed in: netplan.io (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/1821867 Title: network interface is down after post-install reboot of a default disco installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1821867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819761] Re: [MIR] containerd
I see no obvious issues with the package, but it's huge and would benefit the Security Team reviewing it as well. ** Changed in: containerd (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819761 Title: [MIR] containerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1819761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565950] Re: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled
There currently are no plans to that effect. For now; shipping in the devel series, and the installer does not set up any partitioning automatically that would make use of this. It's "only" a convenience for people who do their own partitioning, which requires some prior knowledge to set this up correctly. I'm not against having this landed as stable updates for bionic and cosmic; but it would greatly help if people signed up to do the SRU verification, as this is often what is the bottleneck for releasing updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565950 Title: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1565950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767527] Re: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab
** Changed in: cryptsetup Assignee: TJ (tj) => (unassigned) ** Changed in: cryptsetup (Ubuntu) Assignee: TJ (tj) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767527 Title: [18.04] Installation boot failure. WARNING: invalid line in /etc/crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1767527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800670] Re: Improve error reporting to give clearer messages and context
Verification-done for both bionic and cosmic: ubuntu@humble-cod:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.04.1 amd64 YAML network configuration abstraction for various backends ubuntu@superb-ram:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.1 amd64 YAML network configuration abstraction for various backends Errors are reported exactly as specified in the test cases here for each of the test cases. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800670 Title: Improve error reporting to give clearer messages and context To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1800670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800668] Re: Clarify MAC and MTU setting requirements
Verification-done for both bionic and cosmic: ubuntu@humble-cod:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.04.1 amd64YAML network configuration abstraction for various backends ubuntu@superb-ram:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.1 amd64YAML network configuration abstraction for various backends Opening the netplan manpage, in under the 'mtu' section it is now clearly stated: """ Note: This will not work reliably for devices matched by name only and rendered by networkd, due to interactions with de‐ vice renaming in udev. Match devices by MAC when setting MTU. """ ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800668 Title: Clarify MAC and MTU setting requirements To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1800668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800669] Re: Various documentation fixes
Verification-done for both bionic and cosmic: ubuntu@humble-cod:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.04.1 amd64 YAML network configuration abstraction for various backends ubuntu@superb-ram:~$ dpkg -l netplan.io | grep ii ii netplan.io 0.96-0ubuntu0.18.10.1 amd64 YAML network configuration abstraction for various backends Opening the netplan manpage: - ipv6-privacy is defined (bool, with explanation of what it does) - DHCP Overrides is its own section - MTU MAC matching requirement is listed - 'renderer: networkd' is shown with an accompanying comment ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800669 Title: Various documentation fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1800669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799487] Re: Support for sit (ipv6) tunnels
Verification done on bionic with netplan.io: mtrudel@daikoku:~$ dpkg -l netplan.io | more Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--=== ii netplan.io 0.96-0ubuntu0.18.04.1 amd64YAML network configuration abstraction for various backends Setting up an IPv6 sit tunnel via Hurricane Electric works nicely with the supplied configuration (changed with the right addresses for that tunnel). ** 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/1799487 Title: Support for sit (ipv6) tunnels To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1799487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759014] Re: Netplan has no way to control DHCP client
This means we'll need to identify what patches need to be applied on top of v237 to make this work. Is this crippling? Are we able to verify that dhcp customization work despite anything missing in systemd? I think it's the case; but I'd like a second opinion. To be clear: I think we can verify this SRU despite any additional issues existing in systemd that also might need to be fixed. ** Also affects: systemd (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/1759014 Title: Netplan has no way to control DHCP client To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776228] Re: Duplicate default routes on VMs with multiple NICs
Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776228 Title: Duplicate default routes on VMs with multiple NICs To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1776228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739578] Re: Missing support for WPA2 Enterprise
That is up to the Ubuntu Core team to do; but before they can do it it needs to be landed in the archive for classic :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739578 Title: Missing support for WPA2 Enterprise To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1739578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed
Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811868 Title: networkd/NetworkManager are not re-started on netplan apply when config files are removed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759014] Re: Netplan has no way to control DHCP client
There is no dependency on v239 for netplan backports. Bionic ships with v237 (and some patches); the dependency on systemd is for >= 235-3ubuntu3 in netplan.io. I do not believe a newer version than that is required. Alexey, I really appreciate the work done to make such a backport available, but it's typically not a good thing to recommend or enable, since the reinforces a behavior (installing random stuff from the Internet, running commands that download scripts and run them as root) that is very unsafe. It is better to enable and use the package straight from the Ubuntu archive from a more recent release (or even build it yourself); or wait for Ubuntu developers to make the backports available. For netplan, we do run a large number of tests when making backports to help ensure there are no regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759014 Title: Netplan has no way to control DHCP client To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1759014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401532] Re: GRUB's Secure Boot implementation loads unsigned kernel without warning
** Changed in: grub2 (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: grub2-signed (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: grub2 (Ubuntu Trusty) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2-signed (Ubuntu Trusty) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2-signed (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2 (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2 (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: grub2-signed (Ubuntu Xenial) 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/1401532 Title: GRUB's Secure Boot implementation loads unsigned kernel without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub
** Description changed: [Impact] All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot) [Test case] + == Upgrade prompting == + 0) Install Ubuntu + 1) Modify /etc/default/grub.cfg options + 2) Copy /etc/default/grub.cfg to /var/lib/grub/ucf/grub.previous + 3) Update grub to the new package + + Verify that the user IS prompted to approve grub.cfg changes due to + changes in the template coming from the process. == User-specified changes == 0) Install Ubuntu 1) Modify /etc/default/grub.cfg options 2) Update grub to the new package Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg. == Post-deployment upgrades on MAAS-controlled system == 0) Deploy a system using MAAS 1) Update grub to the new package Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg. - [Regression potential] Pay attention to prompting behavior on grub updates as well as any failure to update the grub* packages. Prompting should be limited to the cases where the grub2 source package has changed the contents for the default provided grub.cfg; and on MAAS-controlled systems, the local modifications have changed in some way from the original copy of grub2 installed on the system. --- Binary package hint: grub-pc This concerns grub-pc 1.98-1ubuntu5 in Lucid beta1 (upgrading from 1.98-1ubuntu4). I have a locally modified /etc/default/grub file. When I upgraded to this version of grub-pc, I got the "A new version of configuration file /etc/default/grub is available, but the version installed currently has been locally modified. What do you want to do about modified configuration file grub?" question. The problem is, when I look at the diff, it just shows the differences between my file, and the way it was originally. In other words, the upgraded package does not include any updates to this file; its "pristine" copy of /etc/default/grub is the same as the previous version's. So I shouldn't even be getting a conffile prompt in the first place---as far as the administrator is concerned, nothing has changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
netplan is currently writing about as much as we can for the networkd/udev configs; some values we don't know how to handle at all. Looking at this, it feels to me like there will indeed be a need to find a different data point to differentiate the interfaces, and MAC and driver are not sufficient. This might require work in udev, so I've added a task for systemd. Could you please provide us with more information on these devices? Could you please run 'udevadm info' for the slaves as well, so we see if there are any extra fields we can use? If we can't find anything usable already in udev, then we might need to consider modifying the kernel driver itself to expose some information that will be needed to make the difference between the devices. This is Triaged/Undecided for netplan, since it's quite obviously a limitation, it will need work to implement, but we can't really prioritize it before knowing what data we can work with to match on the interfaces / work done on systemd/udev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: systemd (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/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811160] Re: Add option to configure wireless network frequency / channel
Triaged / Wishlist While the example shows "channel", that feature doesn't currently exist. ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Wishlist ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811160 Title: Add option to configure wireless network frequency / channel To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1811160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812457] Re: Parsing error
Thanks! This is quite a fun bug; well defined and should be interesting to address. Triaging. ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => High ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => High ** Summary changed: - Parsing error + Parsing error / silent fail on unmatched brackets ** Changed in: netplan 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/1812457 Title: Parsing error / silent fail on unmatched brackets To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1812457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813835] Re: Wrong dev in routing table in case of bridge on vlan
That's odd. Let's dig in deeper, as it quite likely might be a systemd bug, but I rather be certain it's not us doing something wrong. Could you please attach the config files generated in /run/systemd/network/ so we can confirm that the routes are created for the right devices? Thanks! ** Changed in: netplan Status: New => Incomplete ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (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/1813835 Title: Wrong dev in routing table in case of bridge on vlan To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1813835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814012] Re: netplan type wifis needs a device option
That's not quite the device, but a driver value though. I wonder if it wouldn't be best to either always set -Dnl80211 on wireless (and -Dwired for 802.1x on ethernet...), or to make it possible to use an alternative value if matching by driver. For example: wifis: wlan1: match: driver: wext name: wlan1 access-points: [...] dhcp4: yes ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => High ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (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/1814012 Title: netplan type wifis needs a device option To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1814012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814012] Re: netplan type wifis needs a device option
Triaged; we will need some input from Steve though to figure out how to addess this in the netplan schema. It's Triaged High as it actually does potentially impact many devices. There are sadly still lots of devices that either don't do wext, or don't do nl80211, and maybe it wouldn't hurt to be explicit when enabling 802.1x on wired. ** Changed in: netplan Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814012 Title: netplan type wifis needs a device option To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1814012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814602] Re: unconfigured interfaces part of a 802.3ad bond getting DHCP IP & being set as default route
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (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/1814602 Title: unconfigured interfaces part of a 802.3ad bond getting DHCP IP & being set as default route To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1814602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814952] Re: netplan try crashes if exception occurs
*** This bug is a duplicate of bug 1817660 *** https://bugs.launchpad.net/bugs/1817660 ** Changed in: netplan Status: New => Fix Released ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1817660 test_terminal.TestTerminal tests fail when run a second time -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814952 Title: netplan try crashes if exception occurs To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1814952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815734] Re: yml yaml file extension
Sure. This seems like a simple fix / enhancement. ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Wishlist ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => Wishlist ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815734 Title: yml yaml file extension To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817650] Re: Primary slave on the bond not getting set.
What are the exact contents of /etc/netplan/50-cloud-init.yaml and /etc/netplan/60-puppet-netplan.yaml? Do both define bond0? I have used the config provided (after setting dummy IPs and MAC that pass validation) and made sure indentation was correct, and it seems to parse and generate config just fine: netplan.generate:54: DEBUG: running ['./generate', '--root-dir', '../testing/'] (generate:16592): netplan.generate-DEBUG: 13:48:46.639: Processing input file ../testing//etc/netplan/netplan.yaml.. (generate:16592): netplan.parse-DEBUG: 13:48:46.639: starting new processing pass (generate:16592): netplan.generate-DEBUG: 13:48:46.639: Generating output files.. (generate:16592): netplan.generate.nm-DEBUG: 13:48:46.640: NetworkManager: definition e1p1 is not for us (backend 1) (generate:16592): netplan.generate.nm-DEBUG: 13:48:46.640: NetworkManager: definition p1p1 is not for us (backend 1) (generate:16592): netplan.generate.nm-DEBUG: 13:48:46.640: NetworkManager: definition p1p2 is not for us (backend 1) (generate:16592): netplan.generate.nm-DEBUG: 13:48:46.640: NetworkManager: definition bond0 is not for us (backend 1) (generate:16592): GLib-DEBUG: 13:48:46.640: posix_spawn avoided (fd close requested) I've used exactly this: network: version: 2 ethernets: e1p1: addresses: - 1.1.1.1/24 gateway4: 1.1.1.24 match: macaddress: 00:00:00:0a:ab:cd mtu: 9000 nameservers: addresses: - 8.8.8.8 set-name: e1p1 p1p1: match: macaddress: 01:00:00:0a:ab:cd mtu: 1500 set-name: p1p1 p1p2: match: macaddress: 02:00:00:0a:ab:cd mtu: 1500 set-name: p1p2 bonds: bond0: mtu: 9000 interfaces: [p1p1, p1p2] parameters: mode: active-backup mii-monitor-interval: 100 primary: p1p2 Is there any additional information you can provide that would help us in identifying what might be the issue here? Thanks! ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete ** Changed in: netplan 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/1817650 Title: Primary slave on the bond not getting set. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1817650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818689] Re: netplan fails to apply IP address
This is a red herring. The debug message does not mean that there isn't configuration. Is it possible that the MAC address changes across reboots? Could you enable debugging on systemd-networkd; then reboot so we can see if the interfaces are available at the time netwrokd will try to apply the configuration? ** Changed in: netplan Status: New => Incomplete ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete ** No longer affects: netplan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818689 Title: netplan fails to apply IP address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1818689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819833] Re: CLI option to find version would be very nice
** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => High ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (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/1819833 Title: CLI option to find version would be very nice To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1819833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819831] Re: broken genration of wpa config for hashed passwords
Sound simple and straightforward. I was not aware that such shorthand was possible (in fact, it doesn't seem to be documented in the manpage?) Marking Triaged / Medium; this should really be quite the simple fix to special-case when the password starts with "hash:". ** Changed in: netplan Status: New => Triaged ** Changed in: netplan Importance: Undecided => Medium ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => Medium ** Tags added: bitesize -- 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 genration 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 1820245] Re: Netplan and Keepalived not work
Evgeniy Yablokov: Could you also please send me configs (after sanitizing them for IPs you don't want to share, etc.)? I'd be quite curious to see how you did your setup, how it works, etc. There are some known issues, especially in running 'netplan apply' which might cause netwrokd to blast away the addresses. ** Changed in: netplan Status: New => Incomplete ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (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/1820245 Title: Netplan and Keepalived not work To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820771] Re: systemd-networkd exhibits core dump on greater than 1024 addresses
Reassigning to systemd -- netplan isn't limited, but if systemd-networkd crashes that's a bug in systemd-networkd. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** No longer affects: netplan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820771 Title: systemd-networkd exhibits core dump on greater than 1024 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
** Also affects: debian-installer (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/1798171 Title: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1798171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819084] Re: Installer crashed
Mar 8 01:55:10 ubuntu /install.py: keeping language packs for: en_CA.UTF-8 en_US.UTF-8 Mar 8 01:55:11 ubuntu ubiquity: W: --force-yes is deprecated, use one of the options starting with --allow instead. Mar 8 01:55:11 ubuntu ubiquity: E: Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable) Mar 8 01:55:11 ubuntu ubiquity: E: Unable to lock directory /target/var/cache/apt/archives/ Mar 8 01:55:20 ubuntu /install.py: MD5 failure on /target/lib/firmware/intel/ibt-hw-37.7.bseq Mar 8 01:55:21 ubuntu ubiquity: W: --force-yes is deprecated, use one of the options starting with --allow instead. This may be symptoms of a disk that is about to fail -- these errors are things that really shouldn't be happening: "Resource temporarily unavailable" trying to claim a lock or an MD5 failure on firmware files aren't normal. Could you please first check that the image you downloaded was indeed complete (by verifying the image from the boot menu, and/or checking its checksum (see https://help.ubuntu.com/community/BurningIsoHowto#Verifying_the_ISO_integrity and https://help.ubuntu.com/community/Installation/CDIntegrityCheck). If everything looks good; I would suggest trying to install on a separate computer, or replacing the disk / installing on a different device (such as installing on another USB disk). Thanks! ** Changed in: ubiquity (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/1819084 Title: Installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1819084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
Disabling Secure Boot temporarily in order to finish the installation (mmx64.efi is supposed to be installed on disk at the end of the install), or editing an installation image on USB to copy grubx64.efi in a new file called mmx64.efi Should be good workarounds for this. Please don't run a system-rescue-cd or such custom "rescue" images to manually remove files from /sys/firmware/efi/efivars -- it *can* be done, but it's quite dangerous, likely to brick you system in a way that *can't* be recovered. As per the above, the right fix is to finish the installation and run the real mmx64.efi either by disabling Secure Boot in your firmware (but NOT switching to Legacy boot) or making the mmx64.efi available as a copy of grub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798171 Title: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1798171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798171] Re: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found
** Changed in: grub2 (Ubuntu) Assignee: Miguel Alcaide (migalc) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798171 Title: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1798171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820779] Re: Failed to reinstall Ubuntu 18.10
This appears likely to have been a transient network issue. Are you able to reproduce the same crash again if you try the install again? ** Changed in: ubiquity (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/1820779 Title: Failed to reinstall Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820676] Re: Something has gone seriously wrong: import_mok_state0 failed
\EFI\BOOT\mmx64.efi should be on all the images; we should investigate this in case it was somehow dropped. The issue seems to be that we immediately go apply the changes when people configure Secure Boot in the installer, but this requires MokManager to run at the very next boot -- if it's not available anywhere, we should fail more gracefully than we currently do though. Still, MokManager is supposed to be on the images. ** 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/1820676 Title: Something has gone seriously wrong: import_mok_state0 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820795] Re: Ubuntu installer crashed
There are some odd errors in UbiquitySyslog.txt I haven't seen before: Mar 19 04:38:51 ubuntu user-setup: adduser: Only one or two names allowed. Mar 19 04:38:51 ubuntu ubiquity: chpasswd: (user ) pam_chauthtok() failed, error: Mar 19 04:38:51 ubuntu ubiquity: Authentication token manipulation error Mar 19 04:38:51 ubuntu ubiquity: chpasswd: (line 1, user ) password not changed Could you please tell us more about exactly how you filled in the User Setup screen? Did you use any special characters, or something with spaces under the username field? ** Changed in: ubiquity (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/1820795 Title: Ubuntu installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1820795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub
** Description changed: + [Impact] + All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot) + + [Test case] + + == User-specified changes == + 0) Install Ubuntu + 1) Modify /etc/default/grub.cfg options + 2) Update grub to the new package + + Verify that the user is not prompted to approve grub.cfg changes unless + the grub2 package unless the grub packages have changed the contents of + the default grub.cfg. + + == Post-deployment upgrades on MAAS-controlled system == + 0) Deploy a system using MAAS + 1) Update grub to the new package + + Verify that the user is not prompted to approve grub.cfg changes unless + the grub2 package unless the grub packages have changed the contents of + the default grub.cfg. + + + [Regression potential] + Pay attention to prompting behavior on grub updates as well as any failure to update the grub* packages. Prompting should be limited to the cases where the grub2 source package has changed the contents for the default provided grub.cfg; and on MAAS-controlled systems, the local modifications have changed in some way from the original copy of grub2 installed on the system. + + --- + Binary package hint: grub-pc This concerns grub-pc 1.98-1ubuntu5 in Lucid beta1 (upgrading from 1.98-1ubuntu4). I have a locally modified /etc/default/grub file. When I upgraded to this version of grub-pc, I got the "A new version of configuration file /etc/default/grub is available, but the version installed currently has been locally modified. What do you want to do about modified configuration file grub?" question. The problem is, when I look at the diff, it just shows the differences between my file, and the way it was originally. In other words, the upgraded package does not include any updates to this file; its "pristine" copy of /etc/default/grub is the same as the previous version's. So I shouldn't even be getting a conffile prompt in the first place---as far as the administrator is concerned, nothing has changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787630] Re: [FFe] Include HTTP support in pre-build GRUB module
** Description changed:
- {Description]
+ [Impact]
+ Required for MAAS to use HTTP transport to provide files for grub2.
+
+ [Test case]
+ 0) Provide kernel and initrd on an HTTP server on the network.
+ 1) Boot from the network in UEFI mode using grub's grubnet.efi binary.
+ 2) Run the following commands:
+
+ linuxefi http:///
+ initrdefi http:///
+ boot
+
+ Verify that the system is able to correctly retrieve the kernel and
+ initrd files from the HTTP server, and that the system boots normally.
+
+ [Regression potential]
+ None. This makes an additional module available for use in the
grubnet.efi pre-built and signed UEFI binaries for grub; it does not
otherwise affect other pre-built UEFI images, does not change grub code, and is
not used unless explicitly configured to do so by a custom grub configuration
file (not in use by default).
+
+ ---
+
+ [Description]
Grub supports booting files over the network via both FTP/HTTP. However, the
Ubuntu package is not built with the grub HTTP modules. Enabling this would
allow grub to obtain files over HTTP (such as initrd/kernel).
[Rationale]
Enabling HTTP support for Grub would allow MAAS to use such functionality to
boot files over the network with HTTP. This allows for improvement performance
(vs using ftp) and for better security.
MAAS would use this to download kernel and initrd over HTTP instead of
FTP at first for performance improvements.
[Original bug report]
GRUB has builtin support for HTTP via http.mod. This module is not being
included in the prebuild grubnetx64.efi. All that should be required is
adding the http module. I also suggest building grubnetx64.efi using
GRUB modules to include lvm and RAID support this will allow
grubnetx64.efi to local boot in all situations.
--- build-efi-images 2018-08-17 10:50:35.124311043 -0700
+++ build-efi-images.new 2018-08-17 10:50:59.270661126 -0700
@@ -148,8 +148,9 @@
raid5rec
raid6rec
"
-NET_MODULES="$CD_MODULES
+NET_MODULES="$GRUB_MODULES
tftp
+ http
"
"$grub_mkimage" -O "$platform" -o "$outdir/gcd$efi_name.efi" \
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787630
Title:
[FFe] Include HTTP support in pre-build GRUB module
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1787630/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742711] Re: MIR: vulkan-loader
Looks generally good to me, but this is a very large and complex project. I've tried to review the code as much as I could, but I would feel better if there were more eyes on it. Assigning to ~ubuntu-security ... I'm not requesting a full security code review, but leaving it to the Security Team to ack or decide if it really should need a more in- depth code review. ** Changed in: vulkan-loader (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742711 Title: MIR: vulkan-loader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
