4 failures reported in net:fcnal-test.sh on Jammy

[Po-Hsu Lin]

This is not a regression, but something covered by bug 2006692

There are 5 sub-test failures reported in this test on Jammy:

 # Tests passed: 857
 # Tests failed: 5

# With VRF
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping local, VRF bind - VRF IP [FAIL]
# TEST: ping local, device bind - ns-A IP [FAIL]

# SYSCTL: net.ipv4.ping_group_range=0 2147483647
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping local, VRF bind - VRF IP [FAIL]
# TEST: ping local, device bind - ns-A IP [FAIL]

=== The following seems to be fixed, see comment #4
# With VRF
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# SYSCTL: net.ipv4.ping_group_range=0 2147483647
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL]

We might see failure came up in F/K after bug 2006391 being fixed.

[Andrei Gherzan (agherzan)]

This affects focal:linux-hwe-5.15. I've encountered it in the 20230320 cycle.

[Cory Todd (corytodd)]

This affects jammy:linux-oracle-5.15-1040.46 for the 2023.07.10 cycle

[Po-Hsu Lin (cypressyew)]

This is also affecting J-hwe-6.2, despite it's running with 6.2
So I think this is probably userspace related.

[Po-Hsu Lin (cypressyew)]

Looks like:
# With VRF
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# SYSCTL: net.ipv4.ping_group_range=0 2147483647
# SYSCTL: net.ipv4.raw_l3mdev_accept=1
# TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL]

Has gone, verified with:
 * j-aws-5.15.0-1046.51 c4.large, t3a.2xlarge
 * j-5.15.0-85.95 openstack amd64
 * j-gcp-5.15.0-1043.51 n1-standard-64
 * j-azure-5.15.0-1048.55 Standard_D4s_v3-gen2