Fix netperf docker image build failure

[bitmeal]

What this PR does / why we need it:

What

• Update netperf container base from debian:jessie to debian:bullseye
• Add CFLAGS=-fcommon to build of netperf binary

Why

• The default image sirot/netperf-latest used by the netperf test crashes when given the -testFrom and -testTo parameters. These parameters cannot be turned off, but are implicitly set when omitted by user; introduced by Add qperf support to netperf for network benchmarking #2144.
• debian:jessie container on docker hub is ~2 years old: apt repo keys are expired, thus preventing dependency installation and container build
• After upgrade to debian:bullseye, with a newer compiler, netperf needs -fcommon flag for building (as workaround); see nettest_omni: Remove duplicate variable definitions HewlettPackard/netperf#46

Relevance/Value

Updating the container is necessary to run the tests at all, fixing a regression introduced by the additionally passed parameters from #2144

Which issue(s) this PR fixes:

NONE

Special notes for your reviewer:

NONE

What type of PR is this?

/kind bug
/kind regression

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: bitmeal (456482e)

[k8s-ci-robot]

Welcome @bitmeal!

It looks like this is your first PR to kubernetes/perf-tests 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/perf-tests has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @bitmeal. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[marseel]

Could you take a look at it Dorde?
/assign @dlapcevic

[dlapcevic]

Thanks @bitmeal.
/approve

[dlapcevic]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bitmeal, dlapcevic

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• network/OWNERS [dlapcevic]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment