[release-4.15] OCPBUGS-33023: update egressFWTestE2E image which contains ping binary

[openshift-cherrypick-robot]

This is an automated cherry-pick of #28408

/assign werled

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-20487 has been cloned as Jira Issue OCPBUGS-33023. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-33023: update egressFWTestE2E image which contains ping binary

In response to this:

This is an automated cherry-pick of #28408

/assign werled

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-33023, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected dependent Jira Issue OCPBUGS-20487 to target a version in 4.16.0, but it targets "4.15.0" 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.

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

In response to this:

This is an automated cherry-pick of #28408

/assign werled

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 openshift-eng/jira-lifecycle-plugin repository.

[routerhan]

/retest-required

[routerhan]

/jira refresh

[openshift-ci-robot]

@routerhan: This pull request references Jira Issue OCPBUGS-33023, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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 openshift-eng/jira-lifecycle-plugin repository.

[routerhan]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.z) matches configured target version for branch (4.15.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-20487 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-20487 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

Requesting review from QA contact:
/cc @djslavens

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 openshift-eng/jira-lifecycle-plugin repository.

[routerhan]

/jira refresh

[openshift-ci-robot]

@routerhan: This pull request references Jira Issue OCPBUGS-33023, which is invalid:

• expected dependent Jira Issue OCPBUGS-20487 to target a version in 4.16.0, but it targets "4.15.0" 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 openshift-eng/jira-lifecycle-plugin repository.

[routerhan]

/jira refresh

[openshift-ci-robot]

@routerhan: This pull request references Jira Issue OCPBUGS-33023, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.z) matches configured target version for branch (4.15.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-20487 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-20487 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

Requesting review from QA contact:
/cc @djslavens

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 openshift-eng/jira-lifecycle-plugin repository.

[djslavens]

/lgtm

[werled]

/retest-required

[knobunc]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djslavens, knobunc, openshift-cherrypick-robot

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:

• test/extended/networking/OWNERS [knobunc]

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

[routerhan]

/label backport-risk-assessed

[openshift-ci]

@routerhan: Can not set label backport-risk-assessed: Must be member in one of these teams: [openshift-staff-engineers]

In response to this:

/label backport-risk-assessed

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-sigs/prow repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2320880 and 2 for PR HEAD b2a3add in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD c13a01e and 1 for PR HEAD b2a3add in total

[openshift-ci]

@openshift-cherrypick-robot: 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-aws-ovn-single-node	b2a3add	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial	b2a3add	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-csi	b2a3add	link	false	/test e2e-gcp-csi
ci/prow/e2e-metal-ipi-sdn	b2a3add	link	false	/test e2e-metal-ipi-sdn
ci/prow/e2e-aws-ovn-single-node-upgrade	b2a3add	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-agnostic-ovn-cmd	b2a3add	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-etcd-recovery	b2a3add	link	false	/test e2e-aws-etcd-recovery
ci/prow/e2e-gcp-ovn-rt-upgrade	b2a3add	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-gcp-ovn	b2a3add	link	true	/test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-ipv6	b2a3add	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-fips	b2a3add	link	true	/test e2e-aws-ovn-fips

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