OCPBUGS-63: e2e: performance: update path of latency binary

[openshift-cherrypick-robot]

This is an automated cherry-pick of #443

/assign shajmakh

[shajmakh]

/test e2e-upgrade

[shajmakh]

/retitle OCPBUGS-63: e2e: performance: update path of latency binary

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references [Jira Issue OCPBUGS-63](https://issues.redhat.com//browse/OCPBUGS-63), which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST)
• dependent bug [Jira Issue OCPBUGS-65](https://issues.redhat.com//browse/OCPBUGS-65) is in the state Verified (Done), which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent [Jira Issue OCPBUGS-65](https://issues.redhat.com//browse/OCPBUGS-65) targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
• bug has dependents

In response to this:

This is an automated cherry-pick of #443

/assign shajmakh

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]

@openshift-cherrypick-robot: 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-63: e2e: performance: update path of latency binary

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]

@openshift-cherrypick-robot: all tests passed!

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.

[shajmakh]

@MarSik / @yanirq can you provide approved and backport-risk-assessed please?

[shajmakh]

/label cherry-pick-approved
/lgtm

[MarSik]

/label backport-risk-assessed
/label approved
/label lgtm

[openshift-ci]

@MarSik: Can not set label approved: Must be member in one of these teams: [openshift-release-oversight]

In response to this:

/label backport-risk-assessed
/label approved
/label lgtm

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]

@MarSik: The label(s) /label lgtm cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, approved, backport-risk-assessed, cherry-pick-approved

In response to this:

/label backport-risk-assessed
/label approved
/label lgtm

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.

[yanirq]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [yanirq]

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

[openshift-ci-robot]

@openshift-cherrypick-robot: Some pull requests linked via external trackers have merged:

• openshift/cluster-node-tuning-operator#402
• openshift/cluster-node-tuning-operator#401

The following pull requests linked via external trackers have not merged:

• openshift/cluster-node-tuning-operator#446 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

This is an automated cherry-pick of #443

/assign shajmakh

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.