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-43091: Remove restart required msg from affinity and node selector #2047

Conversation

metalice
Copy link
Member

📝 Description

I am removing the restart required message from the affinity and node selector models as they are now live update, and no restart is needed if they are live migratable.

🎥 Demo

After:
image

image

Before:
image

image

@openshift-ci-robot
Copy link
Collaborator

openshift-ci-robot commented Jun 19, 2024

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

In response to this:

📝 Description

I am removing the restart required message from the affinity and node selector models as they are now live update, and no restart is needed if they are live migratable.

🎥 Demo

After:
image

image

Before:
image

image

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 requested review from upalatucci and yaacov June 19, 2024 06:20
@openshift-ci openshift-ci bot added the approved This issue is something we want to fix label Jun 19, 2024
Copy link
Member

Choose a reason for hiding this comment

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

I think here we need to completely remove the affinity and node selector references from this function.
We don't need to check with getChangedAffinity and getChangedNodeSelector if there are discrepancies between VM and vmi for that right?

Copy link
Member Author

Choose a reason for hiding this comment

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

I left it because of a situation where the machine isn't live migratable, so it still shows a message of pending changes. However, we won't show it in most cases, so I removed it from the main modal. In most cases, it's not relevant anymore, but in the some cases, it is applicable, so the pending changes in the global VM details message will cover it.

@upalatucci
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Passed code review, ready for merge label Jun 20, 2024
Copy link
Contributor

openshift-ci bot commented Jun 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: metalice, 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:
  • OWNERS [metalice,upalatucci]

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 67c5f76 into kubevirt-ui:main Jun 20, 2024
10 checks passed
@gouyang
Copy link
Member

gouyang commented Aug 12, 2024

/cherry-pick release-4.16

@openshift-cherrypick-robot
Copy link
Collaborator

@gouyang: new pull request created: #2123

In response to this:

/cherry-pick release-4.16

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.

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.

5 participants