Skip to content

OCPBUGS-56496-19: Removed the SR-IOV Operator from the 4.19 release n… #97473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 18, 2025
Merged

OCPBUGS-56496-19: Removed the SR-IOV Operator from the 4.19 release n… #97473

merged 1 commit into from
Aug 18, 2025

Conversation

dfitzmau
Copy link
Contributor

@dfitzmau dfitzmau commented Aug 13, 2025 •
edited
Loading

CM sent on the 15th of August. Merge on the 18th.

Version(s):
4.19

Issue:
OCPBUGS-56496 and OCPBUGS-58291

Link to docs preview:

  • SME has approved this change (William Zhao).
  • QE has approved this change (Zhiqiang Fang).

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 13, 2025
@openshift-ci-robot
Copy link

@dfitzmau: This pull request references Jira Issue OCPBUGS-56496, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done-Errata) 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:

Version(s):
4.19

Issue:
OCPBUGS-56496

Link to docs preview:

  • SME has approved this change.
  • QE has approved this change.

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 added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 13, 2025
@ocpdocs-previewbot
Copy link

🤖 Wed Aug 13 09:34:38 - Prow CI generated the docs preview:

https://97473--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-19-release-notes.html

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Aug 13, 2025

@dfitzmau: all tests passed!

Full PR test history. Your PR dashboard.

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.

@zhiqiangf
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 14, 2025
@wizhaoredhat
Copy link

/lgtm

@dfitzmau dfitzmau added the merge-review-needed Signifies that the merge review team needs to review this PR label Aug 14, 2025
@jeana-redhat jeana-redhat added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Aug 14, 2025
@jeana-redhat jeana-redhat added this to the Continuous Release milestone Aug 14, 2025
jeana-redhat
jeana-redhat reviewed Aug 14, 2025
View reviewed changes
Copy link
Contributor

@jeana-redhat jeana-redhat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, does it need change mgmt?

/remove-label merge-review-in-progress
/remove-label merge-review-needed

@openshift-ci openshift-ci bot removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Aug 14, 2025
@dfitzmau
Copy link
Contributor Author

LGTM, does it need change mgmt?

/remove-label merge-review-in-progress /remove-label merge-review-needed

It does. MY apologies. I've sent out about 3 to 4 of these this week, so I missed this one.

@dfitzmau dfitzmau added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 15, 2025
@dfitzmau dfitzmau merged commit cf33ba2 into openshift:enterprise-4.19 Aug 18, 2025
2 checks passed
@openshift-ci-robot
Copy link

@dfitzmau: Jira Issue OCPBUGS-56496 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state.

In response to this:

CM sent on the 15th of August. Merge on the 18th.

Version(s):
4.19

Issue:
OCPBUGS-56496 and OCPBUGS-58291

Link to docs preview:

  • SME has approved this change (William Zhao).
  • QE has approved this change (Zhiqiang Fang).

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
Reviewers

@jeana-redhat jeana-redhat jeana-redhat left review comments

Assignees

@zhiqiangf zhiqiangf

@wizhaoredhat wizhaoredhat

Labels
branch/enterprise-4.19 do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
Continuous Release
Development

Successfully merging this pull request may close these issues.
6 participants
@dfitzmau @openshift-ci-robot @ocpdocs-previewbot @zhiqiangf @wizhaoredhat @jeana-redhat