[release-4.20] OCPBUGS-63751: PPC: ghw: filter out namespaces dir

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1403

/assign shajmakh

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-60218 has been cloned as Jira Issue OCPBUGS-63751. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-63751: PPC: ghw: filter out namespaces dir

Details

In response to this:

This is an automated cherry-pick of #1403

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

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-60218 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

Details

In response to this:

This is an automated cherry-pick of #1403

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

[jmencak]

/lgtm
/approved
/label backport-risk-assessed

[yanirq]

/jira refresh

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-60218 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.

Details

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.

[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

Details

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

[shajmakh]

/jira refresh

[openshift-ci-robot]

@shajmakh: This pull request references Jira Issue OCPBUGS-63751, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-60218 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-60218 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

Details

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.

[shajmakh]

/label verified-later
@mrniranjan

[openshift-ci]

@shajmakh: The label(s) /label verified-later cannot be applied. These labels are supported: acknowledge-critical-fixes-only, 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, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, ok-to-test, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label verified-later
@mrniranjan

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.

[shajmakh]

/verified-later

[shajmakh]

/verified later @mrniranjan

[openshift-ci-robot]

@shajmakh: This PR has been marked to be verified later by @mrniranjan.

Details

In response to this:

/verified later @mrniranjan

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]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[openshift-ci-robot]

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

• openshift/cluster-node-tuning-operator#1421

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-63751 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #1403

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

[shajmakh]

/cherry-pick release-4.19

[openshift-cherrypick-robot]

@shajmakh: #1421 failed to apply on top of branch "release-4.19":

Applying: PPC: pkg: public consts to private
Using index info to reconstruct a base tree...
A	pkg/performanceprofile/profilecreator/ghwhandler.go
A	pkg/performanceprofile/profilecreator/mustgather.go
M	pkg/performanceprofile/profilecreator/profilecreator.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/performanceprofile/profilecreator/profilecreator.go
CONFLICT (modify/delete): pkg/performanceprofile/profilecreator/mustgather.go deleted in HEAD and modified in PPC: pkg: public consts to private. Version PPC: pkg: public consts to private of pkg/performanceprofile/profilecreator/mustgather.go left in tree.
CONFLICT (modify/delete): pkg/performanceprofile/profilecreator/ghwhandler.go deleted in HEAD and modified in PPC: pkg: public consts to private. Version PPC: pkg: public consts to private of pkg/performanceprofile/profilecreator/ghwhandler.go left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 PPC: pkg: public consts to private

Details

In response to this:

/cherry-pick release-4.19

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.