Ubuntu
iperf package

iperf >2.0.13 blocks mininet 2.3.0 tests (e.g. in openvswitch autopkgtest)

Bug #1936796 reported by Christian Ehrhardt 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
iperf (Ubuntu)
Fix Released
Undecided
Unassigned
mininet (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi,
this is the return of bug 1919432
Sadly upstream mininet did not continue on it https://github.com/mininet/mininet/issues/1060

Due to that we need to resolve it somehow or we will stay behind the new iperf for (too) long.

The details in the links above are long, but the TL;DR is:
- iperf changed the output in a few cases
- mininet needs to adapt in a way not loosing the ability to
  wait for output

I'll try to apply my upstream suggestion if it lets the new iperf/openvsitch pass with valid results.
If it does I'll ask jamespage (for openvswitch experience) to have a look.

See original description

Related branches

~paelzer/ubuntu/+source/mininet:impish-lp-1936796
James Page (community): Approve
Christian Ehrhardt : Approve
Diff: 60 lines (+40/-0)
3 files modified
debian/changelog (+12/-0)
debian/patches/fix-new-iperf.patch (+27/-0)
debian/patches/series (+1/-0)
Christian Ehrhardt  (paelzer)
tags: added: update-excuse
description: updated
Christian Ehrhardt  (paelzer)
Changed in iperf (Ubuntu):
status: New → Confirmed
Changed in mininet (Ubuntu):
status: New → Triaged
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

After various tests in launchpad infrastructure I can confirm that my upstream suggested fix works (for us).
Therfore I have nudged upstream again and prepared a merge proposal to fix the package.
=> https://code.launchpad.net/~paelzer/ubuntu/+source/mininet/+git/mininet/+merge/405896

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

MP Review complete, uploading new mininet to resolve the issue in Impish.

Changed in iperf (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

https://launchpad.net/ubuntu/+source/mininet/2.3.0-1ubuntu1 built and works fine AFAICS.

The openvswitch tests of iperf triggered with the new mininet worked as well:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/o/openvswitch/20210720_113258_ddb48@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/o/openvswitch/20210720_113229_c5208@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/o/openvswitch/20210720_113130_db5a1@/log.gz
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/o/openvswitch/20210720_113246_d5712@/log.gz

Thereby iperf should migrate as well as hopefully mininet itself once all tets are completed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mininet - 2.3.0-1ubuntu1

---------------
mininet (2.3.0-1ubuntu1) impish; urgency=medium

  * d/p/fix-new-iperf.patch: avoid hangs with iperf >2.0.13 (LP: #1936796)

 -- Christian Ehrhardt <email address hidden> Mon, 19 Jul 2021 11:06:11 +0200

Changed in mininet (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

And by that iperf migrated as well
   iperf | 2.1.2+dfsg1-1 | impish/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x

Changed in iperf (Ubuntu):
status: Won't Fix → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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