Skip to content

OCPBUGS-77164: d/s only: install kmod for mstfwreset support#1173

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
SchSeba:add_kmod_ds
Apr 15, 2026
Merged

OCPBUGS-77164: d/s only: install kmod for mstfwreset support#1173
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
SchSeba:add_kmod_ds

Conversation

@SchSeba
Copy link
Copy Markdown
Contributor

@SchSeba SchSeba commented Feb 25, 2026

this is needed when the version of mstfwreset will be >= v4.32

this is needed when the version of mstfwreset will be >= v4.32

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
@openshift-ci openshift-ci Bot requested review from kunalmemane and pliurh February 25, 2026 12:25
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 25, 2026
@zeeke
Copy link
Copy Markdown
Contributor

zeeke commented Feb 26, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SchSeba, zeeke

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

@cgoncalves
Copy link
Copy Markdown
Contributor

/retitle OCPBUGS-77164: d/s only: install kmod for mstfwreset support

@openshift-ci openshift-ci Bot changed the title d/s only: install kmod for mstfwreset support OCPBUGS-77164: d/s only: install kmod for mstfwreset support Feb 26, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Feb 26, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@SchSeba: This pull request references Jira Issue OCPBUGS-77164, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ajaggapa

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

Details

In response to this:

this is needed when the version of mstfwreset will be >= v4.32

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 ajaggapa February 26, 2026 15:46
@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Mar 10, 2026

Thanks!
/verified bypass

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

@SchSeba: The verified label has been added.

Details

In response to this:

Thanks!
/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.

@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Mar 10, 2026

/retest

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD aa5235a and 2 for PR HEAD 77864c2 in total

@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Mar 15, 2026

/override ci/prow/operator-e2e-sriov-sno

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 15, 2026

@SchSeba: Overrode contexts on behalf of SchSeba: ci/prow/operator-e2e-sriov-sno

Details

In response to this:

/override ci/prow/operator-e2e-sriov-sno

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.

@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Mar 18, 2026

/retest

1 similar comment
@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Mar 18, 2026

/retest

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3a29196 and 1 for PR HEAD 77864c2 in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 29e2a2d and 0 for PR HEAD 77864c2 in total

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

/hold

Revision 77864c2 was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 1, 2026
@kunalmemane
Copy link
Copy Markdown
Member

/unassign @kunalmemane

@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Apr 12, 2026

/retest

@openshift-bot
Copy link
Copy Markdown
Contributor

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-bot: This pull request references Jira Issue OCPBUGS-77164, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @ajaggapa

Details

In response to this:

/jira refresh

The requirements for Jira bugs have changed (Jira issues linked to PRs on main branch need to target different OCP), recalculating validity.

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.

@SchSeba
Copy link
Copy Markdown
Contributor Author

SchSeba commented Apr 15, 2026

/retest
/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 15, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

@SchSeba: 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 336917d into openshift:main Apr 15, 2026
12 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@SchSeba: Jira Issue OCPBUGS-77164: All pull requests linked via external trackers have merged:

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

Details

In response to this:

this is needed when the version of mstfwreset will be >= v4.32

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. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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.

6 participants