canonical-ubuntu-qa team mailing list archive

[Magali Lemes do Sacramento <2115903@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Running the ubuntu_kselftests_net tests with the plucky:aws kernel on
a1.xlarge leads to a timeout.

It often stops at the net:test_vxlan_mdb.sh test case when it reaches
the 180-minute threshold:

WARNING: sut-test timed out after 180 minutes and was killed!
WARNING: The test may have hung or the timeout may need to be increased.

This has been seen on plucky:linux-aws 6.14.0-1007.7 during the
2025.06.16 cycle, but can also be found in the 2025.05.19 and 2025.04.14
cycles. I couldn't find such problem with the 64k flavor on the same
instance, but the test is also very close to reaching the 180-minute
limit.

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New

-- 
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/2115903

Title:
  ubuntu_kselftests_net with plucky:aws times out on a1.xlarge

Status in ubuntu-kernel-tests:
  New

Bug description:
  Running the ubuntu_kselftests_net tests with the plucky:aws kernel on
  a1.xlarge leads to a timeout.

  It often stops at the net:test_vxlan_mdb.sh test case when it reaches
  the 180-minute threshold:

  WARNING: sut-test timed out after 180 minutes and was killed!
  WARNING: The test may have hung or the timeout may need to be increased.

  This has been seen on plucky:linux-aws 6.14.0-1007.7 during the
  2025.06.16 cycle, but can also be found in the 2025.05.19 and
  2025.04.14 cycles. I couldn't find such problem with the 64k flavor on
  the same instance, but the test is also very close to reaching the
  180-minute limit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2115903/+subscriptions