Public bug reported:
First observed on jammy:linux-kvm 5.15.0-1080.85 (sru-20250414).
The test pmtu_ipv4_mp_exceptions, which belongs to
tools/testing/selftests/net/pmtu.sh, fails as follows on jammy:linux-
kvm:
TEST: ipv4: PMTU multipath nh exceptions [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
TEST: ipv4: PMTU multipath nh exceptions - nexthop objects [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
The test pmtu_ipv4_mp_exceptions was first introduced by:
7d3f3b4367f315 net: ipv4: Cache pmtu for all packet paths if multipath enabled
which landed in jammy:linux 5.15.0-140.150
As shown by executing the execution of the test with VERBOSE option
enabled, the test requires multipath support (CONFIG_IP_ROUTE_MULTIPATH
= y)
# ./tools/testing/selftests/net/pmtu.sh pmtu_ipv4_mp_exceptions
##########################################################################
COMMAND: ip netns exec ns-A ip addr add 192.168.99.99 dev lo
COMMAND: ip netns exec ns-A ip route add 192.168.88.88 src 192.168.99.99
nexthop via 10.0.1.2 weight 1 nexthop via 10.0.2.2 weight 1
Error: Multipath support not enabled in kernel.
COMMAND: ip netns exec ns-B ip addr add 192.168.88.88 dev lo
COMMAND: ip netns exec ns-B ip route add 192.168.99.99 src 192.168.88.88
nexthop via 10.0.3.2 weight 1 nexthop via 10.0.4.2 weight 1
Error: Multipath support not enabled in kernel.
COMMAND: ip netns exec ns-R1 ip route add 192.168.99.99 via 10.0.1.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.99.99 via 10.0.2.1
COMMAND: ip netns exec ns-R1 ip route add 192.168.88.88 via 10.0.3.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.88.88 via 10.0.4.1
COMMAND: ip netns exec ns-A ping -q -M want -i 0.1 -c 1 -s 1800
192.168.88.88
PING 192.168.88.88 (192.168.88.88) 1800(1828) bytes of data.
--- 192.168.88.88 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
TEST: ipv4: PMTU multipath nh exceptions [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
##########################################################################
COMMAND: ip netns exec ns-A ip addr add 192.168.99.99 dev lo
COMMAND: ip netns exec ns-A ip nexthop add id 401 via 10.0.1.2 dev veth_A-R1
COMMAND: ip netns exec ns-A ip nexthop add id 402 via 10.0.2.2 dev veth_A-R2
COMMAND: ip netns exec ns-A ip nexthop add id 403 group 401/402
COMMAND: ip netns exec ns-A ip route add 192.168.88.88 src 192.168.99.99
nhid 403
COMMAND: ip netns exec ns-B ip addr add 192.168.88.88 dev lo
COMMAND: ip netns exec ns-B ip nexthop add id 401 via 10.0.3.2 dev veth_B-R1
COMMAND: ip netns exec ns-B ip nexthop add id 402 via 10.0.4.2 dev veth_B-R2
COMMAND: ip netns exec ns-B ip nexthop add id 403 group 401/402
COMMAND: ip netns exec ns-B ip route add 192.168.99.99 src 192.168.88.88
nhid 403
COMMAND: ip netns exec ns-R1 ip route add 192.168.99.99 via 10.0.1.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.99.99 via 10.0.2.1
COMMAND: ip netns exec ns-R1 ip route add 192.168.88.88 via 10.0.3.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.88.88 via 10.0.4.1
COMMAND: ip netns exec ns-A ping -q -M want -i 0.1 -c 1 -s 1800
192.168.88.88
PING 192.168.88.88 (192.168.88.88) 1800(1828) bytes of data.
--- 192.168.88.88 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
TEST: ipv4: PMTU multipath nh exceptions - nexthop objects [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
CONFIG_IP_ROUTE_MULTIPATH is not enabled in jammy:linux-kvm, which means that
this is not a regression.
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags: 5.15 jammy linux-kvm sru-20250414 ubuntu-kernel-selftests
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2110030
Title:
ubuntu_kernel_selftests:net:pmtu.sh failing on j:linux-kvm
Status in ubuntu-kernel-tests:
New
Bug description:
First observed on jammy:linux-kvm 5.15.0-1080.85 (sru-20250414).
The test pmtu_ipv4_mp_exceptions, which belongs to
tools/testing/selftests/net/pmtu.sh, fails as follows on jammy:linux-
kvm:
TEST: ipv4: PMTU multipath nh exceptions [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
TEST: ipv4: PMTU multipath nh exceptions - nexthop objects [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
The test pmtu_ipv4_mp_exceptions was first introduced by:
7d3f3b4367f315 net: ipv4: Cache pmtu for all packet paths if multipath enabled
which landed in jammy:linux 5.15.0-140.150
As shown by executing the execution of the test with VERBOSE option
enabled, the test requires multipath support
(CONFIG_IP_ROUTE_MULTIPATH = y)
# ./tools/testing/selftests/net/pmtu.sh pmtu_ipv4_mp_exceptions
##########################################################################
COMMAND: ip netns exec ns-A ip addr add 192.168.99.99 dev lo
COMMAND: ip netns exec ns-A ip route add 192.168.88.88 src 192.168.99.99
nexthop via 10.0.1.2 weight 1 nexthop via 10.0.2.2 weight 1
Error: Multipath support not enabled in kernel.
COMMAND: ip netns exec ns-B ip addr add 192.168.88.88 dev lo
COMMAND: ip netns exec ns-B ip route add 192.168.99.99 src 192.168.88.88
nexthop via 10.0.3.2 weight 1 nexthop via 10.0.4.2 weight 1
Error: Multipath support not enabled in kernel.
COMMAND: ip netns exec ns-R1 ip route add 192.168.99.99 via 10.0.1.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.99.99 via 10.0.2.1
COMMAND: ip netns exec ns-R1 ip route add 192.168.88.88 via 10.0.3.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.88.88 via 10.0.4.1
COMMAND: ip netns exec ns-A ping -q -M want -i 0.1 -c 1 -s 1800
192.168.88.88
PING 192.168.88.88 (192.168.88.88) 1800(1828) bytes of data.
--- 192.168.88.88 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
TEST: ipv4: PMTU multipath nh exceptions [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
##########################################################################
COMMAND: ip netns exec ns-A ip addr add 192.168.99.99 dev lo
COMMAND: ip netns exec ns-A ip nexthop add id 401 via 10.0.1.2 dev
veth_A-R1
COMMAND: ip netns exec ns-A ip nexthop add id 402 via 10.0.2.2 dev
veth_A-R2
COMMAND: ip netns exec ns-A ip nexthop add id 403 group 401/402
COMMAND: ip netns exec ns-A ip route add 192.168.88.88 src 192.168.99.99
nhid 403
COMMAND: ip netns exec ns-B ip addr add 192.168.88.88 dev lo
COMMAND: ip netns exec ns-B ip nexthop add id 401 via 10.0.3.2 dev
veth_B-R1
COMMAND: ip netns exec ns-B ip nexthop add id 402 via 10.0.4.2 dev
veth_B-R2
COMMAND: ip netns exec ns-B ip nexthop add id 403 group 401/402
COMMAND: ip netns exec ns-B ip route add 192.168.99.99 src 192.168.88.88
nhid 403
COMMAND: ip netns exec ns-R1 ip route add 192.168.99.99 via 10.0.1.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.99.99 via 10.0.2.1
COMMAND: ip netns exec ns-R1 ip route add 192.168.88.88 via 10.0.3.1
COMMAND: ip netns exec ns-R2 ip route add 192.168.88.88 via 10.0.4.1
COMMAND: ip netns exec ns-A ping -q -M want -i 0.1 -c 1 -s 1800
192.168.88.88
PING 192.168.88.88 (192.168.88.88) 1800(1828) bytes of data.
--- 192.168.88.88 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
TEST: ipv4: PMTU multipath nh exceptions - nexthop objects [FAIL]
PMTU exception wasn't created after exceeding MTU (veth_A-R2)
CONFIG_IP_ROUTE_MULTIPATH is not enabled in jammy:linux-kvm, which means that
this is not a regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2110030/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
