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
Bug 1946232: VM List can consume very high CPU #9761
Bug 1946232: VM List can consume very high CPU #9761
Conversation
|
@glekner: An error was encountered searching for bug 1946232 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
could not unmarshal response body: invalid character '<' looking for beginning of value
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
fb26b11
to
7272bab
Compare
|
/retest |
7272bab
to
4a20309
Compare
|
/retest |
|
#9758 - merged /lgtm |
|
/retest |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
4a20309
to
bf53977
Compare
cae5b10
to
1150957
Compare
|
/retest |
|
/retest p.s. |
1f6dd66
to
f7c49e0
Compare
|
/test e2e-gcp-console |
|
/test kubevirt-plugin |
|
/test e2e-gcp-console |
f7c49e0
to
a84beda
Compare
|
/retest |
|
/bugzilla refresh |
|
@yaacov: This pull request references Bugzilla bug 1946232, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
| if (status === VM_STATUS.Running) { | ||
| const { name, namespace } = vmData; | ||
| cy.waitForLoginPrompt(name, namespace); | ||
| } | ||
|
|
||
| if (status === VM_STATUS.Starting) { |
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.
a. https://github.com/kubevirt/user-guide/pull/439/files
maybe we may report starting when real status is provisioning ?
we should look at the logic for reporting "starting" and see if in some cases we should report "provisioning" instead ?
b. can we make a new method
export const waitForStatuses = (statuses: string[], vmData?: VirtualMachineData, timeout?: number) => {
and use it when we can continue if we see one of the correct statuses ?
e.g.
continue to next step if vm status is in ["starting", "provisioning"] acceptable statuses list ...
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: glekner, yaacov 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 |
| @@ -87,7 +87,7 @@ describe('Test VM creation', () => { | |||
| }); | |||
| }); | |||
|
|
|||
| [urlVM, registryVM, pvcVM, pxeVM].forEach((vmData) => { | |||
| [urlVM, registryVM, pvcVM].forEach((vmData) => { | |||
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.
NOTE:
this is skipping the PXE test, we will need to re-introduce this test once we fix the test flakynes
I don't think the PXE test flakynes is connected to this PR
|
@glekner: All pull requests linked via external trackers have merged: Bugzilla bug 1946232 has been moved to the MODIFIED state. 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. |
@glekner (cc @yaacov) sorry for the delayed response (was on vacation 😎). This behavior is actually by design. The different VM states aren't mutually exclusive, some of them coexist (e.g., Stopped and Provisioning, or Running and Migrating). Since we include only one state in |

blocked by #9758