Skip to content

OCPBUGS-78165: fixes for dpu-intel-ipu-p4sdk hermetic build#632

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.20from
fgallott:hermetic-4.20
Mar 31, 2026
Merged

OCPBUGS-78165: fixes for dpu-intel-ipu-p4sdk hermetic build#632
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.20from
fgallott:hermetic-4.20

Conversation

@fgallott
Copy link
Copy Markdown
Contributor

cherry pick of 3f8aefc, #629

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 24, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@fgallott: This pull request explicitly references no jira issue.

Details

In response to this:

cherry pick of 3f8aefc, #629

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.

@fgallott
Copy link
Copy Markdown
Contributor Author

/jira cherrypick OCPBUGS-78164

@openshift-ci-robot
Copy link
Copy Markdown

@fgallott: Jira Issue OCPBUGS-78164 has been cloned as Jira Issue OCPBUGS-78165. Will retitle bug to link to clone.
/retitle OCPBUGS-78165: NO-JIRA: fixes for dpu-intel-ipu-p4sdk hermetic build

Details

In response to this:

/jira cherrypick OCPBUGS-78164

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-ci Bot changed the title NO-JIRA: fixes for dpu-intel-ipu-p4sdk hermetic build OCPBUGS-78165: NO-JIRA: fixes for dpu-intel-ipu-p4sdk hermetic build Mar 10, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@fgallott: This pull request references Jira Issue OCPBUGS-78165, 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". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-78164 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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:

cherry pick of 3f8aefc, #629

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.

@fgallott fgallott changed the title OCPBUGS-78165: NO-JIRA: fixes for dpu-intel-ipu-p4sdk hermetic build OCPBUGS-78165: fixes for dpu-intel-ipu-p4sdk hermetic build Mar 10, 2026
@fgallott
Copy link
Copy Markdown
Contributor Author

/retest

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@fgallott
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 27, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@fgallott: This pull request references Jira Issue OCPBUGS-78165, 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.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-78164 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-78164 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhiqiangf

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

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.

@openshift-ci openshift-ci Bot requested a review from zhiqiangf March 27, 2026 13:49
rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@fgallott
Copy link
Copy Markdown
Contributor Author

/test make-test

@fgallott
Copy link
Copy Markdown
Contributor Author

@wizhaoredhat I think this one is ready to be reviewed, it's a backport of #629, and the failing tests are the same as in the other pr

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/approve

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/lgtm

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 31, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@wizhaoredhat: The verified label has been added.

Details

In response to this:

/verified bypass

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.

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Mar 31, 2026
@wizhaoredhat
Copy link
Copy Markdown
Contributor

/approve

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 31, 2026
@wizhaoredhat
Copy link
Copy Markdown
Contributor

/lgtm

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/override ci/prow/make-e2e-test
/override ci/prow/make-e2e-test-marvell

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 31, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgallott, wizhaoredhat

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:

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

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 31, 2026

@wizhaoredhat: Overrode contexts on behalf of wizhaoredhat: ci/prow/make-e2e-test, ci/prow/make-e2e-test-marvell

Details

In response to this:

/override ci/prow/make-e2e-test
/override ci/prow/make-e2e-test-marvell

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
Copy link
Copy Markdown

openshift-ci Bot commented Mar 31, 2026

@fgallott: 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-merge-bot openshift-merge-bot Bot merged commit a462d40 into openshift:release-4.20 Mar 31, 2026
10 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@fgallott: Jira Issue OCPBUGS-78165: All pull requests linked via external trackers have merged:

All linked pull requests have the verified tag. Jira Issue OCPBUGS-78165 has been moved to the VERIFIED state.

Details

In response to this:

cherry pick of 3f8aefc, #629

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants