ubuntu_fan_smoke_test failed with "Error: Unsupported attribute." on J-oem-6.5
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned | |||
linux (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Invalid
|
Undecided
|
Unassigned | |||
Mantic |
Incomplete
|
Undecided
|
Unassigned | |||
linux-oem-6.5 (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Fix Released
|
Undecided
|
Unassigned | |||
Mantic |
Invalid
|
Undecided
|
Unassigned | |||
ubuntu-fan (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Invalid
|
Undecided
|
Unassigned | |||
Mantic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Issue found with J-oem-6.5.0-1002
The ubuntu_
Error: Unsupported attribute.
$ fanatic enable-fan -u 172.17.0.0/16 -o 250.0.0.0/8
configuring fan underlay:
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.
/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-
/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.
Error: Unsupported attribute.
$ ip addr
1: lo: <LOOPBACK,
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,
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:
valid_lft forever preferred_lft forever
3: lxcbr0: <NO-CARRIER,
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,
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
description: | updated |
description: | updated |
Changed in linux-oem-6.5 (Ubuntu): | |
status: | New → Invalid |
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 "