V2 https://lists.ubuntu.com/archives/kernel-team/2022-May/130594.html
** Description changed:
[Impact]
test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
will fail on 5.13 kernel with:
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but
it's better to have corresponding patches applied to reduce the
maintenance cost in the future.
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
First patch (e7e4785f):
- Can be cherry-picked to Impish 5.13
- Can be cherry-picked to F-oem-5.14.
Second patch (b50d3b46):
- Can be cherry-picked to Impish 5.13 (-C2 is required while
applying it due to our SAUCE patches)
- F-oem-5.14 has already got this one applied.
- - Can be cherry-picked to J-oem-5.17
The reason why we need the second patch is that after the first one
got applied, we will see another failure, which we made it an expected
failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
- 5.13, F-oem-5.14 and J-oem-5.17 without any issue:
+ 5.13 and F-oem-5.14 without any issue:
Checking HV connectivity [ OK ]
Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
[Where problems could occur]
Change limit to test cases, should not have any real impact to any
kernel functions. But if these fixes are incorrect we will see
failures in our regression-testing report. The worst scenario is
getting false-negative results.
[Original Bug Report]
Issue found with GCP 5.3.0-1017.18~18.04.1
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
The failure is different from bug 1837348
** Description changed:
[Impact]
test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
will fail on 5.13 kernel with:
- # selftests: net: test_vxlan_under_vrf.sh
- # Checking HV connectivity [ OK ]
- # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
- not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
+ # selftests: net: test_vxlan_under_vrf.sh
+ # Checking HV connectivity [ OK ]
+ # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
+ not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
- Note that this test is not failing on F-oem-5.14 / J-oem-5.17, but
- it's better to have corresponding patches applied to reduce the
- maintenance cost in the future.
+ Note that this test is not failing on F-oem-5.14 but it's better to
+ have corresponding patches applied to reduce the maintenance cost
+ in the future.
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
First patch (e7e4785f):
- - Can be cherry-picked to Impish 5.13
- - Can be cherry-picked to F-oem-5.14.
+ - Can be cherry-picked to Impish 5.13
+ - Can be cherry-picked to F-oem-5.14.
Second patch (b50d3b46):
- - Can be cherry-picked to Impish 5.13 (-C2 is required while
- applying it due to our SAUCE patches)
- - F-oem-5.14 has already got this one applied.
+ - Can be cherry-picked to Impish 5.13 (-C2 is required while
+ applying it due to our SAUCE patches)
+ - F-oem-5.14 has already got this one applied.
The reason why we need the second patch is that after the first one
got applied, we will see another failure, which we made it an expected
failure (XFAIL) with SAUCE patches:
- Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
+ Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
5.13 and F-oem-5.14 without any issue:
- Checking HV connectivity [ OK ]
- Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
- Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
+ Checking HV connectivity [ OK ]
+ Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
+ Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
[Where problems could occur]
Change limit to test cases, should not have any real impact to any
kernel functions. But if these fixes are incorrect we will see
failures in our regression-testing report. The worst scenario is
getting false-negative results.
[Original Bug Report]
Issue found with GCP 5.3.0-1017.18~18.04.1
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
The failure is different from bug 1837348
** Description changed:
[Impact]
test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
will fail on 5.13 kernel with:
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
Note that this test is not failing on F-oem-5.14 but it's better to
have corresponding patches applied to reduce the maintenance cost
in the future.
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
First patch (e7e4785f):
- Can be cherry-picked to Impish 5.13
- Can be cherry-picked to F-oem-5.14.
Second patch (b50d3b46):
- Can be cherry-picked to Impish 5.13 (-C2 is required while
applying it due to our SAUCE patches)
- F-oem-5.14 has already got this one applied.
The reason why we need the second patch is that after the first one
got applied, we will see another failure, which we made it an expected
failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
5.13 and F-oem-5.14 without any issue:
Checking HV connectivity [ OK ]
Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
[Where problems could occur]
Change limit to test cases, should not have any real impact to any
kernel functions. But if these fixes are incorrect we will see
failures in our regression-testing report. The worst scenario is
getting false-negative results.
+ v2: Update cover-letter content and target in patch title to make it
+ easier to read.
+
+
[Original Bug Report]
Issue found with GCP 5.3.0-1017.18~18.04.1
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
The failure is different from bug 1837348
** Description changed:
[Impact]
test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests
will fail on 5.13 kernel with:
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1
Note that this test is not failing on F-oem-5.14 but it's better to
have corresponding patches applied to reduce the maintenance cost
in the future.
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
+
+ Only I-5.13 and F-oem-5.14 need these patches.
First patch (e7e4785f):
- Can be cherry-picked to Impish 5.13
- Can be cherry-picked to F-oem-5.14.
Second patch (b50d3b46):
- Can be cherry-picked to Impish 5.13 (-C2 is required while
applying it due to our SAUCE patches)
- F-oem-5.14 has already got this one applied.
The reason why we need the second patch is that after the first one
got applied, we will see another failure, which we made it an expected
failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
With the patched test_vxlan_under_vrf.sh test, it can pass on Impish
5.13 and F-oem-5.14 without any issue:
Checking HV connectivity [ OK ]
Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ]
Check VM connectivity through VXLAN (underlay in a VRF) [ OK ]
[Where problems could occur]
Change limit to test cases, should not have any real impact to any
kernel functions. But if these fixes are incorrect we will see
failures in our regression-testing report. The worst scenario is
getting false-negative results.
v2: Update cover-letter content and target in patch title to make it
- easier to read.
-
+ easier to read.
[Original Bug Report]
Issue found with GCP 5.3.0-1017.18~18.04.1
# selftests: net: test_vxlan_under_vrf.sh
# Checking HV connectivity [ OK ]
# Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1
The failure is different from bug 1837348
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015
Title:
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
(Check VM connectivity through VXLAN (underlay in the default VRF)
[FAIL])
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
