Skip to content
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

CNV-55107: loading on vm change #2408

Merged
merged 1 commit into from
Feb 3, 2025

Conversation

upalatucci
Copy link
Member

@upalatucci upalatucci commented Jan 31, 2025

📝 Description

On VM change, we wait only for the VM to be fetched. We should also wait for the instancetype spec expansion request
Changing VMs without waiting will make the screen flickering between the previous instance and the other

🎥 Demo

Before

Screen.Recording.2025-01-31.at.15.14.37.mov

After

Screen.Recording.2025-01-31.at.15.10.49.mov

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 31, 2025

@upalatucci: This pull request references CNV-55107 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.19.0" version, but no target version was set.

In response to this:

📝 Description

On VM change, we wait only for the VM to be fetched. We should also wait for the instancetype spec expansion request
Changing VMs without waiting will make the screen flickering between the previous instance and the other

🎥 Demo

Before

Screen.Recording.2025-01-31.at.15.14.37.mov

After
https://github.com/user-attachments/assets/a752b893-9d51-4a88-ba03-31f26f4e2b31

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 approved This issue is something we want to fix label Jan 31, 2025
@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jan 31, 2025

@upalatucci: This pull request references CNV-55107 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.19.0" version, but no target version was set.

In response to this:

📝 Description

On VM change, we wait only for the VM to be fetched. We should also wait for the instancetype spec expansion request
Changing VMs without waiting will make the screen flickering between the previous instance and the other

🎥 Demo

Before

Screen.Recording.2025-01-31.at.15.14.37.mov

After

Screen.Recording.2025-01-31.at.15.10.49.mov

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.

params={params}
{...props}
/>
<StateHandler loaded={!expandedSpecLoading} withBullseye>
Copy link
Member

Choose a reason for hiding this comment

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

how this works for VMs created with templates or YML?

Copy link
Member Author

Choose a reason for hiding this comment

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

works great. THe expandedSpecLoading is false from the start with template vms

@avivtur
Copy link
Member

avivtur commented Feb 3, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Feb 3, 2025
Copy link
Contributor

openshift-ci bot commented Feb 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: avivtur, upalatucci

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 21b502f into kubevirt-ui:main Feb 3, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved This issue is something we want to fix jira/valid-reference lgtm Passed code review, ready for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants