canonical-ubuntu-qa team mailing list archive

[Ian Whitfield <2071590@xxxxxxxxxxxxxxxxxx>]

Assuming I'm seeing the same or similar problem with noble:linux-gcp-6.14 (6.14.0-1007.7~24.04.1) on Google's t2d-standard-4, c3d-standard-16, e2-highcpu-8:
TEST: VM connectivity over vnifiltering vxlan (ipv6 default rdst)   [FAIL]

With this kernel, t2a-standard-4 is also failing with the exact message
listed in the bug description above. Note that's the only ARM64 machine
out of the instances I listed, though this is maybe more closely
correlated to NICs. Have yet to investigate that.

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

Title:
  test_vxlan_vnifiltering.sh from ubuntu_kselftests_net failed on linux-
  oem-6.8 (with ipv6 default rdst)

Status in ubuntu-kernel-tests:
  New

Bug description:
  Test complains about:
  TAP version 13
  1..1
  # timeout set to 0
  # selftests: net: test_vxlan_vnifiltering.sh
  #     TEST: Create traditional vxlan device                               [ OK ]
  #     TEST: Cannot create vnifilter device without external flag          [ OK ]
  #     TEST: Creating external vxlan device with vnifilter flag            [ OK ]
  #     TEST: Cannot set in-use vni id on vnifiltering device               [ OK ]
  #     TEST: Set new vni id on vnifiltering device                         [ OK ]
  #     TEST: Create second external vxlan device with vnifilter flag       [ OK ]
  #     TEST: Cannot set in-use vni id on vnifiltering device               [ OK ]
  #     TEST: Set new vni id on vnifiltering device                         [ OK ]
  #     TEST: Update vni id on vnifiltering device                          [ OK ]
  #     TEST: Add new vni id on vnifiltering device                         [ OK ]
  #     TEST: Set multicast group on existing vni                           [ OK ]
  #     TEST: Set multicast group on existing vni                           [ OK ]
  #     TEST: Cannot set vnifilter flag on a device                         [ OK ]
  #     TEST: Cannot unset vnifilter flag on a device                       [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan (ipv4 default rdst)   [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan (ipv6 default rdst)   [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan pervni remote (ipv4 default rdst)  [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan pervni remote (ipv6 default rdst)  [FAIL]
  #     TEST: VM connectivity over vnifiltering vxlan mgroup (ipv4 default rdst)  [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan mgroup (ipv6 default rdst)  [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan pervni mgroup (ipv4 default rdst)  [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan pervni mgroup (ipv6 default rdst)  [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan pervni remote mix (ipv4 default rdst)  [ OK ]
  #     TEST: VM connectivity over vnifiltering vxlan pervni remote mix (ipv6 default rdst)  [ OK ]
  #     TEST: VM connectivity over traditional vxlan (ipv4 default rdst)    [ OK ]
  #     TEST: VM connectivity over traditional vxlan (ipv6 default rdst)    [ OK ]
  #     TEST: VM connectivity over metadata nonfiltering vxlan (ipv4 default rdst)  [ OK ]
  # 
  # Tests passed:  26
  # Tests failed:   1
  not ok 1 selftests: net: test_vxlan_vnifiltering.sh # exit=1

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