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.
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
[release-0.58]: Fix: Align Reenlightenment flows between converter.go and template.go #8798
[release-0.58]: Fix: Align Reenlightenment flows between converter.go and template.go #8798
Conversation
ac91562
to
112ba5c
Compare
|
/hold |
While the converter.go logic checked whether we have topology hints defined and that tsc frequency is required (which is the right thing to do), template.go logic did not check the later. In addition, improve IsManualTSCFrequencyRequired() to also check whether topology hints are defined. Signed-off-by: Itamar Holder <iholder@redhat.com>
Signed-off-by: Itamar Holder <iholder@redhat.com>
Signed-off-by: Itamar Holder <iholder@redhat.com>
…e updated Signed-off-by: Itamar Holder <iholder@redhat.com>
That's how we can distinguish between us waiting for a TSC frequency and knowing there is no TSC frequency information, hence we can stop waiting for it. This is necessary, since the vmi controller executes "sync()" and "updateStatus()" in every control loop. If TSC frequency is required, sync() would wait until topology hints would be set up by updateStatus(). Today, updateStatus() doesn't update the topology hints at all if no TSC frequency information exists, therefore sync will continue waiting forever and the VM wouldn't be able to start. Signed-off-by: Itamar Holder <iholder@redhat.com>
…gy hints are updated Signed-off-by: Itamar Holder <iholder@redhat.com>
…ined Signed-off-by: Itamar Holder <iholder@redhat.com>
Signed-off-by: Itamar Holder <iholder@redhat.com>
112ba5c
to
03d63fc
Compare
|
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enp0s3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@iholder-redhat: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
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/test-infra repository. |
|
/test pull-kubevirt-build-0.58 |
|
/retest-required |
|
@iholder101: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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/test-infra repository. |
|
/retest-required |
1 similar comment
|
/retest-required |
|
/retest-required |
What this PR does / why we need it:
Manual backport for #8740.
The reason a manual backport is required is because the functional tests are added to hyperv_test.go which didn't exist in
release-58branch because the PR that created this file wasn't backported.Release note: