Skip to content

Conversation

@jherrman
Copy link
Contributor

@jherrman jherrman commented Jun 25, 2024

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 25, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 25, 2024

@jherrman: This pull request references CNV-38323 which is a valid jira issue.

In response to this:

Version(s):
4.14 (and possibly 4.15 as well)

Issue:
https://issues.redhat.com/browse/CNV-38323

Link to docs preview:
TBA

QE review:

  • 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 Jun 25, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jun 25, 2024

🤖 Wed Sep 04 09:43:15 - Prow CI generated the docs preview:

https://78023--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/release_notes/virt-4-14-release-notes.html

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 25, 2024

@jherrman: This pull request references CNV-38323 which is a valid jira issue.

In response to this:

Version(s):
4.14 (and possibly 4.15 as well)

Issue:
https://issues.redhat.com/browse/CNV-38323

Link to docs preview:
https://78023--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/release_notes/virt-4-14-release-notes.html

QE review:

  • 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.

@jherrman
Copy link
Contributor Author

jherrman commented Jul 2, 2024

Note - As confirmed by Nijin in https://issues.redhat.com/browse/CNV-38323 , this should be applied to enterprise-4.14 as well (most likely via cherry-pick after the initial merge)

@jherrman
Copy link
Contributor Author

jherrman commented Jul 3, 2024

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jul 3, 2024
@dfitzmau
Copy link
Contributor

dfitzmau commented Jul 3, 2024

/remove-label peer-review-needed

/label peer-review-in-progress

@openshift-ci openshift-ci bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jul 3, 2024
@dfitzmau
Copy link
Contributor

dfitzmau commented Jul 3, 2024

Hi @jherrman . The merger would need to know for sure if 4.15 is impacted. Can you confirm? Bug was fixed in 4.16?

Copy link
Contributor

@dfitzmau dfitzmau left a comment

Choose a reason for hiding this comment

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

/remove-label peer-review-in-progress

/label peer-review-done

* Uninstalling {VirtProductName} does not remove the `feature.node.kubevirt.io` node labels created by {VirtProductName}. You must remove the labels manually. (link:https://issues.redhat.com/browse/CNV-22036[*CNV-22036*])

//BZ 2151169
* In a heterogeneous cluster with different compute nodes, virtual machines that have HyperV Reenlightenment enabled cannot be scheduled on nodes that do not support timestamp-counter scaling (TSC) or have the appropriate TSC frequency. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2151169[*BZ#2151169*])
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* In a heterogeneous cluster with different compute nodes, virtual machines that have HyperV Reenlightenment enabled cannot be scheduled on nodes that do not support timestamp-counter scaling (TSC) or have the appropriate TSC frequency. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2151169[*BZ#2151169*])
* In a heterogeneous cluster with different compute nodes, virtual machines that have HyperV reenlightenment enabled cannot be scheduled on nodes that do not support timestamp-counter scaling (TSC) or have the appropriate TSC frequency. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2151169[*BZ#2151169*])

Lowercase according to link.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch, fixed now

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jul 3, 2024
@jherrman
Copy link
Contributor Author

Hi @jherrman . The merger would need to know for sure if 4.15 is impacted. Can you confirm? Bug was fixed in 4.16?

@dfitzmau SME confirmed in https://issues.redhat.com/browse/CNV-38323 that the issue impacts 4.15 and 4.16 as well (and possibly will for 4.17, too).

@dfitzmau
Copy link
Contributor

Thanks, @jherrman . LGTM. WOuld you be OK to update the following description item to state "4.14+"?

Screenshot from 2024-07-22 16-15-19

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 23, 2024

@jherrman: This pull request references CNV-38323 which is a valid jira issue.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/CNV-38323

Link to docs preview:
https://78023--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/release_notes/virt-4-14-release-notes.html

QE review:

  • 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.

@jherrman
Copy link
Contributor Author

Thanks, @jherrman . LGTM. WOuld you be OK to update the following description item to state "4.14+"?

Done, thank you for the heads-up :-)

@dshchedr
Copy link

dshchedr commented Aug 9, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 9, 2024
@jherrman
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Aug 12, 2024
@jab-rh jab-rh added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Aug 12, 2024
@jab-rh
Copy link
Contributor

jab-rh commented Aug 12, 2024

@jherrman, if this is intended for 4.14+, I think this should be a PR against the main branch and not the enterprise-4.14 branch? Thanks!

@jherrman jherrman changed the base branch from enterprise-4.14 to main August 12, 2024 15:27
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 12, 2024

@jherrman: This pull request references CNV-38323 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/CNV-38323

Link to docs preview:
https://78023--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/release_notes/virt-4-14-release-notes.html

QE review:

  • 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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 12, 2024
@jherrman jherrman changed the base branch from main to enterprise-4.14 August 12, 2024 15:28
@openshift-ci-robot
Copy link

@jherrman: This pull request references CNV-38323 which is a valid jira issue.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/CNV-38323

Link to docs preview:
https://78023--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/release_notes/virt-4-14-release-notes.html

QE review:

  • 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 size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 12, 2024
@jherrman
Copy link
Contributor Author

@jherrman, if this is intended for 4.14+, I think this should be a PR against the main branch and not the enterprise-4.14 branch? Thanks!

@jab-rh , my apologies, must have missed that in the OpenShift docs manual. Still, is it necessary? Changing the base branch to "main" complicates the PR quite a lot (due to the many added commits), and it's just a single very simple change, which should be easy to cherry-pick to other branches.

@jab-rh
Copy link
Contributor

jab-rh commented Aug 13, 2024

@kalexand-rh, can this be cherry-picked around from enterprise-4.14 or should this be re-done against main? Thanks!

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 13, 2024
@kalexand-rh
Copy link
Contributor

It's not one of the repo best practices to cherry-pick to main, but if you can find a merge reviewer who is willing to make sure that no other changes creep into other branches, you can.

@jherrman
Copy link
Contributor Author

jherrman commented Sep 3, 2024

Thank you for the info Kathryn!

However, one thing I did not realize earlier is that as an update to Release Notes, this cannot really be merged into Main. Also, as a bug fix description becoming a known issue description, it cannot be easily cherry-picked to the newer branches without conflict (since the newer branches don't contain the original bug fix).

So, this PR should still cover 4.14 (I changed the original description to reflect that) and I created a new one for 4.15 - 4.17: #78023 - which should theoretically be cherry-pickable without much trouble

Hopefully this does the trick, apologies for the shenanigans...

@jab-rh jab-rh removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Sep 3, 2024
@jab-rh
Copy link
Contributor

jab-rh commented Sep 3, 2024

@jherrman, can you squad the commits for this PR? Thank you!

Moved BZ#2151169 into a specific node section

Fixing up a capitalization issue
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 4, 2024
@openshift-ci
Copy link

openshift-ci bot commented Sep 4, 2024

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link

openshift-ci bot commented Sep 4, 2024

@jherrman: 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.

@jherrman
Copy link
Contributor Author

jherrman commented Sep 6, 2024

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Sep 6, 2024
@sheriff-rh sheriff-rh added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Sep 6, 2024
Copy link
Contributor

@sheriff-rh sheriff-rh left a comment

Choose a reason for hiding this comment

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

LGTM, merging.

@sheriff-rh sheriff-rh merged commit 1c82017 into openshift:enterprise-4.14 Sep 6, 2024
@jab-rh jab-rh removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants