pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth device in a timely manner, PMTU dst likely leaked)
Bug #1881643 reported by
Thadeu Lima de Souza Cascardo
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned | ||
| linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
| Focal |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
[...]
03:48:34 DEBUG| [stdout] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [FAIL]
03:48:34 DEBUG| [stdout] # can't delete veth device in a timely manner, PMTU dst likely leaked
[...]
03:49:17 DEBUG| [stdout] not ok 16 selftests: net: pmtu.sh # exit=1
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Changed in linux (Ubuntu Focal): | |
| status: | New → Confirmed |
| tags: | added: 5.4 focal ppc64el sru-20200518 ubuntu-kernel-selftests |
| tags: | added: kqa-blocker |
Revision history for this message
| Kelsey Steele (kelsey-steele) wrote Re: pmtu.sh net selftest fail with PMTU dst likely leaked | #2 |
| tags: | added: groovy s390x sru-20201109 |
| tags: | added: 5.8 |
| summary: |
- pmtu.sh net selftest fail with PMTU dst likely leaked + pmtu.sh net selftest fail with PMTU dst likely leaked (ipv6: cleanup of + cached exceptions - nexthop objects [FAIL]) |
| summary: |
- pmtu.sh net selftest fail with PMTU dst likely leaked (ipv6: cleanup of - cached exceptions - nexthop objects [FAIL]) + pmtu.sh net selftest fail with PMTU dst likely leaked (can't delete veth + device in a timely manner, PMTU dst likely leaked) |
| tags: | added: hirsute |
| tags: | added: sru-20210315 |
| tags: | added: sru-20210412 |
| tags: | added: sru-20210621 |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1881643
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.