WireGuard broken on Noble ppc64el

Bug #2049924 reported by Danilo Egea Gondolfo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
New
Undecided
bugproxy
linux (Ubuntu)
Status tracked in Noble
Noble
New
Undecided
Unassigned
netplan.io (Ubuntu)
Status tracked in Noble
Noble
Invalid
Undecided
Unassigned

Bug Description

Netplan autopkgtests related to Wireguard are currently failing (see below) on Noble ppc64el. Trying it manually on a ppc64el system, I can't load the kernel module:

~# modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': No such device

And because of that the interface can't be created:

Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]: <warn> [1705679279.5797] platform-linux: do-add-link[wg0/wireguard]: failure 95 (Operation not supported - Unknown device type)
Jan 19 15:47:59 mantic-bos01-ppc64el NetworkManager[2414]: <error> [1705679279.5797] manager: (netplan-wg0) couldn't create the device: Failed to create WireGuard interface 'wg0' for 'netplan-wg0': Operation not supported

Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: /run/systemd/network/10-netplan-wg0.netdev has 0644 mode that is too permissive, please adjust the ownership and access mode.
Jan 19 15:45:08 mantic-bos01-ppc64el systemd-networkd[731]: wg0: netdev could not be created: Operation not supported

Autopkgtest error:

2690s .Interface "wg0" not found.
2691s .Interface "wg0" not found.
2692s .Interface "wg0" not found.
2693s ..Interface "wg0" not found.
2694s Interface "wg0" not found.
2695s .Interface "wg0" not found.
2696s .Interface "wg0" not found.
2697s .Interface "wg0" not found.
2697s FAIL
2697s
2697s ======================================================================
2697s FAIL: test_tunnel_wireguard (__main__.TestNetworkManager.test_tunnel_wireguard)
2697s ----------------------------------------------------------------------
2697s Traceback (most recent call last):
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, in test_tunnel_wireguard
2697s self.generate_and_settle(['wg0', 'wg1'])
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 363, in generate_and_settle
2697s self.nm_wait_connected(iface, 60)
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 419, in nm_wait_connected
2697s self.wait_output(['nmcli', 'dev', 'show', iface], '(connected', timeout)
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in wait_output
2697s self.fail('timed out waiting for "{}" to appear in {}'.format(expected_output, cmd))
2697s AssertionError: timed out waiting for "(connected" to appear in ['nmcli', 'dev', 'show', 'wg0']
2697s
2697s ======================================================================
2697s FAIL: test_tunnel_wireguard (__main__.TestNetworkd.test_tunnel_wireguard)
2697s ----------------------------------------------------------------------
2697s Traceback (most recent call last):
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/tunnels.py", line 126, in test_tunnel_wireguard
2697s self.generate_and_settle(['wg0', 'wg1'])
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 365, in generate_and_settle
2697s self.networkd_wait_connected(iface, 60)
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 423, in networkd_wait_connected
2697s self.wait_output(['networkctl', 'status', iface], '(configured', timeout)
2697s File "/tmp/autopkgtest.N9l4Wi/build.nQ5/src/tests/integration/base.py", line 416, in wait_output
2697s self.fail('timed out waiting for "{}" to appear in {}'.format(expected_output, cmd))
2697s AssertionError: timed out waiting for "(configured" to appear in ['networkctl', 'status', 'wg0']
2697s
2697s ----------------------------------------------------------------------
2697s Ran 26 tests in 294.247s

summary: - WireGuard broken on ppc64el
+ WireGuard broken on Noble ppc64el
Revision history for this message
Danilo Egea Gondolfo (danilogondolfo) wrote (last edit ):

Actually, something else is broken (or not). Apparently anything that depends on power10 can't be loaded. The machine I have access to is a power9.

So I suppose it's lack of hardware support then... chacha20/poly1305-p10 were added on kernel 6.6 apparently.

Although, wireguard shouldn't be locked to -p10 modules on ppc64.

root@mantic-bos01-ppc64el:~# modprobe -v wireguard
insmod /lib/modules/6.6.0-14-generic/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst
modprobe: ERROR: could not insert 'wireguard': No such device

root@mantic-bos01-ppc64el:~# modprobe -v chacha-p10-crypto
insmod /lib/modules/6.6.0-14-generic/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst
modprobe: ERROR: could not insert 'chacha_p10_crypto': No such device

root@mantic-bos01-ppc64el:~# modprobe -v aes-gcm-p10-crypto
insmod /lib/modules/6.6.0-14-generic/kernel/arch/powerpc/crypto/aes-gcm-p10-crypto.ko.zst
modprobe: ERROR: could not insert 'aes_gcm_p10_crypto': No such device

root@mantic-bos01-ppc64el:~# modprobe -v poly1305-p10-crypto
insmod /lib/modules/6.6.0-14-generic/kernel/arch/powerpc/crypto/poly1305-p10-crypto.ko.zst
modprobe: ERROR: could not insert 'poly1305_p10_crypto': No such device

Lukas Märdian (slyon)
tags: added: update-excuse
Frank Heimes (fheimes)
Changed in ubuntu-power-systems:
assignee: nobody → bugproxy (bugproxy)
tags: added: noble ppc64el reverse-proxy-bugzilla
Lukas Märdian (slyon)
Changed in netplan.io (Ubuntu Noble):
status: New → Invalid
bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-205066 severity-medium targetmilestone-inin---
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.