ubuntu_fan_smoke_test failed with "Error: Unsupported attribute." on J-oem-6.5

Bug #2031845 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
Mantic
Incomplete
Undecided
Unassigned
linux-oem-6.5 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
Mantic
Invalid
Undecided
Unassigned
ubuntu-fan (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Invalid
Undecided
Unassigned
Mantic
Invalid
Undecided
Unassigned

Bug Description

Issue found with J-oem-6.5.0-1002

The ubuntu_fan_smoke_test failed with:
    Error: Unsupported attribute.

$ fanatic enable-fan -u 172.17.0.0/16 -o 250.0.0.0/8
configuring fan underlay:172.17.0.0/16 overlay:250.0.0.0/8
Error: Unsupported attribute.
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables v1.8.7 (nf_tables): Chain 'fan-egress' does not exist
Try `iptables -h' or 'iptables --help' for more information.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanctl: /etc/network/fan:40 172.17.0.0/16 250.0.0.0/8 -- failed err=1
/usr/sbin/fanatic: unable to bring fan up, unable to configure

It is the ip command execute in fanctl script (called by fanatic) that trigger this "Error: Unsupported attribute." error:
$ ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16
Error: Unsupported attribute.

$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8942 qdisc fq_codel state UP group default qlen 1000
    link/ether fa:16:3e:b9:7c:28 brd ff:ff:ff:ff:ff:ff
    altname enp0s3
    inet 10.134.252.19/24 metric 100 brd 10.134.252.255 scope global dynamic ens3
       valid_lft 33248sec preferred_lft 33248sec
    inet6 fe80::f816:3eff:feb9:7c28/64 scope link
       valid_lft forever preferred_lft forever
3: lxcbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:52:9f:ef:1d brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

Po-Hsu Lin (cypressyew)
description: updated
description: updated
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

It looks like this "fan-map 250.0.0.0/8:172.17.0.0/16" in ip command is the cause, there will be no error if you just run "ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 "

Po-Hsu Lin (cypressyew)
Changed in linux-oem-6.5 (Ubuntu):
status: New → Invalid
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

On Mantic 6.5.0-1, this test is failing with "Error: Unsupported attribute." as well:
 Running './ubuntu_fan_smoke_test.sh 172.17.0.0/16'
 Testing Fan Networking (pre-0.13.0 API)
 docker pull --platform linux/amd64 ubuntu: PASSED
 Error: Unsupported attribute.
 /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev docker0 dstport 0 local 172.17.0.1 fan-map 250.0.0.0/8:172.17.0.0/16
 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
 RTNETLINK answers: Cannot assign requested address
 iptables v1.8.7 (nf_tables): Chain 'fan-egress' does not exist
 Try `iptables -h' or 'iptables --help' for more information.
 iptables: Bad rule (does a matching rule exist in that chain?).
 iptables: Bad rule (does a matching rule exist in that chain?).
 iptables: No chain/target/match by that name.
 rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
 /usr/sbin/fanatic: unable to bring fan up, unable to configure
 enable disable fan test: FAILED (fanatic enable-fan returned 1)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Download full text (3.6 KiB)

dmesg output for M-6.5.0-1
[ 352.031564] audit: type=1400 audit(1693220500.981:33): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=1659 comm="apparmor_parser"
[ 352.911515] evict_inodes inode 00000000205cc785, i_count = 1, was skipped!
[ 352.911543] evict_inodes inode 00000000a73aa397, i_count = 1, was skipped!
[ 352.911547] evict_inodes inode 00000000a48ed503, i_count = 1, was skipped!
[ 352.911550] evict_inodes inode 00000000d7a5b101, i_count = 1, was skipped!
[ 352.911552] evict_inodes inode 000000008d6cd4b7, i_count = 1, was skipped!
[ 353.138871] evict_inodes inode 000000008fd27656, i_count = 1, was skipped!
[ 353.138883] evict_inodes inode 00000000b245b883, i_count = 1, was skipped!
[ 353.138886] evict_inodes inode 00000000d351735e, i_count = 1, was skipped!
[ 353.138889] evict_inodes inode 000000006975ebb1, i_count = 1, was skipped!
[ 353.312882] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 353.317179] Bridge firewalling registered
[ 353.754638] Initializing XFRM netlink socket
[ 354.367037] evict_inodes inode 0000000059663c47, i_count = 1, was skipped!
[ 354.367050] evict_inodes inode 00000000d351735e, i_count = 1, was skipped!
[ 354.367053] evict_inodes inode 00000000b245b883, i_count = 1, was skipped!
[ 354.367056] evict_inodes inode 000000006975ebb1, i_count = 1, was skipped!
[ 354.367059] evict_inodes inode 000000008fd27656, i_count = 1, was skipped!
[ 368.181558] evict_inodes inode 00000000a0469036, i_count = 1, was skipped!
[ 368.181571] evict_inodes inode 00000000e22170ad, i_count = 1, was skipped!
[ 368.181575] evict_inodes inode 00000000c5b66dae, i_count = 1, was skipped!
[ 368.181578] evict_inodes inode 00000000fcbdb5db, i_count = 1, was skipped!
[ 368.181580] evict_inodes inode 000000008cbd5695, i_count = 1, was skipped!
[ 368.390582] evict_inodes inode 00000000e0e23502, i_count = 1, was skipped!
[ 368.390594] evict_inodes inode 00000000a8c89f20, i_count = 1, was skipped!
[ 368.390597] evict_inodes inode 00000000baa782d3, i_count = 1, was skipped!
[ 368.390600] evict_inodes inode 00000000625c7de9, i_count = 1, was skipped!
[ 369.399411] evict_inodes inode 000000006975ebb1, i_count = 1, was skipped!
[ 369.399440] evict_inodes inode 00000000b245b883, i_count = 1, was skipped!
[ 369.399443] evict_inodes inode 000000008fd27656, i_count = 1, was skipped!
[ 369.399446] evict_inodes inode 00000000d351735e, i_count = 1, was skipped!
[ 369.399449] evict_inodes inode 0000000059663c47, i_count = 1, was skipped!
[ 370.683508] evict_inodes inode 00000000d351735e, i_count = 1, was skipped!
[ 370.683521] evict_inodes inode 000000008fd27656, i_count = 1, was skipped!
[ 370.683525] evict_inodes inode 0000000059663c47, i_count = 1, was skipped!
[ 370.683528] evict_inodes inode 00000000b245b883, i_count = 1, was skipped!
[ 370.683531] evict_inodes inode 000000006975ebb1, i_count = 1, was skipped!
[ 370.892217] evict_inodes inode 000000008d6cd4b7, i_count = 1, was skipped!
[ 370.892230] evict_inodes inode 00000000a73aa397, i_count = 1, was skipped!
[ 370.892233] evict_inode...

Read more...

Changed in linux (Ubuntu Jammy):
status: New → Invalid
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 2031845

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

With test kernel provided by Andrea
https://launchpad.net/~arighi/+archive/ubuntu/linux?field.series_filter=mantic

The test can pass, with some known ZFS UBSAN: array-index-out-of-bounds error in dmesg.

 Testing Fan Networking (pre-0.13.0 API)
 docker pull --platform linux/amd64 ubuntu: PASSED
 enable disable fan test: PASSED
 fanctl show test: PASSED
 fanctl check bridge config test: PASSED
 fanatic docker test(--dns=10.246.72.3): PASSED
                GOOD ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-test timestamp=1693300037 localtime=Aug 29 09:07:17 completed successfully
        END GOOD ubuntu_fan_smoke_test.fan-smoke-test ubuntu_fan_smoke_test.fan-smoke-test timestamp=1693300037 localtime=Aug 29 09:07:17

$ uname -a
Linux autovm4 6.5.0-2-generic #2+arighi2-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 29 03:34:56 UTC 20 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue does not exist with J-oem-6.5.0-1004.4 anymore.

Changed in linux-oem-6.5 (Ubuntu Jammy):
status: New → Fix Released
Changed in ubuntu-fan (Ubuntu Jammy):
status: New → Invalid
Changed in ubuntu-fan (Ubuntu Mantic):
status: New → Invalid
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

This issue still exists with Mantic 6.5.0-5.5, keep this open.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.