rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)

[Po-Hsu Lin]

This test failed because of the unsuccessful attempt to add a dummy device with ip link command:
    # devdummy="test-dummy0"
    # ip link add name "$devdummy" type dummy
    RTNETLINK answers: Operation not supported

 selftests: rtnetlink.sh
 ========================================
 RTNETLINK answers: Operation not supported
 Cannot find device "test-dummy0"
 FAIL: cannot add dummy interface
 not ok 1..10 selftests: rtnetlink.sh [FAIL]

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 10:21:02 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

[Po-Hsu Lin (cypressyew)]

Found in 4.18 Bionic AWS as well.

[Kleber Sacilotto de Souza (kleber-souza)]

Also found in cosmic/linux-azure:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux-azure/20190416_185145_846ae@/log.gz

I'll nominate this bug against cosmic/linux.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1812194

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.

[Po-Hsu Lin (cypressyew)]

Error message on D-KVM:
 selftests: net: rtnetlink.sh
 ========================================
 Error: Unknown device type.
 Cannot find device "test-dummy0"
 FAIL: cannot add dummy interface
 not ok 1..11 selftests: net: rtnetlink.sh [FAIL]

[Po-Hsu Lin (cypressyew)]

This test will need:
CONFIG_DUMMY
CONFIG_NETDEVSIM

To be set to either Y or M.

[Guilherme G. Piccoli (gpiccoli)]

Found on Focal/linux-kvm, cycle sru-20210412

[Guilherme G. Piccoli (gpiccoli)]

Found on Bionic/linux-kvm, cycle sru-20210412

[Guilherme G. Piccoli (gpiccoli)]

Observed in F/KVM, cycle sru-20210510.

[Guilherme G. Piccoli (gpiccoli)]

Observed on G/KVM, cycle sru-20210510 .

[Guilherme G. Piccoli (gpiccoli)]

Observed on B/KVM, cycle sru-20210510 .

[Guilherme G. Piccoli (gpiccoli)]

Observed on H/KVM, cycle sru-20210510 .

[Guilherme G. Piccoli (gpiccoli)]

Observed on G/KVM, cycle sru-20210531 .

[Kleber Sacilotto de Souza (kleber-souza)]

bserved with focal/linux: 5.4.0-76.85.

[Brian Murray (brian-murray)]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release.

[Po-Hsu Lin (cypressyew)]

With config_dummy enabled for KVM kernels (bug 1998244) this test is now failing with:

 Running 'make run_tests -C net TEST_PROGS=rtnetlink.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: rtnetlink.sh
 # PASS: policy routing
 # sysctl: cannot stat /proc/sys/net/ipv4/fib_multipath_hash_policy: No such file or directory
 # Error: Multipath support not enabled in kernel.
 # sysctl: cannot stat /proc/sys/net/ipv4/fib_multipath_hash_policy: No such file or directory
 # sysctl: cannot stat /proc/sys/net/ipv4/fib_multipath_hash_policy: No such file or directory
 # sysctl: cannot stat /proc/sys/net/ipv4/fib_multipath_hash_policy: No such file or directory
 # RTNETLINK answers: No such process
 # FAIL: route get
 # PASS: preferred_lft addresses have expired
 # PASS: promote_secondaries complete
 # RTNETLINK answers: Operation not supported
 # RTNETLINK answers: Operation not supported
 # RTNETLINK answers: Operation not supported
 # We have an error talking to the kernel
 # RTNETLINK answers: Operation not supported
 # We have an error talking to the kernel
 # RTNETLINK answers: Operation not supported
 # We have an error talking to the kernel
 # RTNETLINK answers: Operation not supported
 # We have an error talking to the kernel
 # RTNETLINK answers: Operation not supported
 # We have an error talking to the kernel
 # RTNETLINK answers: Operation not supported
 # Dump terminated
 # RTNETLINK answers: Operation not supported
 # We have an error talking to the kernel
 # RTNETLINK answers: Operation not supported
 # Dump terminated
 # RTNETLINK answers: Operation not supported
 # FAIL: tc htb hierarchy
 # add tunnel "gre0" failed: No such device
 # Cannot find device "neta"
 # Cannot find device "neta"
 # Cannot find device "neta"
 # Device "neta" does not exist.
 # Device "neta" does not exist.
 # Device "neta" does not exist.
 # FAIL: ip netconf show neta
 # Cannot find device "neta"
 # FAIL: gre tunnel endpoint
 # Error: Unknown device type.
 # Cannot find device "gretap00"
 # Cannot find device "gretap00"
 # Cannot find device "gretap00"
 # Error: Unknown device type.
 # Cannot find device "gretap00"
 # FAIL: gretap
 # Error: Unknown device type.
 # Cannot find device "ip6gretap00"
 # Cannot find device "ip6gretap00"
 # Cannot find device "ip6gretap00"
 # Error: Unknown device type.
 # Cannot find device "ip6gretap00"
 # FAIL: ip6gretap
 # Error: Unknown device type.
 # Cannot find device "erspan00"
 # Cannot find device "erspan00"
 # Cannot find device "erspan00"
 # Error: Unknown device type.
 # Cannot find device "erspan00"
 # Cannot find device "erspan00"
 # Cannot find device "erspan00"
 # Error: Unknown device type.
 # Cannot find device "erspan00"
 # FAIL: erspan
 # Error: Unknown device type.
 # Cannot fi...