The result of `strace -f -s 200 netplan status` is in the attachment (netplan.strace).
Regarding a minimal configuration, we haven't yet been able to determine the minimum setup required to reproduce the issue reliably. Our environment consists of a two-node K3s cluster using the default Flannel VXLAN backend, with the NVIDIA Network Operator installed to provide Multus and SR-IOV secondary networking. At this point we cannot say with confidence whether the issue is reproducible on a plain K3s installation or whether some aspect of our networking stack is required to trigger it. If there are any additional commands or configuration files that would help narrow down the minimal reproducer, we'd be happy to provide them. ** Attachment added: "netplan.strace" https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2158629/+attachment/5987625/+files/netplan.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2158629 Title: Netplan status cannot query iproute2 interface data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2158629/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
