start-iperf3 can fail to start on device if it has multiple IP addresses

Bug #2036263 reported by Rod Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas-cert-server
Fix Committed
Undecided
Rod Smith

Bug Description

The start-iperf3 script can fail to start iperf3 on a device if that device has multiple IP addresses. For instance:

$ ip addr show dev ens4f0
2: ens4f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:16:0c:ae:28:3a brd ff:ff:ff:ff:ff:ff
    altname enp23s0f0
    inet 10.1.11.121/23 brd 10.1.11.255 scope global ens4f0
       valid_lft forever preferred_lft forever
    inet 10.245.130.75/21 brd 10.245.135.255 scope global ens4f0
       valid_lft forever preferred_lft forever
    inet6 fe80::8616:cff:feae:283a/64 scope link
       valid_lft forever preferred_lft forever
$ ./start-iperf3 -a 10.1.11.121 -n 1
NUMA node of ens4f0 is 0....
Will use CPU cores: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47]....
Launching: iperf3 -sD -B 10.1.11.121 -p 5201 -A0
$ ./start-iperf3 -a 10.245.130.75 -n 1
Could not find a network device associated with 10.245.130.75!

Although the device has IP addresses 10.1.11.121 and 10.245.130.75, start-iperf3 can launch iperf3 on the former address only, not on the latter address.

Related branches

Rod Smith (rodsmith)
Changed in maas-cert-server:
assignee: nobody → Rod Smith (rodsmith)
Rod Smith (rodsmith)
Changed in maas-cert-server:
status: New → Fix Committed
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.