Interestingly, in netplan-sriov-apply.service I can see this: "Apr 16
15:44:44 romano netplan[1171]: failed parsing sriov_totalvfs for
ens7f1np1: [Errno 2] No such file or directory:
'/sys/class/net/ens7f1np1/device/sriov_totalvfs'"
Whereas it should be:
ubuntu@romano:~$ cat /sys/class/net/ens7f1
FTR: I'm seeing exactly the same behavior when testing with "MT2892
Family [ConnectX-6 Dx]" on 24.04 LTS. Was this actually ever working in
Ubuntu on this hardware model?
ubuntu@romano:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 24.04.2 LTS
Release
eing":100,"external":false,"learning":false,"proxy":false,"rsc":true,"l2miss":true,"l3miss":true,"udp_csum":true,"udp_zero_csum6_tx":true,"udp_zero_csum6_rx":true,"remcsum_tx":true,"remcsum_r
$ autopkgtest -U -B . --add-apt-source='deb [trusted=yes]
https://ppa.launchpadcontent.net/tjaalton/ppa/ubuntu plucky main'
--test-name=tunnels -s -- qemu /data/autopkgtest-plucky-amd64.img
Still fails in the same way using iproute2 6.14.0-1ubuntu1~ppa1
--
You received this bug notification beca
iproute2 6.14.0-1ubuntu1~ppa2 from the PPA fixes the Netplan test
regression on my system.
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Pa
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2105484
Title:
Invalid "fan-map" in iproute2 JSON output
Status in
Seeing the "DEBUG::61:00.1 VF LAG state is not active yet,
retrying..." messages, it might be worth trying to increase the timeout
(FALLBACK_WAIT_TIME_SEC, INTERVAL_SEC, MAX_WAITING_TIME_SEC) in
/usr/share/netplan/netplan_cli/cli/commands/sriov_rebind.py
Maybe Mellanox ConnectX-6 just needs a
After a reboot with the configuration from the test case on Mellanox
CX6, the system comes up in a half broken state (not all VFs created,
"legacy" eswitch mode, LAG disabled):
ubuntu@romano:~$ sudo lshw -c network -businfo
Bus info Device Class Description
=
Some debugging output (which seems to be different from what's observed
in bug #2020409, https://pastebin.canonical.com/p/ZBVkc8rstg/):
ubuntu@romano:~$ systemctl status netplan-sriov-rebind.service
○ netplan-sriov-rebind.service - (Re-)bind SR-IOV Virtual Functions to their
driver
Loaded: l
I've re-executed the test plan on Mellanox ConnectX-6 Dx (MT2892). As
there seems to be some issue with this hardware generation (see bug
#2020409 comment #11++). And indeed, I seem to be able to reproduce that
failure, the devices are not set to "switchdev" mode and the VF-LAG is
not activated:
u
** Tags removed: sru-next
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988018
Title:
[SRU][mlx5] Intermittent VF-LAG activation failure
Status in linux package in Ubuntu:
Fix Commi
I tested netplan.io 0.107.1-3ubuntu0.22.04.2 from jammy-proposed, all looking
good!
The intermittent failures reported in comment #12 are resolved.
First of all, the eswitch/switchdev functionality is not available on Jammy's
GA 5.15 kernel,
so I upgraded to the HWE kernel and installed Netplan
I see the patches got sponsored and accepted by SRU reviewers, so I'm
dropping the ~ubuntu-sponsors subscription. Please re-subscribe, should
you need another sponsor in the future.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-
Dear openstack team (or anyone with the relevant hardware), can you
please help to test this, using the following commands?
cat
There's a potential regression with Juju in bug #208
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988018
Title:
[SRU][mlx5] Intermittent VF-LAG activation failure
Status in linux
Dropping ~ubuntu-sponsors, as this got sponsored already.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2069760
Title:
Soundwire support for CS42L43 and CS35L56 on Intel MTL
St
Dropping ~ubuntu-sponsors, as this got sponsored already.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs/2069417
Title:
Soundwire support for the Intel LNL Gen platforms
Status i
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
Status
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2080489
Title:
Network Manager stops functioning on Ubuntu 24.0
** Tags added: sru-next
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988018
Title:
[mlx5] Intermittent VF-LAG activation failure
Status in linux package in Ubuntu:
Fix Committed
St
I can see this behavior on a ThinkPad T410 with Intel graphics.
Rolling back to kernel 6.5 or 5.15 solves the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2077260
Both debdiffs have landed, so I'm unsubscribing ~ubuntu-sponsors. Please
re-subscribe should you need further sponsorship.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2072
This should be fixed as of Netplan v1.0:
https://github.com/canonical/netplan/pull/439
Please re-open if you think this is still an issue.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: Fix Committed
** Also affects: netplan.io (Ubuntu Noble)
Importance: Medium
** Changed in: netplan.io (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049924
Title:
WireGuard broken on Noble ppc64el
Status in The Ubun
Actually, we can further reduce the patch to the removal of
`.generate_mac = true`. This already fixes the issue we observe here.
** Patch added: "lp2037667.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741632/+files/lp2037667.patch
--
You received this bug
This seems to do the trick using the following Netplan config as a
testcase.
All 3 interfaces (tun[0-2]) are correctly created with their local &
remote properties set:
root@jj-abi:~/systemd# ip link show dev tun0
19: tun0@NONE: mtu 1448 qdisc noqueue state UNKNOWN mode
DEFAULT group default ql
So after bisecting systemd (v249..v251) on Jammy, this seems to be the
commit that changed behavior for the better:
https://github.com/systemd/systemd/commit/9f0cf80dd007491698978dbfe38158d74c1c9526
It probably needs some backporting for v249.11.
--
You received this bug notification because yo
We talked to our systemd maintainer inside foundations and also reached
out to upstream system [1], which didn't lead anywhere. We shouldn't
need to bisect systemd-networkd and do a high impact systemd SRU to fix
a regression in a kernel update, where we can pinpoint the exact (small)
git commit.
** Tags added: update-excuse
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049924
Title:
WireGuard broken on Noble ppc64el
Status in linux package in Ubuntu:
New
Status in netplan.i
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037667
Title:
Regression on Jammy's kernel 5.15 when creating ip6gre a
Thank you! I confirmed that the added distro-patches match the upstream
patches. The feature looks useful, but it's not very common to backport
new features as part of an SRU... So I'll leave that decision to the SRU
team.
In either way, this should probably first be fixed in the current
"devel" s
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037667
Title:
Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
tunnels
Status in linux pa
his case (user visible)?
Problems: None
** Changed in: protection-domain-mapper (Ubuntu)
Status: New => Confirmed
** Changed in: protection-domain-mapper (Ubuntu)
Assignee: Lukas Märdian (slyon) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification becaus
** Changed in: qrtr (Ubuntu)
Status: New => Confirmed
** Changed in: qrtr (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
** Changed in: protection-domain-mapper (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received
Review for Source Package: qrtr
[Summary]
qrtr is the userspace part for IPC communication with qualcomm processors. It
is primarily used on mobile phones, but can also be relevant for ARM based
laptops, such as the Lenovo X13s.
MIR team ACK (pending security-team ACK), with some suggested
Rec
Could this be related to https://bugs.launchpad.net/netplan/+bug/2020409
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988018
Title:
[mlx5] Intermittent VF-LAG activation failure
St
** Tags removed: foundations-triage-discuss
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988018
Title:
[mlx5] Intermittent VF-LAG activation failure
Status in linux package in Ubuntu
** Changed in: netplan.io (Ubuntu Kinetic)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu Kinetic)
Importance: Undecided => Medium
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Basic VRF support landed in netplan v0.105:
https://github.com/canonical/netplan/pull/285
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Does this also happen when you use the more recent version 2.4.8 from
the jammy-updates pocket?
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
Importance: Undecided
Sta
Setting the systemd bug task to "Invalid", as this is being handled in
the kernel.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu Focal)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu Jammy)
Status: Confirmed => Inval
Public bug reported:
depmod: WARNING: could not open modules.builtin.modinfo at
/tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic:
No such file or directory
https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/amd64/i/initramfs-tools/20220823_
Closing this bug for systemd, as it's not relevant anymore IMO and is a
red herring in proposed-migration.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.4 i
netplan.io (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs i
In more recent kernels (i.e. linux-meta-aws/azure 5.13) I can see
messages like this: " watchdog: BUG: soft lockup - CPU#3 stuck for
238s!" that seems to indicate the kernel is not giving back control to
the userspace/systemd.
Also a message about a missing autofs4 module, that might be related:
"
This seems to be a regression (deprecated AF_ALG RC4 support) in the
linux-hwe-5.11 stack: https://lkml.org/lkml/2020/8/4/512
A workaround exists by either using Linux 5.8 or using a newer iwd
version (e.g. from https://launchpad.net/~slyon/+archive/ubuntu/iwd+nm )
Unfortunately, we cannot easily
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1860672
Title:
Autopkgtest fa
*** 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 Kernel
Packages, which i
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 additio
> 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 lo
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
51 matches
Mail list logo
