| 2020-04-06 02:40:16 |
Po-Hsu Lin |
bug |
|
|
added bug |
| 2020-04-06 02:40:26 |
Po-Hsu Lin |
tags |
|
5.3 eoan gcp sru-20200316 |
|
| 2020-04-06 02:40:32 |
Po-Hsu Lin |
tags |
5.3 eoan gcp sru-20200316 |
5.3 eoan gcp sru-20200316 ubuntu-kernel-selftests |
|
| 2021-05-18 20:41:05 |
Kelsey Steele |
tags |
5.3 eoan gcp sru-20200316 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210412 ubuntu-kernel-selftests |
|
| 2021-05-18 20:42:19 |
Kelsey Steele |
tags |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210412 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210511 ubuntu-kernel-selftests |
|
| 2021-05-18 20:43:20 |
Kelsey Steele |
tags |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210511 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210510 ubuntu-kernel-selftests |
|
| 2021-05-24 08:51:23 |
Po-Hsu Lin |
summary |
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with B-5.3-gcp |
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) |
|
| 2021-06-15 16:31:53 |
Kelsey Steele |
tags |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210510 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210510 sru-20210531 ubuntu-kernel-selftests |
|
| 2021-06-21 19:58:21 |
Kelsey Steele |
tags |
5.11 5.3 eoan gcp hirsute sru-20200316 sru-20210510 sru-20210531 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 ubuntu-kernel-selftests |
|
| 2021-07-06 16:14:45 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu) |
|
| 2021-07-06 16:15:02 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-07-06 16:15:02 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Hirsute) |
|
| 2021-07-06 16:15:08 |
Kleber Sacilotto de Souza |
linux (Ubuntu Hirsute): status |
New |
Confirmed |
|
| 2021-07-06 16:15:42 |
Kleber Sacilotto de Souza |
tags |
5.11 5.3 eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 sru-20210621 ubuntu-kernel-selftests |
|
| 2021-07-21 21:05:16 |
Kelsey Steele |
tags |
5.11 5.3 eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 sru-20210621 ubuntu-kernel-selftests |
5.11 5.3 eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 ubuntu-kernel-selftests |
|
| 2021-08-18 07:08:44 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2021-10-27 13:37:09 |
Tim Gardner |
tags |
5.11 5.3 eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 ubuntu-kernel-selftests |
5.11 5.3 aws eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 ubuntu-kernel-selftests |
|
| 2022-01-20 11:19:31 |
Krzysztof Kozlowski |
tags |
5.11 5.3 aws eoan gcp hirsute impish sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 ubuntu-kernel-selftests |
5.11 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 ubuntu-kernel-selftests |
|
| 2022-01-26 22:00:43 |
Brian Murray |
linux (Ubuntu Hirsute): status |
Confirmed |
Won't Fix |
|
| 2022-02-25 12:30:01 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Impish |
|
| 2022-02-25 12:30:01 |
Kleber Sacilotto de Souza |
bug task added |
|
linux (Ubuntu Impish) |
|
| 2022-02-25 12:30:08 |
Kleber Sacilotto de Souza |
linux (Ubuntu Impish): status |
New |
Confirmed |
|
| 2022-02-25 12:32:03 |
Kleber Sacilotto de Souza |
tags |
5.11 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 ubuntu-kernel-selftests |
5.11 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests |
|
| 2022-05-25 05:27:17 |
Po-Hsu Lin |
linux (Ubuntu Impish): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-05-25 05:27:20 |
Po-Hsu Lin |
ubuntu-kernel-tests: assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-05-25 05:27:21 |
Po-Hsu Lin |
linux (Ubuntu Impish): status |
Confirmed |
In Progress |
|
| 2022-05-25 05:27:23 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
New |
In Progress |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Jammy) |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Bionic |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Kinetic |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Focal |
|
| 2022-05-25 06:35:52 |
Po-Hsu Lin |
bug task added |
|
linux (Ubuntu Focal) |
|
| 2022-05-25 06:37:46 |
Po-Hsu Lin |
linux (Ubuntu Bionic): status |
New |
Invalid |
|
| 2022-05-25 06:42:27 |
Po-Hsu Lin |
linux (Ubuntu Focal): status |
New |
Fix Released |
|
| 2022-05-25 06:42:35 |
Po-Hsu Lin |
linux (Ubuntu Jammy): status |
New |
Fix Released |
|
| 2022-05-25 06:44:24 |
Po-Hsu Lin |
linux (Ubuntu Kinetic): status |
Incomplete |
Fix Released |
|
| 2022-05-25 07:16:37 |
Po-Hsu Lin |
bug task added |
|
linux-oem-5.14 (Ubuntu) |
|
| 2022-05-25 07:16:51 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Bionic): status |
New |
Invalid |
|
| 2022-05-25 07:17:03 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Focal): status |
New |
Invalid |
|
| 2022-05-25 07:17:17 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Hirsute): status |
New |
Invalid |
|
| 2022-05-25 07:17:31 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Focal): status |
Invalid |
In Progress |
|
| 2022-05-25 07:17:31 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Focal): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-05-25 07:17:43 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Impish): status |
New |
Invalid |
|
| 2022-05-25 07:17:46 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Jammy): status |
New |
Invalid |
|
| 2022-05-25 07:17:49 |
Po-Hsu Lin |
linux-oem-5.14 (Ubuntu Kinetic): status |
New |
Invalid |
|
| 2022-05-25 07:18:14 |
Po-Hsu Lin |
tags |
5.11 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests |
13 5. 5.11 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests |
|
| 2022-05-25 07:23:26 |
Po-Hsu Lin |
description |
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 |
[Impact]
[Fix]
[Test]
[Where problems could occur]
[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 |
|
| 2022-05-25 07:57:29 |
Po-Hsu Lin |
summary |
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) |
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) |
|
| 2022-05-25 08:59:00 |
Po-Hsu Lin |
description |
[Impact]
[Fix]
[Test]
[Where problems could occur]
[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 |
[Impact]
The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with:
Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue:
[Where problems could occur]
[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 |
|
| 2022-05-25 09:04:56 |
Po-Hsu Lin |
description |
[Impact]
The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with:
Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass without any issue:
[Where problems could occur]
[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 |
[Impact]
The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with:
Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
|
| 2022-05-25 09:05:43 |
Po-Hsu Lin |
description |
[Impact]
The test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with:
Running 'make run_tests -C net TEST_PROGS=test_vxlan_under_vrf.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
[Impact]
The 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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
|
| 2022-05-25 09:07:01 |
Po-Hsu Lin |
description |
[Impact]
The 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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch to solve the another failure on Impish 5.13, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
[Impact]
The 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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
F-oem-5.14 has already got this one applied.
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
|
| 2022-05-25 09:13:46 |
Po-Hsu Lin |
description |
[Impact]
The 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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
F-oem-5.14 has already got this one applied.
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
[Impact]
The 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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
The second patch (b50d3b46) can be cherry-picked with must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one applied.
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
|
| 2022-05-25 09:30:15 |
Po-Hsu Lin |
description |
[Impact]
The 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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch on Impish 5.13 to solve the another failure, which we made it an expected failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
The second patch (b50d3b46) can be cherry-picked with must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has already got this one applied.
[Test]
Patch tested on Impish 5.13 and F-oem-5.14, this test_vxlan_under_vrf.sh test can pass 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 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 |
[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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and
F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to
have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch on
Impish 5.13 to solve the another failure, which we made it an expected
failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but
must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has
already got this one applied.
[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.
[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 |
|
| 2022-05-25 10:49:46 |
Po-Hsu Lin |
description |
[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
[Fix]
* e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case
The first patch (e7e4785f) can be cherry-picked to Impish 5.13 and
F-oem-5.14.
Note that this test is not failing on F-oem-5.14, but it's better to
have it applied to reduce the maintenance cost.
After the first patch was applied, we will need the second patch on
Impish 5.13 to solve the another failure, which we made it an expected
failure (XFAIL) with SAUCE patches:
Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL]
The second patch (b50d3b46) can be cherry-picked to Impish 5.13 but
must be applied with -C2 due to our SAUCE patches. F-oem-5.14 has
already got this one applied.
[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.
[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 |
[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:
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 |
|
| 2022-05-25 10:59:18 |
Po-Hsu Lin |
description |
[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:
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 |
[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.
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.
[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 |
|
| 2022-05-25 11:01:44 |
Po-Hsu Lin |
description |
[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.
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.
[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 |
[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.
[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 |
|
| 2022-05-25 11:03:18 |
Po-Hsu Lin |
description |
[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.
[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 |
[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 |
|
| 2022-05-25 11:05:14 |
Po-Hsu Lin |
description |
[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 |
[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.
[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 |
|
| 2022-05-26 05:41:59 |
Po-Hsu Lin |
linux (Ubuntu Focal): status |
Fix Released |
In Progress |
|
| 2022-05-26 05:41:59 |
Po-Hsu Lin |
linux (Ubuntu Focal): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2022-05-27 08:56:54 |
Kleber Sacilotto de Souza |
linux (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-05-27 08:57:08 |
Kleber Sacilotto de Souza |
linux (Ubuntu Impish): status |
In Progress |
Fix Committed |
|
| 2022-05-30 09:09:04 |
Po-Hsu Lin |
description |
[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.
[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 |
[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 F-5.4, I-5.13 and F-oem-5.14 need these patches.
First patch (e7e4785f):
- Can be cherry-picked to F-5.4 / Impish 5.13
- Can be cherry-picked to F-oem-5.14.
Second patch (b50d3b46):
- Can be cherry-picked to F-5.4 / 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 |
|
| 2022-06-07 09:54:02 |
Timo Aaltonen |
linux-oem-5.14 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-06-09 01:45:52 |
Po-Hsu Lin |
tags |
13 5. 5.11 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests |
|
| 2022-06-16 22:16:37 |
Ubuntu Kernel Bot |
tags |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-needed-focal |
|
| 2022-06-16 22:43:02 |
Ubuntu Kernel Bot |
tags |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-needed-focal |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-needed-focal verification-needed-impish |
|
| 2022-06-17 08:53:58 |
Po-Hsu Lin |
tags |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-needed-focal verification-needed-impish |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-done-impish verification-needed-focal |
|
| 2022-06-17 09:12:57 |
Po-Hsu Lin |
tags |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-done-impish verification-needed-focal |
5.11 5.13 5.3 aws eoan gcp hirsute impish oracle sru-20200316 sru-20210510 sru-20210531 sru-20210621 sru-20210719 sru-20211018 sru-20220221 ubuntu-kernel-selftests verification-done-focal verification-done-impish |
|
| 2022-06-22 15:04:22 |
Launchpad Janitor |
linux (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-06-22 15:04:22 |
Launchpad Janitor |
cve linked |
|
2022-28388 |
|
| 2022-06-22 15:04:36 |
Launchpad Janitor |
linux (Ubuntu Impish): status |
Fix Committed |
Fix Released |
|
| 2022-06-30 08:57:03 |
Launchpad Janitor |
linux-oem-5.14 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-06-30 08:57:03 |
Launchpad Janitor |
cve linked |
|
2022-21123 |
|
| 2022-06-30 08:57:03 |
Launchpad Janitor |
cve linked |
|
2022-21125 |
|
| 2022-06-30 08:57:03 |
Launchpad Janitor |
cve linked |
|
2022-21166 |
|
| 2023-02-24 04:28:02 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
In Progress |
Fix Released |
|
