OCPBUGS-3819: Add bond cni test

[mmirecki]

Adding a test case for the bond-cni.
The test checks if a pod with a bond is created successfully, and then checks connectivity between two pods with bond interfaces.

[openshift-ci]

@mmirecki: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Add bond cni test

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.

[openshift-ci]

@mmirecki: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-csi	41b7130	link	false	/test e2e-gcp-csi
ci/prow/e2e-aws-single-node-upgrade	41b7130	link	false	/test e2e-aws-single-node-upgrade
ci/prow/e2e-aws-cgroupsv2	41b7130	link	false	/test e2e-aws-cgroupsv2

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[cgoncalves]

/lgtm

[openshift-ci]

@mmirecki: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

CNF-6648: Add bond cni test

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.

[mmirecki]

/jira refresh

[openshift-ci-robot]

@mmirecki: No Jira bug is referenced in the title of this pull request.
To reference a bug, add 'OCPBUGS-XXX:' to the title of this pull request and request another bug refresh with /jira refresh.

In response to this:

/jira refresh

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.

[openshift-ci]

@mmirecki: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-3819: Add bond cni test

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.

[openshift-ci-robot]

@mmirecki: This pull request references Jira Issue OCPBUGS-3819, which is invalid:

• expected Jira Issue OCPBUGS-3819 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Adding a test case for the bond-cni.
The test checks if a pod with a bond is created successfully, and then checks connectivity between two pods with bond interfaces.

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.

[mmirecki]

/jira refresh

[openshift-ci-robot]

@mmirecki: This pull request references Jira Issue OCPBUGS-3819, which is invalid:

• expected Jira Issue OCPBUGS-3819 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[mmirecki]

/jira refresh

[openshift-ci-robot]

@mmirecki: This pull request references Jira Issue OCPBUGS-3819, which is invalid:

• expected Jira Issue OCPBUGS-3819 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[mmirecki]

/jira refresh

[openshift-ci-robot]

@mmirecki: This pull request references Jira Issue OCPBUGS-3819, which is invalid:

• expected Jira Issue OCPBUGS-3819 to depend on a bug targeting a version in 4.12.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[cgoncalves]

/jira refresh

[openshift-ci-robot]

@cgoncalves: This pull request references Jira Issue OCPBUGS-3819, which is invalid:

• expected dependent Jira Issue OCPBUGS-3820 to target a version in 4.12.0, but it targets "4.12.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[cgoncalves]

/jira refresh

[openshift-ci-robot]

@cgoncalves: This pull request references Jira Issue OCPBUGS-3819, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.11.z) matches configured target version for branch (4.11.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-3820 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-3820 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (weliang@redhat.com), skipping review request.

In response to this:

/jira refresh

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.

[mmirecki]

/cc @knobunc
Could you please take a look

[mmirecki]

@knobunc @deads2k @dcbw @danwinship @smarterclayton @bparees @mfojtik
Can you please take a look at this?

[knobunc]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgoncalves, knobunc, mmirecki

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:

• OWNERS [knobunc]

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

[mmirecki]

@dgoodwin @akram @coreydaley @dmage @gangwgr @jadhaj @jitendar-singh
Could you please apply the backport-risk-assessed, cherry-pick-approved labels?
Thanks

[jadhaj]

/label cherry-pick-approved

[mmirecki]

@kasturinarra @pamoedom @prietyc123 @stbenjam
Can you please apply the backport-risk-assessed label?
Thanks

[pamoedom]

Hi @mmirecki, please note that from the persons you pinged above, only @stbenjam has credentials to add backport-risk-assessed label. You can check here the whole list for both labels if needed.

Regards.

[bparees]

i'll apply it manually. Given this is affecting tests and not production code, the risk is low (the only real risk is that it opens a hole for a regression to be introduced elsewhere, and since it's adding tests, not changing them, that risk is also low)

[openshift-ci-robot]

@mmirecki: All pull requests linked via external trackers have merged:

• openshift/origin#27554

Jira Issue OCPBUGS-3819 has been moved to the MODIFIED state.

In response to this:

Adding a test case for the bond-cni.
The test checks if a pod with a bond is created successfully, and then checks connectivity between two pods with bond interfaces.

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.