WireGuard broken on ppc64el Noble++
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
The Ubuntu-power-systems project |
Confirmed
|
Undecided
|
bugproxy | |||
linux (Ubuntu) | Status tracked in Oracular | |||||
Noble |
Confirmed
|
Undecided
|
Unassigned | |||
Oracular |
Confirmed
|
Undecided
|
Unassigned | |||
netplan.io (Ubuntu) | Status tracked in Oracular | |||||
Noble |
Invalid
|
Undecided
|
Unassigned | |||
Oracular |
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-
Jan 19 15:47:59 mantic-
Jan 19 15:45:08 mantic-
Jan 19 15:45:08 mantic-
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_
2697s -------
2697s Traceback (most recent call last):
2697s File "/tmp/autopkgte
2697s self.generate_
2697s File "/tmp/autopkgte
2697s self.nm_
2697s File "/tmp/autopkgte
2697s self.wait_
2697s File "/tmp/autopkgte
2697s self.fail('timed out waiting for "{}" to appear in {}'.format(
2697s AssertionError: timed out waiting for "(connected" to appear in ['nmcli', 'dev', 'show', 'wg0']
2697s
2697s =======
2697s FAIL: test_tunnel_
2697s -------
2697s Traceback (most recent call last):
2697s File "/tmp/autopkgte
2697s self.generate_
2697s File "/tmp/autopkgte
2697s self.networkd_
2697s File "/tmp/autopkgte
2697s self.wait_
2697s File "/tmp/autopkgte
2697s self.fail('timed out waiting for "{}" to appear in {}'.format(
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 |
tags: | added: update-excuse |
Changed in ubuntu-power-systems: | |
assignee: | nobody → bugproxy (bugproxy) |
tags: | added: noble ppc64el reverse-proxy-bugzilla |
Changed in netplan.io (Ubuntu Noble): | |
status: | New → Invalid |
tags: | added: architecture-ppc64le bugnameltc-205066 severity-medium targetmilestone-inin--- |
summary: |
- WireGuard broken on Noble ppc64el + WireGuard broken on ppc64el Noble++ |
Changed in ubuntu-power-systems: | |
status: | New → Confirmed |
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 6.6.0-14- generic/ kernel/ arch/powerpc/ crypto/ chacha- p10-crypto. ko.zst
insmod /lib/modules/
modprobe: ERROR: could not insert 'wireguard': No such device
root@mantic- bos01-ppc64el: ~# modprobe -v chacha-p10-crypto 6.6.0-14- generic/ kernel/ arch/powerpc/ crypto/ chacha- p10-crypto. ko.zst p10_crypto' : No such device
insmod /lib/modules/
modprobe: ERROR: could not insert 'chacha_
root@mantic- bos01-ppc64el: ~# modprobe -v aes-gcm-p10-crypto 6.6.0-14- generic/ kernel/ arch/powerpc/ crypto/ aes-gcm- p10-crypto. ko.zst p10_crypto' : No such device
insmod /lib/modules/
modprobe: ERROR: could not insert 'aes_gcm_
root@mantic- bos01-ppc64el: ~# modprobe -v poly1305-p10-crypto 6.6.0-14- generic/ kernel/ arch/powerpc/ crypto/ poly1305- p10-crypto. ko.zst p10_crypto' : No such device
insmod /lib/modules/
modprobe: ERROR: could not insert 'poly1305_