[Bug 1904987] Re: Please add this package to i386-whitelist
** Changed in: pycryptodome (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904987 Title: Please add this package to i386-whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycryptodome/+bug/1904987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905156] Re: netplan KeyError with gretap in bridge
This looks similar to bug #1904633 ** Tags added: fr-960 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905156 Title: netplan KeyError with gretap in bridge To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1905156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904549] Re: MTU is not set on vlan interface
This looks kind of similar to LP: #1888726 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904549 Title: MTU is not set on vlan interface To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1904549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898997] Re: MAAS cannot deploy/boot if OVS bridge is configured on a single PXE NIC
I can confirm this is now working with hirsute images on MAAS 2.9.0~rc3, not using any additional PPAs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898997 Title: MAAS cannot deploy/boot if OVS bridge is configured on a single PXE NIC To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1898997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905156] Re: netplan KeyError with gretap in bridge
I think this should actually already be fixed upstream via https://github.com/CanonicalLtd/netplan/pull/163 where the tunnel interfaces were added to the python parser (configmanager.py). I will prepare a test-case to make sure it always works in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905156 Title: netplan KeyError with gretap in bridge To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1905156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905156] Re: netplan KeyError with gretap in bridge
test case and extra protection here: https://github.com/CanonicalLtd/netplan/pull/172 ** Changed in: netplan Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905156 Title: netplan KeyError with gretap in bridge To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1905156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903814] Re: [binutils] Prevent GOT access rewrite for certain symbols
Both autopkgtest regressions have turned out to be intermittent failures and have been resolved by retriggering the corresponding tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916888] Re: The autopkgtest started failing on ppc64el: Temporary failure resolving 'ftpmaster.internal'
** Changed in: netplan.io (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: netplan.io (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916888 Title: The autopkgtest started failing on ppc64el: Temporary failure resolving 'ftpmaster.internal' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1916888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915926] Re: Make R packages migrate
** Changed in: rmatrix (Ubuntu) Status: New => Fix Released ** Changed in: r-cran-matrixstats (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-s4vectors (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-rhdf5lib (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-matrixgenerics (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-iranges (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-hdf5array (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-delayedarray (Ubuntu) Status: New => Fix Released ** Changed in: r-bioc-beachmat (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915926 Title: Make R packages migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/r-bioc-beachmat/+bug/1915926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926442] Re: cannot execute 'netplan generate' from within a snap
The new io.netplan.Netplan.Generate() DBus API has been implemented in netplan upstream: https://github.com/canonical/netplan/pull/208 https://github.com/canonical/netplan/pull/209 It needs to be released and SRUed down to Bionic for the snapd change to be accepted (https://github.com/snapcore/snapd/pull/10212) ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => In Progress ** Also affects: netplan.io (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Impish) Importance: Undecided Status: In Progress ** Also affects: netplan.io (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Groovy) Importance: Undecided Status: New ** Summary changed: - cannot execute 'netplan generate' from within a snap + [SRU] cannot execute 'netplan generate' from within a snap ** Tags added: fr-1382 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926442 Title: [SRU] cannot execute 'netplan generate' from within a snap To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1926442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Also affects: dbus (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags added: rls-ff-incoming rls-hh-incoming ** Also affects: dbus (Ubuntu Impish) Importance: High Status: Incomplete ** Also affects: gnome-shell (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: accountsservice (Ubuntu Impish) Importance: Undecided Status: Invalid ** Also affects: dbus (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Groovy) Importance: Undecided Status: New ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919451] Re: Update (python-)zhmcclient to latest release
LGTM, thanks for the debdiff! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
After crushing the logs a bit more, I found a few interesting things and
also have a few open questions. Thank you very much for your `date`
timestamps in between the different steps, those are very helpful in
linking the order of events!
Open questions:
1) The "udevadm-monitor.txt" log shows that there is a manual
"/etc/systemd/network/10-enP53p0s0.link" configuration file, while all other
interfaces make use of "/usr/lib/systemd/network/99-default.link". Can you show
us what is inside this file?
2) In comment #22 you show the output of "networkctl":
root@ilabg13:~# netplan apply
root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager
? 7: enP53p0s0.171
Link File: n/a
Network File: n/a
Type: vlan
State: degraded (pending)
HW Address: 82:0c:9b:c9:78:f8
=> I wonder why "Link File: n/a" and "Network File: n/a" is set.. The
Link state is still "(pending)", would you mind executing the same steps
again and re-executing the "networkctl status enP53p0s0.171 --no-pager"
a bit later again (like 10sec after and 30sec after)?
3) Does the workaround from
https://github.com/systemd/systemd/issues/15445#issuecomment-776856604
work for you? E.g.:
# netplan apply
- wait 15 sec
# networkctl reload
- wait 15 sec
# networkctl renew enP53p0s0.171
- wait 15 sec
# networkctl reconfigure enP53p0s0.171
- wait 15 sec
# networkctl reconfigure enP53p0s0.171
- wait 30 sec
# networkctl status enP53p0s0.171 --no-pager
# ip a
=== Findings from comment #33 (journalctl_udev_monitor.txt) ===
You executed "netplan apply" between 08:10:29 - 08:10:59 and it looks like
systemd-networkd found the correct netplan-*.network configuration and applied
it (assigned the IP) at 08:10:57. See "***" lines:
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Link state is
up-to-date
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: found matching
network '/run/systemd/network/10-netplan-enP53p0s0.171.network'
Jun 15 08:10:57 systemd-networkd[182847]: Setting
'/proc/sys/net/ipv6/conf/enP53p0s0.171/disable_ipv6' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: IPv6 successfully
enabled
Jun 15 08:10:57 systemd-networkd[182847]: Setting
'/proc/sys/net/ipv6/conf/enP53p0s0.171/proxy_ndp' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: Setting
'/proc/sys/net/ipv6/conf/enP53p0s0.171/use_tempaddr' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: Setting
'/proc/sys/net/ipv6/conf/enP53p0s0.171/accept_ra' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: LLDP: Started LLDP client
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Started LLDP.
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Setting address
genmode for link
[...]
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering
updated address: 192.168.171.53/24 (valid forever)
Jun 15 08:10:57 systemd-networkd[182847]: Sent message type=signal sender=n/a
destination=n/a path=/org/freedesktop/network1/link/_37
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=45
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route:
dst: 192.168.171.53/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope:
host, table: local, proto: kernel, type: local
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route:
dst: 192.168.171.255/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope:
link, table: local, proto: kernel, type: broadcast
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route:
dst: 192.168.171.0/24, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link,
table: main, proto: kernel, type: unicast
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route:
dst: 192.168.171.0/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link,
table: local, proto: kernel, type: broadcast
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Addresses set
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: State changed:
configuring -> configured
[...]
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Processing device
(SEQNUM=87120, ACTION=change)
Jun 15 08:11:28 systemd-udevd[182940]: enP50s3832:
/usr/lib/udev/rules.d/75-net-description.rules:12 Importing properties from
results of builtin command 'hwdb --subsystem=pci'
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171:
/usr/lib/udev/rules.d/75-net-description.rules:6 Importing properties from
results of builtin command 'net_id'
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171:
/usr/lib/udev/rules.d/80-net-setup-link.rules:5 Importing properties from
results of builtin command 'path_id'
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171:
/usr/lib/udev/rules.d/80-net-setup-link.rules:5 Failed to run builtin
'path_id': No such file or directory
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171:
/usr/lib/udev/rules.d/80-net-setup-link.rules:9 Importing properties from
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Looks like I can at least reproduce the issue on an arm64 Canonistack machine, utilizing an armhf container: ubuntu@focal-arm64:~$ time autopkgtest systemd --test-name=boot-and-services -U -- lxd autopkgtest/ubuntu/impish/armhf [...] autopkgtest [15:59:21]: test boot-and-services: [--- lxc Created symlink /etc/systemd/system/default.target → /lib/systemd/system/graphical.target. bash: line 1: 3532 Killed /tmp/autopkgtest.OAYOpR/build.yrL/src/debian/tests/boot-and-services 2> >(tee -a /tmp/autopkgtest.OAYOpR/boot-and-services-stderr >&2) > >(tee -a /tmp/autopkgtest.OAYOpR/boot-and-services-stdout) autopkgtest [15:59:24]: test process requested reboot with marker boot1 Unexpected error: Traceback (most recent call last): File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 738, in mainloop command() File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 667, in command r = f(c, ce) File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 363, in cmd_reboot caller.hook_wait_reboot() File "/usr/bin/autopkgtest-virt-lxd", line 231, in hook_wait_reboot wait_booted() File "/usr/bin/autopkgtest-virt-lxd", line 104, in wait_booted VirtSubproc.check_exec(['lxc', 'exec', container_name, '--', 'sh', '-ec', '[ ! -d /run/systemd/system ] || systemctl start network-online.target'], timeout=60) File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 182, in check_exec (status, out, err) = execute_timeout(None, timeout, real_argv, File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 144, in execute_timeout (out, err) = sp.communicate(instr) File "/usr/lib/python3.8/subprocess.py", line 1014, in communicate stderr = self.stderr.read() File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 64, in alarm_handler raise Timeout() VirtSubproc.Timeout autopkgtest [16:01:18]: ERROR: testbed failure: unexpected eof from the testbed real8m29.354s user0m8.866s sys 0m8.141s Let's see what we can do about it. It looks like a dnsmasq (security-)update was pushed to Bionic++ on 2021-06-02 – about the same time that this test started failing on Bionic++ ... I wonder if this might somehow be related? ... need to further investigate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
> Gave some time between netplan apply and check without success, I can leave > it for > hours and the IP never gets assigned Indeed, I cannot see it being assigned an IPv4 address in your latest "_delay" run. (Well, there is some assignment of an IP to enP53p0s0.171 at 15:05:29 in the journal logs, but that was before you started the experiment). > maybe what you are seeing is the manual assignment that I did with > ip addr add 192.168.171.53/24 dev enP53p0s0.171 No I don't think so, as the timestamp of your manual "ip addr add" command (08:13:02++) is after the systemd-networkd assignment in the logs (08:12:38). Also, your output clearly shows that the IP was already assigned when you tried to (re-)assign it manually (it shows the "RTNETLINK answers: File exists" error): > root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171 > RTNETLINK answers: File exists I'm a bit worried about the /etc/systemd/network/10-enP53p0s0.link file (now there seems to be another one "10-enP53p0s0.link" as well...) – Is this file needed? Why was it created? It matches on "MACAddress=82:0c:9b:c9:78:f8", which would match enP53p0s0 AND enP53p0s0.171 at the same time (they use the same inherited MAC address), leading to unspecified behavior, as we cannot rename two interfaces to the same "Name=enP53p0s0". Could you try deleting this file in /etc/systemd/network/10-enP53p0s0.link (potentially adopting your netplan YAML config to the name assigned to this interface by the kernel/systemd) and check if this makes any difference? # rm /etc/systemd/network/10-enP53p0s0.link If for some reason you cannot delete this file, try adding a "Type=!vlan" line instead: # cat /etc/systemd/network/10-enP53p0s0.link [Match] MACAddress=82:0c:9b:c9:78:f8 Type=!vlan [Link] Name=enP53p0s0 Does this make any difference when running "netplan apply && sleep 30 && networkctl status -a --no-pager"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Thank you! The core problem still is that systemd-networkd does not find any .link and .network file for the enP53p0s0.171 interface, that's why it cannot apply any configuration (IP address): > ? 9: enP53p0s0.171 > Link File: n/a > Network File: n/a This might very well be related to the additional /etc/systemd/network/10-enP53p0s0.link, which is now gone and apparently not needed (good!) – leave that away. Still the configuration/match of that file might still be loaded into the running udev, so we must somehow reset udev to a clean state. I'd like to ask you for another test run (and potential reboot of that machine – if that is possible?): # try to reload udev at runtime udevadm control --reload; udevadm trigger; udevadm settle # wait a bit sleep 30 # apply netplan configuration netplan --debug apply # wait a bit sleep 30 # check results networkctl status enP53p0s0.171 --no-pager ip a If the IP is still not set, could you please try to reboot the machine and check "networkctl" afterwards? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
So I can reproduce the problem even locally, using a simple: `autopkgtest systemd --test-name=boot-and-services -- lxd autopkgtest/ubuntu/impish/amd64` When logging into the (stalled) system, while it is waiting for its timeout I can see that eth0 gets configured, but then put in DOWN state. Therefore, systemd-networkd-wait-online.service (and thus network-wait- online.target) never get ready and the test times out waiting on "network-wait-online.target". A simple "networkctl up eth0" (inside the LXD container) during that 60s "timeout-wait" makes the test runner connect an finish the test successfully. The culprit for bringing down the interface seems to be "/run/systemd/system/network-device-down.service", but I have no idea where this files comes from or what it is used for. It's not part of any package. That service has a "Before=NetworkManager.service" dependency, that's why it only breaks tests making use of network-manager (boot-and- services & boot-smoke). The LXD/LXC stack seems to be somehow involved in creating that file: https://github.com/lxc/lxc-ci/pull/266 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Also affects: lxd (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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
This should fix the problem: https://github.com/lxc/distrobuilder/pull/476 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932368] Re: boot-smoke systemd/237-3ubuntu10.48 ADT test failure with bionic
*** This bug is a duplicate of bug 1931088 *** https://bugs.launchpad.net/bugs/1931088 ** This bug has been marked a duplicate of bug 1931088 boot-and-services tests fails in impish on armhf (248.3) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932368 Title: boot-smoke systemd/237-3ubuntu10.48 ADT test failure with bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: systemd (Ubuntu Impish) Status: Confirmed => Invalid ** Changed in: lxd (Ubuntu Impish) Status: New => Fix Committed ** Changed in: lxd (Ubuntu Impish) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: auto-package-testing Status: Incomplete => Invalid ** Changed in: dnsmasq (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: gdm3 (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: glibc (Ubuntu Impish) Status: Incomplete => Invalid ** Changed in: isc-dhcp (Ubuntu Impish) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
An interesting observation I made is that all journal logs (in this LP bug and the upstream systemd bug) show the "polkit.service: Unexpected error response from GetNameOwner(): Connection terminated" message, in addition to a bunch of other "Connection terminated" errors from changing services across the different installations (NetworkManager.service, accounts-daemon.service, systemd- logind.service, ...). I've also seen logs (from Gauthier) where only polkit.service is failing. The polkit.service "Unexpected error response from GetNameOwner()" message is a log from systemd effectively telling us that systemd cannot reach org.freedesktop.PolicyKit1 on DBus. But the root cause for that must be that polkitd is not running (or dbus is somehow stuck in a deadlock, not responding anymore). This gives a new twist to this issue, as we might be searching for a phantom in (lib-)systemd... PolicyKit is using glib's gdbus implementation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: lxd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922126] Re: autopkgtest fails in hirsute on some architectrures
** Changed in: netplan.io (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922126 Title: autopkgtest fails in hirsute on some architectrures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1922126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934988] [NEW] Upgrade s390-tools to latest version (2.17.0)
Public bug reported: Include latest version of s390-tools 2.17.0 related to kernel 5.12+ v2.17.0 was just released: https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.17.0 ** Affects: s390-tools (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ii-incoming ** Also affects: s390-tools (Ubuntu Impish) Importance: Undecided Status: New ** Tags added: rls-ii-incoming ** No longer affects: s390-tools (Ubuntu Impish) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
** Summary changed: - networkd-dispatcher gives corrupted information + [SRU] networkd-dispatcher gives corrupted information -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: [SRU] networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
** Description changed:
+ [Impact]
+
+ * Due to changes in systemd's networkctl output networkd-dispatcher 2.0
contains a bug, producing invalid keys/values inside the JSON it provides to
its scripts
+ * e.g.: json={"A": ["ress: 119.224.106.22 (DHCP4)"], ...}
+ * Therefore the scripts cannot access the relevant network configuration
state
+
+
+ [Test Plan]
+
+ * Run systemd v244+ (e.g. in a LXD container)
+ * Make sure you got an IP address via DHCP:
+ * # networkctl status eth0
+ ● 120: eth0
+ Link File: /usr/lib/systemd/network/99-default.link
+ Network File: /run/systemd/network/10-netplan-eth0.network
+ Type: ether
+ State: routable (configured)
+ Driver: veth
+ HW Address: 00:16:3e:0b:d7:74 (Xensource, Inc.)
+MTU: 1500 (min: 68, max: 65535)
+ Queue Length (Tx/Rx): 1/1
+ Auto negotiation: no
+ Speed: 10Gbps
+ Duplex: full
+ Port: tp
+Address: 10.238.94.146 (DHCP4)
+ fd42:7213:f20e:bd74:216:3eff:fe0b:d774
+ fe80::216:3eff:fe0b:d774
+Gateway: 10.238.94.1 (Xensource, Inc.)
+ fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)
+DNS: 10.238.94.1
+ fd42:7213:f20e:bd74::1
+ fe80::216:3eff:fe0f:ee29
+ Search Domains: lxd
+ Activation Policy: up
+ * # cat /etc/networkd-dispatcher/routable.d/00run.sh
+ #!/bin/bash
+ env > /tmp/out.log
+ * chmod +x /etc/networkd-dispatcher/routable.d/00run.sh
+ * # networkd-dispatcher --run-startup-triggers
+ * cat /tmp/out.log
+ * Check json= ENV to verify if it contains the correct IPv4 address (without
"(DHCP4)" suffix).
+
+ [Where problems could occur]
+
+ * This was broken in 2.0 and the fix changes the behavior back to what was
originally intended.
+ * If people adopted to the broken environment variable, to somehow parse the
information they need from the broken JSON, this change will most probably
break their networkd-dispatcher scripts (again).
+
+
+ [Other Info]
+
+ * The upstream version 2.1 just fixes the parsing of current networkctl
output (in addition to a few testing and documentation improvements)
+ * The Debian revision -2 fixes the parsing of the "(DHCP4 ...)" suffix
+
+
+ === Original description ===
+
I just reinstalled my RPI3 router from Eoan to Focal but a lot of things
about networkd broke. I'm not sure whether they are related or not.
The first thing I noticed was, that I did not get my upstream DNS
servers. I use a dispatcher script to extract the information from the
json environment variable when my uplink becomes routable. Using a test
script to dump the environment I found this:
IP6_ADDRS=
PWD=/
json={"A": ["ress: 119.224.106.22 (DHCP4)"], "AdministrativeState":
"configuring", "Auto negot": ["tion: yes", "peed: 100Mbps", "plex: full",
"Port: mii"], "G": ["eway: 119.224.106.21", "DNS: 202.180.64.10",
"202.180.64.11", ""], "HW A": ["ress: b8:27:eb:b6:a5:f4 (Raspberry Pi
Foundation)", "MTU: 1500 (max: 65535)"], "InterfaceName": "wan", "Jun 20
00:01:49": ["mnus systemd-networkd[534]: wan: netdev ready", "mnus
systemd-networkd[534]: wan: Link UP", "mnus systemd-networkd[534]: wan: Gained
carrier"], "Jun 20 00:01:50": ["mnus systemd-networkd[534]: wan: Lost
carrier"], "Jun 20 00:01:51": ["mnus systemd-networkd[534]: wan: Gained
carrier"], "Jun 20 00:01:53": ["mnus systemd-networkd[534]: wan: DHCPv4 address
119.224.106.22/30 via 119.224.106.21"], "Lin": ["File:
/usr/lib/systemd/network/99-default.link"], "Networ": ["File:
/etc/systemd/network/07-wan.network", "Type: vlan", "tate: routable
(configured)", "iver: 802.1Q VLAN Support"], "OperationalState": "routable",
"Queue Length (": ["/Rx): 1/1"], "State": "routable (configuring)", "Type":
"vlan"}
AdministrativeState=configuring
IFACE=wan
LANG=en_NZ.UTF-8
INVOCATION_ID=384cc7de4e8d45e48ecb2ecf3cb55508
IP_ADDRS=
ESSID=
ADDR=
NOTIFY_SOCKET=/run/systemd/notify
SHLVL=1
STATE=routable
JOURNAL_STREAM=9:35403
OperationalState=routable
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
networkd_dispatcher_args=--run-startup-triggers
Note that the
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
** Changed in: networkd-dispatcher (Ubuntu Hirsute) Status: Fix Released => Triaged ** Also affects: networkd-dispatcher (Ubuntu Impish) Importance: High Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: [SRU] networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
Thank you! This one is looking pretty solid overall. But I think the "hex detection" has some flaws, as it only checks for capital letters and there is a discrepancy between accepting float hex numbers (which is unexpected IMO) but rejecting float octal numbers. Could you please test for some more edge cases like and make sure they all work (and maybe also octal floats): "0xDEADBEEF" "0xcafe42" "0xdeadbeef" "0xdead.beef" "0x." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925212] Re: FTBFS with GCC-11
Fixed in 0.10-15ubuntu1 ** Changed in: baycomepp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925212 Title: FTBFS with GCC-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baycomepp/+bug/1925212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922126] Re: autopkgtest fails in hirsute on some architectrures
Works again, since we changed it back to NOT being in `big_packages`. ** Changed in: netplan.io (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922126 Title: autopkgtest fails in hirsute on some architectrures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1922126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922126] Re: autopkgtest fails in hirsute on some architectrures
ACK. I've drafted some code a while ago which will improve this situation: https://github.com/canonical/netplan/pull/204 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922126 Title: autopkgtest fails in hirsute on some architectrures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1922126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-groovy verification-done-hirsute ** Tags removed: verification-done-groovy ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919453] Re: [SRU][FFe] Update to netplan.io 0.102
I re-verified the Groovy SRU (0.102-0ubuntu1~20.10.3) and updated the corresponding test logs for Groovy in the bug description. The logs are the same as in LP: #1922898 (same package, version & tests). All tests passed on first run. ** Description changed: [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to those improvements. The most notable changes (besides usual bug-fixes) incoming in 0.102: - New API for NetworkManager YAML backend - Improved netplan set CLI to override existing files - Documentation improvements - Allow running more tests in a container - Added congestion-window & advertised-receive-window options for routes - Added ttl option for tunnels (LP: #1846783) - systemd v247 compatibility (for changing MAC address) - Prevent duplicate ARPIPTargets in NetDev files (LP: #1915837) - Enable pristine-tar in gbp See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each release. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan.io package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. [Where problems could occur] Netplan being a core package it could impact the whole networking stack of the operating system up to the point where servers would not be reachable anymore after a reboot, due to broken network config being generated by netplan at bootup. In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug: Groovy: - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_amd64.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_arm64.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_armhf.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_ppc64el.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_s390x.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_amd64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_arm64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_armhf.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_ppc64el.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_s390x.log Focal: https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_s390x.log [Other Info] The integration test logs are attached to this bug, once the package has been accepted into -proposed and the tests have been executed on the real infrastructure. [Changelog] abad253 tests:bonds: fix flaky resend_igmp test 6270143 tests:base: avoid long waits b98a160 tests:base: improve daemon-reload check 3f19eeb tests:base: improve reliabilty by using higher timeout a049983 tests:base: improve management interface handling 8cb8621 test:utils: cleanup formatting e05731c cli:set: write to existing YAML file, if available (#197) 2263a13 libnetplan: provide API for NetworkManager YAML backend (#193) d34df50 test:tunnels: improve stability of wireguard test 15a3380 Prevent duplicate ARPIPTargets in NetDev files (LP: #1915837) (#199) 2ccddbe tests:integration: cleanup OVS/WPA files (#198) 9767b63 Improve integration tests (#196) f086808 Enable CodeQL code scanning (#195) 6c8ed65 Added TTL option for tunnels (LP: #1846783) (#194) 1e0f223 Added per route congestion-window/advertised-receive-window options (#177) ac2a1b9 Update Github URL (#192) 165e908 cli:utils: handle emtpy netifaces.ifaddresess call (#188) 51a6032 Stop using deprecated systemd-resolve tool d9d35c6 cli:apply: Add comment about snapd/DBus compatibility bdc2b1d Clarified `dhcp-identifier` option (#186) 1413f0e tests:integration: adopt for racy systemd MAC assignment 222c104 github: run action on any pull request 03746b4 tests:dbus: improve test stability of timeouts 465c530 tests:tunnels: improve test reliability 944b1e3 tests: adopt to wording changes as of OVS 2.15 86bd330 doc: Add a caveat to wake on LAN which is systemd.link related (LP: #1909114) (#180) 41bfbd6
[Bug 1922898] Re: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
** Description changed: [Impact] This release contains a regression bug-fix for un-breaking the ABI compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken from a pending upstream pull request: https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898) [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each release. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan.io package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Additionally, we want to manually verify the ABI compatibility (i.e. not SEGFAULT) between the new libnetplan and the old netplan.io "generate" binary, with the steps described below: * Have netplan 0.101 installed * Upgrade ONLY libnetplan0 to 0.102 $ cat /etc/netplan/00-config.yaml network: ethernets: ens5: dhcp4: true dhcp6: false match: macaddress: 06:f8:32:e5:34:28 set-name: ens5 version: 2 $ /usr/lib/netplan/generate * Make sure the "generate" binary did not crash. [Where problems could occur] Netplan being a core package it could impact the whole networking stack of the operating system up to the point where servers would not be reachable anymore after a reboot, due to broken network config being generated by netplan at bootup. In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. Additionally, this SRU needs to drop the "Added ttl option for tunnels (LP: #1846783)" feature, added during the 0.102/Hirsute development cycle. So users of the -devel series using the new "tunnels.ttl" setting are going to miss this until it is re-implemented in an ABI preserving way. Hirsute (Bileto pre-test): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/amd64/n/netplan.io/20210416_204928_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/arm64/n/netplan.io/20210416_213837_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/armhf/n/netplan.io/20210416_201636_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/ppc64el/n/netplan.io/20210416_210302_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/s390x/n/netplan.io/20210416_204523_fec70@/log.gz Groovy: - TBD groovy_amd64.log - TBD groovy_arm64.log - TBD groovy_armhf.log - TBD groovy_ppc64el.log - TBD groovy_s390x.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_amd64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_arm64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_armhf.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_ppc64el.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/groovy_s390x.log Focal: https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_s390x.log [Other Info] The integration test logs are attached to this bug, once the package has been accepted into -proposed and the tests have been executed on the real infrastructure. == Original description == Today a bunch of our ubuntu 20.04 servers on AWS EC2 (both amd64 and arm) upgraded to netplan 0.102-0ubuntu1~20.04.1, which resulted in a segfault when netplan ran generate, and then took the whole network down with it, the servers had to be force rebooted. kernel: [1938106.074273] netplan[2874371]: segfault at 1 ip 7f72cb991675 sp 7ffe8be03158 error 4 in libc-2.31.so[7f72cb82b000+178000] kernel: [1938106.074282] Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 2b fd 74 0f c5 fd d7 c1 85 c0
[Bug 1922898] Re: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
I verified the Groovy SRU (for 0.102-0ubuntu1~20.10.3) and attached the corresponding test logs to the bug description. Furthermore, I've verified the regression case, where libnetplan0 v0.102 is used with the netplan.io "generate" binary v0.101, which also passes (i.e. does not crash anymore): root@gg:~# dpkg -l | grep netplan ii libnetplan0:amd640.102-0ubuntu1~20.10.3 ii netplan.io 0.101-0ubuntu3~20.10.1 root@gg:~# cat /etc/netplan/00-config.yaml network: ethernets: ens5: dhcp4: true dhcp6: false match: macaddress: 06:f8:32:e5:34:28 set-name: ens5 version: 2 root@gg:~# /usr/lib/netplan/generate root@gg:~# echo $? 0 As you can see the "generate" binary does not crash with "Segmentation fault (core dumped)" anymore when using libnetplan0 0.102-0ubuntu1~20.10.3 ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928087] [NEW] Please remove src:jack-rack
Public bug reported: Removal request --- Please remove the "jack-rack" source package from the archive. It blocks the python2-rm transition, has been removed from Debian testing/unstable and seems rather unmaintained upstream. The binary package names are: jack-rack The (release) arch that should get targeted for removal is: source It was removed from Debian as well: https://tracker.debian.org/news/409981/bug740123-removed-packages-from-unstable/ It does not have reverse depends: $ reverse-depends -b jack-rack No reverse dependencies found ** Affects: jack-rack (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/1928087 Title: Please remove src:jack-rack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jack-rack/+bug/1928087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922971] Re: Sync python-pyscss 1.3.7-3 (main) from Debian unstable (main)
This bug was fixed in the package python-pyscss - 1.3.7-3 Sponsored for Logan Rosen (logan) --- python-pyscss (1.3.7-3) unstable; urgency=medium * Team upload. * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. * Fix pytest 6 compatibility (Closes: #977092). -- Ondřej Nový Sun, 17 Jan 2021 18:10:38 +0100 python-pyscss (1.3.7-2) unstable; urgency=medium * Uploading to unstable. -- Thomas Goirand Sat, 09 May 2020 13:37:34 +0200 python-pyscss (1.3.7-1) experimental; urgency=medium * New upstream release. * Ran wrap-and-sort -bastk. * Standards-Version: 4.5.0. * Switch to debhelper-compat (= 11). -- Thomas Goirand Tue, 07 Apr 2020 09:42:49 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922971 Title: Sync python-pyscss 1.3.7-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pyscss/+bug/1922971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922971] Re: Sync python-pyscss 1.3.7-3 (main) from Debian unstable (main)
I agree. The Debian package contains all relevant changes from Ubuntu and is in better shape. ** Changed in: python-pyscss (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922971 Title: Sync python-pyscss 1.3.7-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pyscss/+bug/1922971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923626] Re: Mismatch error in test_barbican.py
LGTM. And I confirmed it fixes the build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923626 Title: Mismatch error in test_barbican.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-barbicanclient/+bug/1923626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927944] Re: Sync cdrkit 9:1.1.11-3.2 (main) from Debian unstable
This bug was fixed in the package cdrkit - 9:1.1.11-3.2 Sponsored for Dave Jones (waveform) --- cdrkit (9:1.1.11-3.2) unstable; urgency=medium * Non-maintainer upload. * debian/patches: Apply patch from Fedora to fix build with GCC 10 (Closes: #957074) -- Sebastian Ramacher Thu, 04 Feb 2021 22:36:29 +0100 ** Changed in: cdrkit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927944 Title: Sync cdrkit 9:1.1.11-3.2 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1927944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927944] Re: Sync cdrkit 9:1.1.11-3.2 (main) from Debian unstable
Thanks! $ syncpackage -f -V 9:1.1.11-3.2 -b 1927944 -s waveform cdrkit Source cdrkit -> impish/Proposed: current version 9:1.1.11-3.1ubuntu2, new version 9:1.1.11-3.2 Using existing file cdrkit_1.1.11-3.2.dsc Using existing file cdrkit_1.1.11-3.1ubuntu2.dsc Using existing file cdrkit_1.1.11-3.2.dsc Using existing file cdrkit_1.1.11-3.1ubuntu2.dsc Downloading changelog from launchpadlibrarian.net (0.059 MiB) New changes: cdrkit (9:1.1.11-3.2) unstable; urgency=medium * Non-maintainer upload. * debian/patches: Apply patch from Fedora to fix build with GCC 10 (Closes: #957074) -- Sebastian Ramacher Thu, 04 Feb 2021 22:36:29 +0100 Sponsoring this sync for Dave Jones (waveform) Sync this package [y|N]? y Request succeeded; you should get an e-mail once it is processed. Launchpad bugs to be closed: 1927944 Please wait for the sync to be successful before closing bugs. Close bugs [Y|n]? Y Closed bug https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1927944 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927944 Title: Sync cdrkit 9:1.1.11-3.2 (main) from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/1927944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
Thank you, LGTM! $ dput ubuntu ../db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes D: Setting host argument. Checking signature on .changes gpg: ../db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes: Valid signature from 5889C17AB1C8D890 Checking signature on .dsc gpg: ../db5.3_5.3.28+dfsg1-0.8ubuntu1.dsc: Valid signature from 5889C17AB1C8D890 Uploading to ubuntu (via sftp to upload.ubuntu.com): Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1.dsc: done. Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1.debian.tar.xz: done. Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1_source.buildinfo: done. Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
** Changed in: db5.3 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923590] Re: Telco Customer needs Minimal ISO with customizable set and versions of packages
Hello Szilard, I don't think this is related to the netplan project, thus I'm marking it invalid and re-assigning it to the cdimage-rootfs project instead. I'm not sure if that is the correct place for this feature request, so feel free to re-assign to a better suited project. Lukas ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923590 Title: Telco Customer needs Minimal ISO with customizable set and versions of packages To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1923590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
** Also affects: netplan.io (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: netplan.io (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu Groovy) Status: New => Confirmed ** Changed in: netplan Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
Defining the netplan.io -> libnetplan0 dependency as "libnetplan0 (=
${binary:Version})" makes it work for this specific "unattended-upgrade
case", but unfortunately the regression is more generic than that...
There are some other consumers of libnetplan0, such as the
NetworkManager snap on Ubuntu Core 20, which will fail in the same way
if the new libnetplan0 v0.102 is in place.
I've used git-bisect to find the relevant commit and even found TWO of them:
1)
https://github.com/canonical/netplan/commit/6c8ed65df7c7f31280d5d27b67195a1e9a746e7a
2)
https://github.com/canonical/netplan/pull/181/commits/4275ade922b63ddacc2db2aba9b413ba71836a04
Commit (2) is part of PR#181, itself part of the huge PR#193:
https://github.com/canonical/netplan/pull/193
If both of them are reverted, the old (v0.101) "generate" binary can be
executed nicely, using the newer (v0.102 + two reverts) library.
Unfortunately, we cannot just revert those commits, as they provide some
of the core functionality of netplan v0.102...
Both commits have in common that they add new data to the
"NetplanNetDefinition struct", making it grow in size. So we're probably
crossing some kind of memory boundary here, breaking the ABI.
I need to dig deeper, in order to find a proper way to solve this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922898
Title:
SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
Previous fix in Hirsute is not enough, so I'm resetting it to "Triaged". ** Changed in: netplan.io (Ubuntu Hirsute) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
** Description changed: + [Impact] + This release contains a regression bug-fix for un-breaking the ABI compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken from a pending upstream pull request: https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898) + + [Test Plan] + The following development and SRU process was followed: + https://wiki.ubuntu.com/NetplanUpdates + + Netplan contains an extensive integration test suite that is ran using + the SRU package for each release. This test suite's results are available here: + http://autopkgtest.ubuntu.com/packages/n/netplan.io + + A successful run is required before the proposed netplan.io package + can be let into -updates. + + The netplan team will be in charge of attaching the artifacts and console + output of the appropriate run to the bug. Netplan team members will not + mark ‘verification-done’ until this has happened. + + Additionally, we want to manually verify the ABI compatibility (i.e. not + SEGFAULT) between the new libnetplan and the old netplan.io "generate" + binary, with the steps described below: + + * Have netplan 0.101 installed + * Upgrade ONLY libnetplan0 to 0.102 + $ cat /etc/netplan/00-config.yaml + network: + ethernets: + ens5: + dhcp4: true + dhcp6: false + match: + macaddress: 06:f8:32:e5:34:28 + set-name: ens5 + version: 2 + $ /usr/lib/netplan/generate + * Make sure the "generate" binary did not crash. + + [Where problems could occur] + Netplan being a core package it could impact the whole networking stack of the operating system up to the point where servers would not be reachable anymore after a reboot, due to broken network config being generated by netplan at bootup. In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. + + Additionally, this SRU needs to drop the "Added ttl option for tunnels + (LP: #1846783)" feature, added during the 0.102/Hirsute development + cycle. So users of the -devel series using the new "tunnels.ttl" + setting are going to miss this until it is re-implemented in an ABI + preserving way. + + Hirsute (Bileto pre-test): + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/amd64/n/netplan.io/20210416_204928_fec70@/log.gz + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/arm64/n/netplan.io/20210416_213837_fec70@/log.gz + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/armhf/n/netplan.io/20210416_201636_fec70@/log.gz + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/ppc64el/n/netplan.io/20210416_210302_fec70@/log.gz + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/s390x/n/netplan.io/20210416_204523_fec70@/log.gz + + Groovy: + TBD groovy_amd64.log + TBD groovy_arm64.log + TBD groovy_armhf.log + TBD groovy_ppc64el.log + TBD groovy_s390x.log + + Focal: + TBD focal_amd64.log + TBD focal_arm64.log + TBD focal_armhf.log + TBD focal_ppc64el.log + TBD focal_s390x.log + + [Other Info] + The integration test logs are attached to this bug, once the package has been accepted into -proposed and the tests have been executed on the real infrastructure. + + == Original description == + Today a bunch of our ubuntu 20.04 servers on AWS EC2 (both amd64 and arm) upgraded to netplan 0.102-0ubuntu1~20.04.1, which resulted in a segfault when netplan ran generate, and then took the whole network down with it, the servers had to be force rebooted. kernel: [1938106.074273] netplan[2874371]: segfault at 1 ip 7f72cb991675 sp 7ffe8be03158 error 4 in libc-2.31.so[7f72cb82b000+178000] kernel: [1938106.074282] Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 2b fd 74 0f c5 fd d7 c1 85 c0 0f 85 eb 00 00 00 48 83 c7 20 83 e1 systemd[2874368]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. /etc/netplan/ is the default from aws ubuntu 20.04 image. ** Summary changed: - SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 + [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing lis
[Bug 1925034] [NEW] Please remove src:aws-shell
Public bug reported: Removal request --- Please remove the "aws-shell" source package from the archive. It fails to build from scratch, has been removed from Debian testing and seems rather unmaintained upstream. The FTBFS failure has been reported upstream: https://github.com/awslabs /aws-shell/issues/254 The binary package names are: aws-shell The (release) arch that should get targeted for removal is: source It was removed from Debian as well: https://tracker.debian.org/news/1095837/aws-shell-removed-from-testing/ It does not have reverse depends: $ reverse-depends -b aws-shell No reverse dependencies found Extended removal reason: aws-shell depends on prompt-toolkit 1.0, last released in Oct 2019. It was not updated to support the new major versions of prompt-toolkit 2.x or 3.x ** Affects: aws-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: Removal request --- Please remove the "aws-shell" source package from the archive. It fails to build from scratch, has been removed from Debian testing and seems rather unmaintained upstream. The FTBFS failure has been reported upstream: https://github.com/awslabs /aws-shell/issues/254 - The binary package names are: aws-shell The (release) arch that should get targeted for removal is: source It was removed from Debian as well: https://tracker.debian.org/news/1095837/aws-shell-removed-from-testing/ + It does not have reverse depends: + $ reverse-depends -b aws-shell + No reverse dependencies found + Extended removal reason: aws-shell depends on prompt-toolkit 1.0, last released in Oct 2019. It was not updated to support the new major versions of prompt-toolkit 2.x or 3.x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925034 Title: Please remove src:aws-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aws-shell/+bug/1925034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925212] [NEW] FTBFS with GCC-11
Public bug reported: bayecomepp failed to build from scratch in the latest archive rebuild, using GCC-11: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210325-hirsute-hirsute.html Attached is a patch for fixing the problem, which should be uploaded after the Hirsute final freeze. ** Affects: baycomepp (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs ** Patch added: "CHANGES.debdiff" https://bugs.launchpad.net/bugs/1925212/+attachment/5490157/+files/CHANGES.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925212 Title: FTBFS with GCC-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baycomepp/+bug/1925212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925214] [NEW] FTBFS on armhf (and other 32bit arch)
Public bug reported: Upstream badger does not have good support for 32bit architectures, therefore the armhf binary was removed in Groovy. See: https://pad.lv/1884753 https://github.com/dgraph-io/badger/issues/1384 This bug is here for reference of the 32bit FTBFS issue, so we do not re-investigate this with every archive rebuild. ** Affects: badger (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925214 Title: FTBFS on armhf (and other 32bit arch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/badger/+bug/1925214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925212] Re: FTBFS with GCC-11
** Bug watch added: Debian Bug tracker #987250 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987250 ** Also affects: baycomepp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987250 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925212 Title: FTBFS with GCC-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baycomepp/+bug/1925212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
** Description changed: [Impact] This release contains a regression bug-fix for un-breaking the ABI compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken from a pending upstream pull request: https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898) [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each release. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan.io package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Additionally, we want to manually verify the ABI compatibility (i.e. not SEGFAULT) between the new libnetplan and the old netplan.io "generate" binary, with the steps described below: * Have netplan 0.101 installed * Upgrade ONLY libnetplan0 to 0.102 $ cat /etc/netplan/00-config.yaml network: - ethernets: - ens5: - dhcp4: true - dhcp6: false - match: - macaddress: 06:f8:32:e5:34:28 - set-name: ens5 - version: 2 + ethernets: + ens5: + dhcp4: true + dhcp6: false + match: + macaddress: 06:f8:32:e5:34:28 + set-name: ens5 + version: 2 $ /usr/lib/netplan/generate * Make sure the "generate" binary did not crash. [Where problems could occur] Netplan being a core package it could impact the whole networking stack of the operating system up to the point where servers would not be reachable anymore after a reboot, due to broken network config being generated by netplan at bootup. In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. Additionally, this SRU needs to drop the "Added ttl option for tunnels (LP: #1846783)" feature, added during the 0.102/Hirsute development cycle. So users of the -devel series using the new "tunnels.ttl" setting are going to miss this until it is re-implemented in an ABI preserving way. Hirsute (Bileto pre-test): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/amd64/n/netplan.io/20210416_204928_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/arm64/n/netplan.io/20210416_213837_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/armhf/n/netplan.io/20210416_201636_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/ppc64el/n/netplan.io/20210416_210302_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/s390x/n/netplan.io/20210416_204523_fec70@/log.gz Groovy: TBD groovy_amd64.log TBD groovy_arm64.log TBD groovy_armhf.log TBD groovy_ppc64el.log TBD groovy_s390x.log Focal: - TBD focal_amd64.log - TBD focal_arm64.log - TBD focal_armhf.log - TBD focal_ppc64el.log - TBD focal_s390x.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_amd64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_arm64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_armhf.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_ppc64el.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_s390x.log [Other Info] The integration test logs are attached to this bug, once the package has been accepted into -proposed and the tests have been executed on the real infrastructure. == Original description == Today a bunch of our ubuntu 20.04 servers on AWS EC2 (both amd64 and arm) upgraded to netplan 0.102-0ubuntu1~20.04.1, which resulted in a segfault when netplan ran generate, and then took the whole network down with it, the servers had to be force rebooted. kernel: [1938106.074273] netplan[2874371]: segfault at 1 ip 7f72cb991675 sp 7ffe8be03158 error 4 in libc-2.31.so[7f72cb82b000+178000] kernel: [1938106.074282] Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 2b fd 74 0f c5 fd d7 c1 85 c0 0f 85 eb 00 00 00 48 83 c7 20 83 e1 systemd[2874368]: /usr/lib/systemd/syste
[Bug 1919453] Re: [SRU][FFe] Update to netplan.io 0.102
** Description changed: [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to those improvements. The most notable changes (besides usual bug-fixes) incoming in 0.102: - New API for NetworkManager YAML backend - Improved netplan set CLI to override existing files - Documentation improvements - Allow running more tests in a container - Added congestion-window & advertised-receive-window options for routes - Added ttl option for tunnels (LP: #1846783) - systemd v247 compatibility (for changing MAC address) - Prevent duplicate ARPIPTargets in NetDev files (LP: #1915837) - Enable pristine-tar in gbp See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each release. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan.io package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. [Where problems could occur] Netplan being a core package it could impact the whole networking stack of the operating system up to the point where servers would not be reachable anymore after a reboot, due to broken network config being generated by netplan at bootup. In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug: Groovy: https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/groovy_s390x.log Focal: - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/focal_amd64.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/focal_arm64.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/focal_armhf.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/focal_ppc64el.log - https://git.launchpad.net/~slyon/+git/files/tree/LP1919453/focal_s390x.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_amd64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_arm64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_armhf.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_ppc64el.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_s390x.log [Other Info] The integration test logs are attached to this bug, once the package has been accepted into -proposed and the tests have been executed on the real infrastructure. [Changelog] abad253 tests:bonds: fix flaky resend_igmp test 6270143 tests:base: avoid long waits b98a160 tests:base: improve daemon-reload check 3f19eeb tests:base: improve reliabilty by using higher timeout a049983 tests:base: improve management interface handling 8cb8621 test:utils: cleanup formatting e05731c cli:set: write to existing YAML file, if available (#197) 2263a13 libnetplan: provide API for NetworkManager YAML backend (#193) d34df50 test:tunnels: improve stability of wireguard test 15a3380 Prevent duplicate ARPIPTargets in NetDev files (LP: #1915837) (#199) 2ccddbe tests:integration: cleanup OVS/WPA files (#198) 9767b63 Improve integration tests (#196) f086808 Enable CodeQL code scanning (#195) 6c8ed65 Added TTL option for tunnels (LP: #1846783) (#194) 1e0f223 Added per route congestion-window/advertised-receive-window options (#177) ac2a1b9 Update Github URL (#192) 165e908 cli:utils: handle emtpy netifaces.ifaddresess call (#188) 51a6032 Stop using deprecated systemd-resolve tool d9d35c6 cli:apply: Add comment about snapd/DBus compatibility bdc2b1d Clarified `dhcp-identifier` option (#186) 1413f0e tests:integration: adopt for racy systemd MAC assignment 222c104 github: run action on any pull request 03746b4 tests:dbus: improve test stability of timeouts 465c530 tests:tunnels: improve test reliability 944b1e3 tests: adopt to wording changes as of OVS 2.15 86bd330 doc: Add a caveat to wake on LAN which is systemd.link related (LP: #1909114) (#180) 41bfbd6 parse: fix 'networkmanager:' backend options for modem connections (#179) 85ff2f5 Fix changing of macaddress with systemd v247 (#178) 47ad3cc Cleanup unused code, as noted by clang 72e11a6 parse:doc:test: fix typos (thanks lintian)
[Bug 1919453] Re: [SRU][FFe] Update to netplan.io 0.102
I re-verified the Focal SRU (0.102-0ubuntu1~20.04.2) and updated the corresponding test logs for Focal in the bug description. The logs are the same as in LP: #1922898 (same package, version & tests). All tests passed on first run. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919453 Title: [SRU][FFe] Update to netplan.io 0.102 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1919453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
Thank you very much Brian, for quickly accepting the regression fix into focal-proposed! I verified the Focal SRU (for 0.102-0ubuntu1~20.04.2) and attached the corresponding test logs to the bug description. Furthermore, I've verified the regression case, where libnetplan0 v0.102 is used with the netplan.io "generate" binary v0.101, which also passes (i.e. does not crash anymore): root@ff:~# dpkg -l | grep netplan ii libnetplan0:amd64 0.102-0ubuntu1~20.04.2 amd64 ii netplan.io 0.101-0ubuntu3~20.04.2 amd64 root@ff:~# cat /etc/netplan/00-config.yaml network: ethernets: ens5: dhcp4: true dhcp6: false match: macaddress: 06:f8:32:e5:34:28 set-name: ens5 version: 2 root@ff:~# /usr/lib/netplan/generate root@ff:~# echo $? 0 As you can see the "generate" binary does not crash with "Segmentation fault (core dumped)" anymore when using libnetplan0 0.102-0ubuntu1~20.04.2 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910830] Re: atlas FTBFS with GFortran 10 (groovy and hirsute)
The build failure is fixed in Debian, but it requires a complex merge, including special handling of s390x instruction set and cross-compilation of Z14 on Z13. Also, there are some incompatibilities between the new debhelper-compat 13 and the previous dh-exec logic. I prepared a merge from Debian in a PPA, this fixes the FTBFS: https://launchpad.net/~slyon/+archive/ubuntu/plusone-hh-freeze/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910830 Title: atlas FTBFS with GFortran 10 (groovy and hirsute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atlas/+bug/1910830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922898] Re: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
** Tags added: verification-needed-hirsute ** Changed in: netplan.io (Ubuntu Hirsute) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
Thanks William, this LGTM now! I've modified your debian/changelog and the XML/man pages a bit, to account for the removed handling of floating point numbers. And uploaded the package. $ dput ubuntu ../shadow_4.8.1-1ubuntu9_source.changes D: Setting host argument. Checking signature on .changes gpg: ../shadow_4.8.1-1ubuntu9_source.changes: Valid signature from 5889C17AB1C8D890 Checking signature on .dsc gpg: ../shadow_4.8.1-1ubuntu9.dsc: Valid signature from 5889C17AB1C8D890 Uploading to ubuntu (via sftp to upload.ubuntu.com): Uploading shadow_4.8.1-1ubuntu9.dsc: done. Uploading shadow_4.8.1-1ubuntu9.debian.tar.xz: done. Uploading shadow_4.8.1-1ubuntu9_source.buildinfo: done. Uploading shadow_4.8.1-1ubuntu9_source.changes: done. Successfully uploaded packages. https://launchpad.net/ubuntu/+source/shadow/1:4.8.1-1ubuntu9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
** Changed in: networkd-dispatcher (Ubuntu Hirsute) Status: Triaged => In Progress ** Changed in: networkd-dispatcher (Ubuntu Focal) 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/1884248 Title: [SRU] networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
Thank you very much for providing the debdiffs! They are looking good so far. In the -signed package, you wouldn't even need to adopt the s390-tools- zkey version manually as that would be generated from debian/control.in But it's perfectly fine doing it this way as well! For s390-tools I have a few minor remarks: * Please add a libkmipclient1.symbols (https://wiki.debian.org/UsingSymbolsFiles) if possible. * Please Fix the hsavmcore & lshwc typos in debian/changelog * Please mention the new libxml2-dev build-dep in debian/changelog * Please mention that you refreshed the patches in debian/changelog From what I can see you refreshed all patches, which introduced some unrelated patch header/footer changes, especially in: 0001-dumpconf-Don-t-run-the-service-in-LXC.patch debian/patches/bashism.patch debian/patches/install-iucvterm.patch => This refresh make the patches cleaner, removing the versioned directory path. So I think we can keep it as is (especially if it is mentioned in the changelog), but usually we try to avoid unrelated changes. I saw that there is an unused patch in debian/patches/disable.patch.DEBIAN, which seems to be a leftover from the past, maybe we could clear/delete that one and mention it in the changelog, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
Hello Brian,
thank you for accepting it into hirsute-proposed. I tested networkd-
dispatcher 2.1-2~ubuntu21.04.1 and can confirm the bug is fixed:
# dpkg -l | grep systemd
ii systemd 247.3-3ubuntu3.1
# networkctl status eth0
● 149: eth0
Link File: n/a
Network File: /run/systemd/network/10-netplan-eth0.network
Type: ether
State: routable (configured)
HW Address: 00:16:3e:5c:cd:0c (Xensource, Inc.)
MTU: 1500 (min: 68, max: 65535)
QDisc: noqueue
IPv6 Address Generation Mode: eui64
Queue Length (Tx/Rx): 1/1
Auto negotiation: no
Speed: 10Gbps
Duplex: full
Port: tp
Address: 10.238.94.22 (DHCP4 via 10.238.94.1)
fd42:7213:f20e:bd74:216:3eff:fe5c:cd0c
fe80::216:3eff:fe5c:cd0c
Gateway: 10.238.94.1 (Xensource, Inc.)
fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)
DNS: 10.238.94.1
fe80::216:3eff:fe0f:ee29
Search Domains: lxd
Activation Policy: up
DHCP4 Client ID: 0:16:3e:5c:cd:c
DHCP6 Client IAID: 0x31b8204f
DHCP6 Client DUID: DUID-EN/Vendor:ab1178959fc6ef55425f
# cat /etc/networkd-dispatcher/routable.d/00run.sh
#!/bin/bash
env > /tmp/out.log
# chmod +x /etc/networkd-dispatcher/routable.d/00run.sh
# networkd-dispatcher --run-startup-triggers
# cat /tmp/out.log | grep "\"Address\""
json={"Activation Policy": ["up"], "Address": ["10.238.94.22",
"fd42:7213:f20e:bd74:216:3eff:fe5c:cd0c", "fe80::216:3eff:fe5c:cd0c"],
"AdministrativeState": "configured", "Auto negotiation": ["no"], "DHCP4 Client
ID": ["0:16:3e:5c:cd:c"], "DHCP6 Client DUID":
["DUID-EN/Vendor:ab1178959fc6ef55425f"], "DHCP6 Client IAID":
["0x31b8204f"], "DNS": ["10.238.94.1", "fe80::216:3eff:fe0f:ee29"], "Duplex":
["full"], "Gateway": ["10.238.94.1 (Xensource, Inc.)",
"fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)"], "HW Address":
["00:16:3e:5c:cd:0c (Xensource, Inc.)"], "IPv6 Address Generation Mode":
["eui64"], "InterfaceName": "eth0", "Jul 14 07:02:23 hh systemd-networkd[82]":
["eth0: DHCPv4 address 10.238.94.22/24 via 10.238.94.1"], "Jul 14 07:02:24 hh
systemd-networkd[82]": ["eth0: Gained IPv6LL"], "Jul 14 07:03:10 hh
systemd-networkd[1855]": ["eth0: Gained IPv6LL", "eth0: DHCPv4 address
10.238.94.22/24 via 10.238.94.1"], "Jul 14 07:03:10 hh systemd-networkd[82]":
["eth0: DHCPv6 lease lost"], "Link File": ["n/a"], "MTU": ["1500 (min: 68, max:
65535)"], "Network File": ["/run/systemd/network/10-netplan-eth0.network"],
"OperationalState": "routable", "Port": ["tp"], "QDisc": ["noqueue"], "Queue
Length (Tx/Rx)": ["1/1"], "Search Domains": ["lxd"], "Speed": ["10Gbps"],
"State": "routable (configured)", "Type": "ether"}
As we can see Address is just "10.238.94.22" without any "(DHCP4.*)" suffix.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
** Changed in: networkd-dispatcher (Ubuntu Groovy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
[SRU] networkd-dispatcher gives corrupted information
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
This bug does not happen for Bionic, as the networkctl output was only changed in systemd v244 while Bionic is on v237. ** Changed in: networkd-dispatcher (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884248 Title: [SRU] networkd-dispatcher gives corrupted information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
** Description changed:
[Impact]
- * Due to changes in systemd's networkctl output networkd-dispatcher 2.0
contains a bug, producing invalid keys/values inside the JSON it provides to
its scripts
- * e.g.: json={"A": ["ress: 119.224.106.22 (DHCP4)"], ...}
- * Therefore the scripts cannot access the relevant network configuration
state
-
+ * Due to changes in systemd's networkctl output networkd-dispatcher 2.0
contains a bug, producing invalid keys/values inside the JSON it provides to
its scripts
+ * e.g.: json={"A": ["ress: 119.224.106.22 (DHCP4)"], ...}
+ * Therefore the scripts cannot access the relevant network configuration
state
[Test Plan]
- * Run systemd v244+ (e.g. in a LXD container)
- * Make sure you got an IP address via DHCP:
- * # networkctl status eth0
- ● 120: eth0
- Link File: /usr/lib/systemd/network/99-default.link
- Network File: /run/systemd/network/10-netplan-eth0.network
- Type: ether
- State: routable (configured)
- Driver: veth
- HW Address: 00:16:3e:0b:d7:74 (Xensource, Inc.)
-MTU: 1500 (min: 68, max: 65535)
- Queue Length (Tx/Rx): 1/1
- Auto negotiation: no
- Speed: 10Gbps
- Duplex: full
- Port: tp
-Address: 10.238.94.146 (DHCP4)
- fd42:7213:f20e:bd74:216:3eff:fe0b:d774
- fe80::216:3eff:fe0b:d774
-Gateway: 10.238.94.1 (Xensource, Inc.)
- fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)
-DNS: 10.238.94.1
- fd42:7213:f20e:bd74::1
- fe80::216:3eff:fe0f:ee29
- Search Domains: lxd
- Activation Policy: up
- * # cat /etc/networkd-dispatcher/routable.d/00run.sh
+ * Run systemd v244+ (e.g. in a LXD container)
+ * Make sure you got an IP address via DHCP:
+ * # networkctl status eth0
+ ● 120: eth0
+ Link File: /usr/lib/systemd/network/99-default.link
+ Network File: /run/systemd/network/10-netplan-eth0.network
+ Type: ether
+ State: routable (configured)
+ Driver: veth
+ HW Address: 00:16:3e:0b:d7:74 (Xensource, Inc.)
+ MTU: 1500 (min: 68, max: 65535)
+ Queue Length (Tx/Rx): 1/1
+ Auto negotiation: no
+ Speed: 10Gbps
+ Duplex: full
+ Port: tp
+ Address: 10.238.94.146 (DHCP4)
+ fd42:7213:f20e:bd74:216:3eff:fe0b:d774
+ fe80::216:3eff:fe0b:d774
+ Gateway: 10.238.94.1 (Xensource, Inc.)
+ fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)
+ DNS: 10.238.94.1
+ fd42:7213:f20e:bd74::1
+ fe80::216:3eff:fe0f:ee29
+ Search Domains: lxd
+ Activation Policy: up
+ * # cat /etc/networkd-dispatcher/routable.d/00run.sh
#!/bin/bash
env > /tmp/out.log
- * chmod +x /etc/networkd-dispatcher/routable.d/00run.sh
- * # networkd-dispatcher --run-startup-triggers
- * cat /tmp/out.log
- * Check json= ENV to verify if it contains the correct IPv4 address (without
"(DHCP4)" suffix).
+ * chmod +x /etc/networkd-dispatcher/routable.d/00run.sh
+ * # networkd-dispatcher --run-startup-triggers
+ * cat /tmp/out.log
+ * Check json= ENV to verify if it contains the correct IPv4 address (without
"(DHCP4)" suffix).
[Where problems could occur]
- * This was broken in 2.0 and the fix changes the behavior back to what was
originally intended.
- * If people adopted to the broken environment variable, to somehow parse the
information they need from the broken JSON, this change will most probably
break their networkd-dispatcher scripts (again).
-
+ * This was broken in 2.0 and the fix changes the behavior back to what was
originally intended.
+ * If people adopted to the broken environment variable, to somehow parse the
information they need from the broken JSON, this change will most probably
break their networkd-dispatcher scripts (again).
[Other Info]
-
- * The upstream version 2.1 just fixes the parsing of current networkctl
output (in addition to a few testing and document
[Bug 1934988] Re: Upgrade s390-tools to latest version (2.17.0)
Thanks, uploaded! ** Changed in: s390-tools (Ubuntu Impish) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934988 Title: Upgrade s390-tools to latest version (2.17.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1934988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884248] Re: [SRU] networkd-dispatcher gives corrupted information
Hello Brian,
thank you for accepting it into focal-proposed. I tested networkd-
dispatcher 2.1-2~ubuntu20.04.1 and can confirm the bug is fixed:
# dpkg -l | grep systemd
ii systemd 245.4-4ubuntu3.7
# networkctl status eth0
● 258: eth0
Link File: /usr/lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-eth0.network
Type: ether
State: routable (configured)
Driver: veth
HW Address: 00:16:3e:0b:d7:74 (Xensource, Inc.)
MTU: 1500 (min: 68, max: 65535)
Queue Length (Tx/Rx): 1/1
Auto negotiation: no
Speed: 10Gbps
Duplex: full
Port: tp
Address: 10.238.94.146 (DHCP4)
fd42:7213:f20e:bd74:216:3eff:fe0b:d774
fe80::216:3eff:fe0b:d774
Gateway: 10.238.94.1 (Xensource, Inc.)
fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)
DNS: 10.238.94.1
fd42:7213:f20e:bd74::1
fe80::216:3eff:fe0f:ee29
Search Domains: lxd
Activation Policy: up
# cat /etc/networkd-dispatcher/routable.d/00run.sh
#!/bin/bash
env > /tmp/out.log
# chmod +x /etc/networkd-dispatcher/routable.d/00run.sh
# networkd-dispatcher --run-startup-triggers
# grep "\"Address\"" /tmp/out.log
json={"Activation Policy": ["up"], "Address": ["10.238.94.146",
"fd42:7213:f20e:bd74:216:3eff:fe0b:d774", "fe80::216:3eff:fe0b:d774"],
"AdministrativeState": "configured", "Auto negotiation": ["no"], "DNS":
["10.238.94.1", "fd42:7213:f20e:bd74::1", "fe80::216:3eff:fe0f:ee29"],
"Driver": ["veth"], "Duplex": ["full"], "Gateway": ["10.238.94.1 (Xensource,
Inc.)", "fe80::216:3eff:fe0f:ee29 (Xensource, Inc.)"], "HW Address":
["00:16:3e:0b:d7:74 (Xensource, Inc.)"], "InterfaceName": "eth0", "Jul 15
07:20:21 ff systemd-networkd[86]": ["eth0: IPv6 successfully enabled", "eth0:
DHCPv4 address 10.238.94.146/24 via 10.238.94.1"], "Jul 15 07:20:22 ff
systemd-networkd[86]": ["eth0: Gained IPv6LL"], "Link File":
["/usr/lib/systemd/network/99-default.link"], "MTU": ["1500 (min: 68, max:
65535)"], "Network File": ["/run/systemd/network/10-netplan-eth0.network"],
"OperationalState": "routable", "Port": ["tp"], "Queue Length (Tx/Rx)":
["1/1"], "Search Domains": ["lxd"], "Speed": ["10Gbps"], "State": "routable
(configured)", "Type": "ether"}
As we can see Address is just "10.238.94.146" without any "(DHCP4)"
suffix.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884248
Title:
[SRU] networkd-dispatcher gives corrupted information
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1884248/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
Thanks, I've sponsored the HH & FF uploads. ** Changed in: shadow (Ubuntu Focal) Status: Fix Committed => In Progress ** Changed in: shadow (Ubuntu Hirsute) Status: Fix Committed => 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/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936312] [NEW] nm-online times out, failing autopkgtests
Public bug reported: The nm-online util does not return successfully as of 1.32.2-0ubuntu1 (currently in impish-proposed). systemd VS network-manager autopkgtests (in LXD) fail, because the autopkgtest-virt-lxd runner tries to wait for "network ready" before it is reconnecting after a reboot. This happens by checking the 'systemctl start network-online.target' command, in turn executing the 'nm-online -s -q' util (via NetworkManager-wait-online.service), in addition to systemd-networkd-wait-online.service (which seems to be working OK). nm-online does not return successfully anymore as of 1.32.2-0ubuntu1, but it times out. That is a regression compared to v1.30. Reproducer: $ lxc launch ubuntu-daily:impish test $ lxc exec test bash # apt install network-manager #(version 1.30.0-1ubuntu4) # time systemctl start network-online.target real0m0.071s user0m0.021s sys 0m0.023s # time nm-online -s Connecting... 30s [started] real0m0.043s user0m0.027s sys 0m0.006s root@test:~# echo $? 0 Everything is OK up to here. # vim /etc/apt/sources.list #(enable impish-proposed) # apt update && apt install network-manager #(1.32.2-0ubuntu1) # time nm-online -s Connecting...0s [startup-pending] real0m30.019s user0m0.021s sys 0m0.014s # time systemctl start network-online.target real1m0.104s user0m0.013s sys 0m0.023s # journalctl -u NetworkManager | grep startup Jul 15 09:05:06 test NetworkManager[1912]: [1626339906.6507] manager: startup complete root@test:~# NetworkManager -V 1.32.2 root@test:~# nm-online -s Connecting...0s [startup-pending] root@test:~# echo $? 1 root@test:~# nm-online Connecting...0s [offline] root@test:~# echo $? 1 The journal log contains the "startup completed" line, so 'nm-online -s' should return immediately. But as we can see, nm-online fails (after a timeout) and thus blocks network-online.target, failing the systemd autopkgtests (in LXD). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936312 Title: nm-online times out, failing autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936312] Re: nm-online times out, failing autopkgtests
Related to: LP: #1914062 Two patches exist, both were dropped from their corresponding packages: https://git.launchpad.net/network-manager/commit/?id=4c4f7172 https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?h=ubuntu- impish&id=efebddfe37efff6a259ef7fd59212d65ad1b848b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936312 Title: nm-online times out, failing autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860672] Re: Autopkgtest failing badly since linux-5.4/5.4.0-11.14
It looks like this error happens when the package is only available in -proposed, but not the release pocket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860672 Title: Autopkgtest failing badly since linux-5.4/5.4.0-11.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935666] Re: s390-tools FTBFS when built with libfuse3-dev
Upstream patch: https://github.com/ibm-s390-linux/s390-tools/pull/117 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935666 Title: s390-tools FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1935666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929150] Re: new version fails to start if eth0 not present
** Bug watch added: Debian Bug tracker #895342 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342 ** Also affects: suricata (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895342 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929150 Title: new version fails to start if eth0 not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/suricata/+bug/1929150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936312] Re: nm-online times out, failing autopkgtests
This should have been fixed upstream by: https://github.com/systemd/systemd/pull/18559 Or https://github.com/systemd/systemd/pull/18684 and https://github.com/systemd/systemd/pull/18717 respectively. I wonder why this fix isn't working for network-manager, while it seems to be good for LXD? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936312 Title: nm-online times out, failing autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936312] Re: nm-online times out, failing autopkgtests
After reading a bit more about this issue, I can see where the conflict happens: 1/ systemd requires any container manager to mount /sys read-only, according to https://systemd.io/CONTAINER_INTERFACE/ in order to make udevd behave properly. 2/ NetworkManager checks for /sys to be read-only in order to decide if it should not be using udev 3/ lxc has a different understanding (and requirements), so it mounts /sys r/w, leading to confusion in NetworkManager. => IMO NetworkManager needs to do an improved check if it is running inside a container (in addition to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/78dc57d8f4af1a230053473f3eb7c18d1eaf0730) as the /sys read-only check is not enough for the LXC environment. Maybe NM could be extended to check for something like "systemd-detect-virt --container == 0" and not use udev in this case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936312 Title: nm-online times out, failing autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
After enabling the unified cgroups hierarchy in systemd and running some tests, I can confirm that most things are working as expected, except for snapd. https://bileto.ubuntu.com/excuses/4602/impish.html The Bileto autopkgtests show (ignoring two unrelated/flaky failures in universe packages: suricata & mosquitto) that: * The systemd "tests-in-lxd" test fails, for snapd's "WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement" stderr output. If that stderr output is muted/ignored (by modifying autopkgtests itself) the test passes, as tested locally. * The snapd "autopkgtest:adt-local:tests/smoke/sandbox" spread test fails with an "all ubuntu systems must have strict confinement" error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934221] Re: systemd-resolve segfault
Thank you for providing a patch! That patch looks straight forward and
(almost) resembles the upstream change, obviously missing the parts that
do not yet exist in systemd v245.
The only other thing I found missing is an upstream change in
src/resolve/resolved-dns-transaction.c:
```
static void dns_transaction_stop_timeout(DnsTransaction *t) {
assert(t);
-t->timeout_event_source =
sd_event_source_unref(t->timeout_event_source);
+t->timeout_event_source =
sd_event_source_disable_unref(t->timeout_event_source);
}
DnsTransaction* dns_transaction_free(DnsTransaction *t) {
```
I've created a new patch for Focal, including this change and also
adopted the patch to Hirsute.
I have a few open questions:
1/ Did you leave that out that resolved-dns-transaction.c change on purpose?
2/ What is the best way to reproduce this issue? Can it somehow be triggerd?
3/ How to test/confirm that the issue is indeed fixed? Is there any way other
than observing for 24 hours?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934221] Re: systemd-resolve segfault
** Patch added: "Focal" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512235/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch ** Also affects: systemd (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934221] Re: systemd-resolve segfault
systemd v248 as can be found in Impish already contains the upstream fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936948] [NEW] Dependency loop via sockets.target
Public bug reported: basic.target waits for dbus.socket (via sockets.target) AND dbus.socket waits for basic.target, too, delaying dbus-daemon startup. At some point a timeout happens, dbus is started and all queued services try to start registering to the bus at the same time. All services registering at the same time, seems to be triggering bugs like this more often: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/ This happens since Hirsute (dbus 1.12.20-1ubuntu3), where the following delta was added: Index: dbus-1.12.20/bus/dbus.socket.in === --- dbus-1.12.20.orig/bus/dbus.socket.in +++ dbus-1.12.20/bus/dbus.socket.in @@ -1,5 +1,9 @@ [Unit] Description=D-Bus System Message Bus Socket +# Do not stop on shutdown +DefaultDependencies=no +Wants=sysinit.target +After=sysinit.target basic.target [Socket] ListenStream=@DBUS_SYSTEM_SOCKET@ ** Affects: dbus (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/1936948 Title: Dependency loop via sockets.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936948] Re: Dependency loop via sockets.target
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936948 Title: Dependency loop via sockets.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1936948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934221] Re: systemd-resolve segfault
** Patch added: "Hirsute" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512243/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934221] Re: systemd-resolve segfault
** Description changed: - systemd-resolve keep crashing and it is very annoying as sometimes it - severely interrupt normal dns resolving. + [Impact] + + * systemd-resolved stops replying to clients on the local LAN. + * logging segfault crashes in dmesg: + [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] + [836786.046524] Code: Bad RIP value. + [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] + [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] + [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 + + * The upload backports the upstream fix + (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. + + [Test Plan] + + * Setup /etc/systemd/resolved.conf: + [Resolve] + DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net + DNSSEC=yes + DNSOverTLS=opportunistic + MulticastDNS=no + LLMNR=no + Cache=yes + DNSStubListener=yes + Domains=~. + + * wait for ~24-48 hours and observe if any crash happens + + [Where problems could occur] + + * Any regression would likely cause crashes in systemd-resolved, making + it unresponsive to DNS network name requests to local applications. + + [Other Info] + + * Reported upstream: https://github.com/systemd/systemd/issues/18427 + * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 + + === Original description === + + + systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 - Typical error in dmesg: + Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd /libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919451] Re: Update (python-)zhmcclient to latest release
** Also affects: zhmcclient (Ubuntu Focal) 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/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919451] Re: Update (python-)zhmcclient to latest release
** Description changed: + [Impact] + + In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE + III (or newer) machines/LPARs from within a MAAS controller, the + python3-zhmcclient libraray (>= v0.29) is needed, to provide all the + functions required for controlling the HMC. + + [Test Plan] + * setup a MAAS controller inside a LPAR + * use that controller to deploy a new Ubuntu Server instance in an additional LPAR + * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR) + * Power-cycle the LPAR instance + * Power-cycle the KVM instance + + Also get confirmation from the MAAS team that things are working as + expected. + + [Where problems could occur] + + This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller. + This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either. + + [Other Info] + + https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z + + + === Original description === + While working on MAAS DPM/LPAR it turned out that a newer python- zhmcclient (package zhmcclient) is needed to get certain functions work, like especially storage group support. The latest is package is v0.27 on hirsute and v0.22 on focal. v0.28 is currently the latest release, but 0.29 is coming shortly. https://github.com/zhmcclient/python-zhmcclient/issues/731 Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates). Please notice that MAAS was the only reason why the zhmcclient package was created at all. The updated package is especially needed for focal, since focal is the recommended base distro for MAAS DPM/LPAR, hence this would require a special SRU (for this package version bump). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919451] Re: Update (python-)zhmcclient to latest release
** Description changed: [Impact] In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE III (or newer) machines/LPARs from within a MAAS controller, the python3-zhmcclient libraray (>= v0.29) is needed, to provide all the functions required for controlling the HMC. [Test Plan] - * setup a MAAS controller inside a LPAR - * use that controller to deploy a new Ubuntu Server instance in an additional LPAR - * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR) - * Power-cycle the LPAR instance - * Power-cycle the KVM instance + * setup a MAAS controller inside a LPAR + * use that controller to deploy a new Ubuntu Server instance in an additional LPAR + * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR) + * Power-cycle the LPAR instance + * Power-cycle the KVM instance Also get confirmation from the MAAS team that things are working as expected. [Where problems could occur] This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller. This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either. [Other Info] - - https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z + * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z + * The new package dependencies are fulfilled in Focal: + - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main) + - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main) === Original description === While working on MAAS DPM/LPAR it turned out that a newer python- zhmcclient (package zhmcclient) is needed to get certain functions work, like especially storage group support. The latest is package is v0.27 on hirsute and v0.22 on focal. v0.28 is currently the latest release, but 0.29 is coming shortly. https://github.com/zhmcclient/python-zhmcclient/issues/731 Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates). Please notice that MAAS was the only reason why the zhmcclient package was created at all. The updated package is especially needed for focal, since focal is the recommended base distro for MAAS DPM/LPAR, hence this would require a special SRU (for this package version bump). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919451] Re: Update (python-)zhmcclient to latest release
** Changed in: zhmcclient (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919451] Re: Update (python-)zhmcclient to latest release
** Description changed: [Impact] In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM LinuxONE III (or newer) machines/LPARs from within a MAAS controller, the python3-zhmcclient libraray (>= v0.29) is needed, to provide all the functions required for controlling the HMC. [Test Plan] * setup a MAAS controller inside a LPAR * use that controller to deploy a new Ubuntu Server instance in an additional LPAR * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR) * Power-cycle the LPAR instance * Power-cycle the KVM instance Also get confirmation from the MAAS team that things are working as expected. [Where problems could occur] This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller. This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either. [Other Info] * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z + * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04 * The new package dependencies are fulfilled in Focal: - - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main) - - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main) - + - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main) + - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main) === Original description === While working on MAAS DPM/LPAR it turned out that a newer python- zhmcclient (package zhmcclient) is needed to get certain functions work, like especially storage group support. The latest is package is v0.27 on hirsute and v0.22 on focal. v0.28 is currently the latest release, but 0.29 is coming shortly. https://github.com/zhmcclient/python-zhmcclient/issues/731 Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates). Please notice that MAAS was the only reason why the zhmcclient package was created at all. The updated package is especially needed for focal, since focal is the recommended base distro for MAAS DPM/LPAR, hence this would require a special SRU (for this package version bump). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938404] [NEW] Phoc is not (yet) compatible with wlroots >= 0.13
Public bug reported: Neither phoc 0.6.0 nor 0.8.0 (from Debian experimental) seem to be compatible with wlroots 0.13, yet. There are some upstream patches being worked on: https://source.puri.sm/Librem5/phoc/-/merge_requests/241/ ** Affects: phoc (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938404 Title: Phoc is not (yet) compatible with wlroots >= 0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phoc/+bug/1938404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938404] Re: Phoc is not (yet) compatible with wlroots >= 0.13
** Also affects: wlroots (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/1938404 Title: Phoc is not (yet) compatible with wlroots >= 0.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phoc/+bug/1938404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934221] Re: systemd-resolve segfault
Denys, what kind of MDNS traffic is flowing in your network? I'm not really able to reproduce the problem locally. Maybe I'm missing this special network packets? Have you already been able to find out what triggers the issue for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902533] Re: Please merge user-setup 1.85 (main) from Debian unstable (main)
** Changed in: user-setup (Ubuntu) Status: In Progress => Fix Committed ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902533 Title: Please merge user-setup 1.85 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/user-setup/+bug/1902533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903688] [NEW] Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main)
Public bug reported: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main) Also upload s390-tools-signed 2.14.0-2ubuntu1 afterwards. Debdiff: https://paste.ubuntu.com/p/NtTYKQ7k6q/ ** Affects: s390-tools (Ubuntu) Importance: Undecided Assignee: Lukas Märdian (slyon) Status: In Progress ** Merge proposal linked: https://code.launchpad.net/~slyon/ubuntu/+source/s390-tools/+git/s390-tools/+merge/393502 ** Changed in: s390-tools (Ubuntu) Status: New => In Progress ** Changed in: s390-tools (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Description changed: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main) Also upload s390-tools-signed 2.14.0-2ubuntu1 afterwards. + Debdiff: https://paste.ubuntu.com/p/NtTYKQ7k6q/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903688 Title: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1903688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743200] Re: No support for interface labels
Hi Bruno, you can call `dpkg -l | grep netplan` to see the installed version. Netplan 0.100 is available in Ubuntu Focal 20.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743200 Title: No support for interface labels To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1743200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903688] Re: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main)
Thanks for the upload! Would you mind to also push the corresponding `s390-tools-signed` debdiff from the bug description above? ** Changed in: s390-tools (Ubuntu) Status: In Progress => 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/1903688 Title: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1903688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724895] Re: MTU not applied on private ethernet interfaces
Doing some experiments this seems to be working with netplan.io 0.100 in Groovy. No matter if 'match.macaddress' is set or not on my local eth interface. As far as I can tell the fix was released with netplan 0.99 in Focal final and was SRU'ed to Bionic as well. (https://github.com/CanonicalLtd/netplan/commit/77fcd4dbf77092608021baf5be5e4ae237f7de86) Marking 'Fix released'. Please re-open if it does not work for you. ** Changed in: netplan Status: Fix Committed => Fix Released ** Changed in: netplan.io (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724895 Title: MTU not applied on private ethernet interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1724895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903688] Re: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main)
** Changed in: s390-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903688 Title: Please merge s390-tools 2.14.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1903688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859018] Re: [UBUNTU 20.04] zkey: Fix listing of keys on file systems reporting DT_UNKNOWN.
The 'zkey list' command does not seem to be available in Bionic. Also the patched zkey/keystore.c file does not exist in s390-tools v2.3.0, so it looks like this bug isn't available either: ubuntu@juju-96c787-test-0:~$ zkey list zkey: Invalid command 'list' Try 'zkey --help' for more information. ubuntu@juju-96c787-test-0:~$ zkey --help Usage: zkey COMMAND SECURE-KEY-FILE [OPTIONS] Generate, re-encipher, and validate secure AES keys COMMANDS GENerate Generate a secure AES key REencipherRe-encipher an existing secure AES key VALidate Validate an existing secure AES key COMMON OPTIONS -V, --verbose Print additional information messages during processing -h, --help Print this help, then exit -v, --version Print version information, then exit For more information use 'zkey COMMAND --help'. ubuntu@juju-96c787-test-0:~$ zkey -v zkey version 2.3.0-build-20191025 Copyright IBM Corp. 2017 ** Changed in: s390-tools (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859018 Title: [UBUNTU 20.04] zkey: Fix listing of keys on file systems reporting DT_UNKNOWN. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1859018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860574] Re: [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys
The 'zkey list' command does not seem to be available in Bionic (s390-tools v2.3.0), so it looks like this bug isn't available either: ubuntu@juju-96c787-test-0:~$ zkey list zkey: Invalid command 'list' Try 'zkey --help' for more information. ubuntu@juju-96c787-test-0:~$ zkey --help Usage: zkey COMMAND SECURE-KEY-FILE [OPTIONS] Generate, re-encipher, and validate secure AES keys COMMANDS GENerate Generate a secure AES key REencipherRe-encipher an existing secure AES key VALidate Validate an existing secure AES key COMMON OPTIONS -V, --verbose Print additional information messages during processing -h, --help Print this help, then exit -v, --version Print version information, then exit For more information use 'zkey COMMAND --help'. ubuntu@juju-96c787-test-0:~$ zkey -v zkey version 2.3.0-build-20191025 Copyright IBM Corp. 2017 ** Changed in: s390-tools (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860574 Title: [UBUNTU 20.04] zkey: Fix display of clear key size for XTS keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1860574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865032] Re: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf
** Changed in: s390-tools (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865032 Title: [UBUNTU] zipl/libc: Fix potential buffer overflow in printf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1865032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
