[release-4.12] OCPBUGS-27840: Bump openshift-kni/debug-tools to 0.1.8

[openshift-cherrypick-robot]

This is an automated cherry-pick of #966

/assign rbaturov

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-25819 has been cloned as Jira Issue OCPBUGS-27840. Will retitle bug to link to clone. /retitle [release-4.12] OCPBUGS-27840: Bump openshift-kni/debug-tools to 0.1.8

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/968): >This is an automated cherry-pick of #966 > >/assign rbaturov Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-25819 to target a version in 4.13.0, 4.13.z, but it targets "4.14.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](https://github.com/openshift-kni/performance-addon-operators/pull/968): >This is an automated cherry-pick of #966 > >/assign rbaturov Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[yanirq]

/jira refresh

[openshift-ci-robot]

@yanirq: This pull request references Jira Issue OCPBUGS-27840, which is invalid:

• expected dependent Jira Issue OCPBUGS-27754 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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](https://github.com/openshift-kni/performance-addon-operators/pull/968#issuecomment-1907855014): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[yanirq]

/jira refresh

[openshift-ci-robot]

@yanirq: This pull request references Jira Issue OCPBUGS-27840, which is invalid:

• expected Jira Issue OCPBUGS-27840 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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](https://github.com/openshift-kni/performance-addon-operators/pull/968#issuecomment-1909921008): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[yanirq]

/jira refresh

[openshift-ci-robot]

@yanirq: This pull request references Jira Issue OCPBUGS-27840, which is invalid:

• expected dependent Jira Issue OCPBUGS-27754 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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](https://github.com/openshift-kni/performance-addon-operators/pull/968#issuecomment-1909925921): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[yanirq]

/lgtm /approve

[openshift-ci[bot]]

[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](https://github.com/openshift-kni/performance-addon-operators/blob/release-4.12/OWNERS)~~ [yanirq] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[rbaturov]

/jira refresh

[openshift-ci-robot]

@rbaturov: This pull request references Jira Issue OCPBUGS-27840, 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.12.z) matches configured target version for branch (4.12.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-27754](https://issues.redhat.com//browse/OCPBUGS-27754) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-27754](https://issues.redhat.com//browse/OCPBUGS-27754) targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z * bug has dependents

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

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/968#issuecomment-1914450070): >/jira refresh > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-27840: All pull requests linked via external trackers have merged:

• openshift-kni/performance-addon-operators#968

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

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/968): >This is an automated cherry-pick of #966 > >/assign rbaturov Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift-kni%2Fperformance-addon-operators). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.