search

openshift-kni / performance-addon-operators

Operators related to optimizing OpenShift clusters for applications sensitive to cpu and network latency
Apache License 2.0
45 stars 60 forks source link

OCPBUGS-25819: Bump openshift-kni/debug-tools to 0.1.8 #966

Closed rbaturov closed 8 months ago

rbaturov commented 8 months ago

This version introduces a solution for not collecting pod_info file by Must Gather. More info here: https://github.com/openshift-kni/debug-tools/releases/tag/v0.1.8

Fixes OCPBUGS-25819

openshift-ci-robot commented 8 months ago

@rbaturov: This pull request references Jira Issue OCPBUGS-25819, which is invalid:

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/966): >This version introduces a solution for not collecting pod_info file by Must Gather. More info here: https://github.com/openshift-kni/debug-tools/releases/tag/v0.1.8 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[bot] commented 8 months ago

Hi @rbaturov. Thanks for your PR.

I'm waiting for a openshift-kni 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
yanirq commented 8 months ago

/ok-to-test

ffromani commented 8 months ago

This version introduces a solution for not collecting pod_info file by Must Gather. More info here: https://github.com/openshift-kni/debug-tools/releases/tag/v0.1.8

note we build older version of must-gather from this repo. You'll need a similar PR against https://github.com/openshift/cluster-node-tuning-operator

openshift-ci[bot] commented 8 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, rbaturov

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/master/OWNERS)~~ [ffromani] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
ffromani commented 8 months ago

@rbaturov: This pull request references Jira Issue OCPBUGS-25819, which is invalid:

* expected the bug to target the "4.16.0" version, but no target version was set

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.

@rbaturov

rbaturov commented 8 months ago

/jira refresh

openshift-ci-robot commented 8 months ago

@rbaturov: This pull request references Jira Issue OCPBUGS-25819, which is invalid:

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/966#issuecomment-1887303729): >/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 commented 8 months ago

@rbaturov: No Jira issue is referenced in the title of this pull request. To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/966): >This version introduces a solution for not collecting pod_info file by Must Gather. More info here: https://github.com/openshift-kni/debug-tools/releases/tag/v0.1.8 > >Fixes OCPBUGS-25819 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 commented 8 months ago

/jira refresh

openshift-ci-robot commented 8 months ago

@yanirq: No Jira issue is referenced in the title of this pull request. To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/966#issuecomment-1890941632): >/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 commented 7 months ago

/cherry-pick release-4.13

openshift-cherrypick-robot commented 7 months ago

@yanirq: new pull request created: #967

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/966#issuecomment-1905925722): >/cherry-pick release-4.13 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
openshift-ci-robot commented 7 months ago

@rbaturov: Jira Issue OCPBUGS-25819 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/966): >This version introduces a solution for not collecting pod_info file by Must Gather. More info here: https://github.com/openshift-kni/debug-tools/releases/tag/v0.1.8 > >Fixes OCPBUGS-25819 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.
rbaturov commented 7 months ago

/cherry-pick release-4.12

openshift-cherrypick-robot commented 7 months ago

@rbaturov: new pull request created: #968

In response to [this](https://github.com/openshift-kni/performance-addon-operators/pull/966#issuecomment-1907841247): >/cherry-pick release-4.12 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.