Skip to content

CNV-63496: DOC: UI: Live migration to specific node#98824

Merged
ousleyp merged 1 commit intoopenshift:mainfrom
sbeskin-redhat:CNV_63496_UI_Live_migration_to_specific_node
Sep 17, 2025
Merged

CNV-63496: DOC: UI: Live migration to specific node#98824
ousleyp merged 1 commit intoopenshift:mainfrom
sbeskin-redhat:CNV_63496_UI_Live_migration_to_specific_node

Conversation

@sbeskin-redhat
Copy link
Contributor

@sbeskin-redhat sbeskin-redhat commented Sep 10, 2025

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

openshift-ci-robot commented Sep 10, 2025

@sbeskin-redhat: This pull request references CNV-63496 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 story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Resolves: https://issues.redhat.com/browse/CNV-63496

CNV-4.20
OCP-4.20

Preview:

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/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Sep 10, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 10, 2025

@sbeskin-redhat: This pull request references CNV-63496 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 story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Resolves: https://issues.redhat.com/browse/CNV-63496

CNV-4.20
OCP-4.20

Preview: https://98824--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/live_migration/virt-initiating-live-migration.html#virt-initiating-vm-migration-web_virt-initiating-live-migration

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.

@pcbailey
Copy link

Looks good to me!

@lkladnit
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2025
@sbeskin-redhat sbeskin-redhat force-pushed the CNV_63496_UI_Live_migration_to_specific_node branch from 67632ea to 2757fd3 Compare September 15, 2025 10:07
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2025
@sbeskin-redhat
Copy link
Contributor Author

/retest

@lkladnit
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 16, 2025
@lkladnit lkladnit removed their assignment Sep 16, 2025
@ousleyp ousleyp added CNV Label for all CNV PRs branch/enterprise-4.20 labels Sep 16, 2025
@ousleyp ousleyp added this to the Planned for 4.20 GA milestone Sep 16, 2025
Copy link
Member

@ousleyp ousleyp left a comment

Choose a reason for hiding this comment

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

This almost LGTM, but I have a minimalism suggestion for you to consider. :) Thanks!

Comment on lines 29 to 32
. In the *Migrate Virtual Machine to a different Node* dialog box, select either the *Automatically Selected Node* or the *Specific Node* option.
. If you selected the *Automatically Selected Node* option, click *Migrate Virtual Machine*.
+
If you selected the *Specific Node* option, choose the required node from the list displayed in the dialog box and click *Migrate Virtual Machine*.
Copy link
Member

@ousleyp ousleyp Sep 16, 2025

Choose a reason for hiding this comment

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

This feels a tad convoluted. Here's a suggestion to simplify it:

Suggested change
. In the *Migrate Virtual Machine to a different Node* dialog box, select either the *Automatically Selected Node* or the *Specific Node* option.
. If you selected the *Automatically Selected Node* option, click *Migrate Virtual Machine*.
+
If you selected the *Specific Node* option, choose the required node from the list displayed in the dialog box and click *Migrate Virtual Machine*.
. In the *Migrate Virtual Machine to a different Node* dialog box, select either *Automatically Selected Node* or *Specific Node*.
.. If you selected the *Specific Node* option, select a node from the list.
. Click *Migrate Virtual Machine*.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@ousleyp Thank you, I made the changes. Could you merge it?

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 17, 2025
@openshift-ci
Copy link

openshift-ci bot commented Sep 17, 2025

New changes are detected. LGTM label has been removed.

@sbeskin-redhat sbeskin-redhat force-pushed the CNV_63496_UI_Live_migration_to_specific_node branch from f639e93 to c9eb563 Compare September 17, 2025 11:54
@openshift-ci
Copy link

openshift-ci bot commented Sep 17, 2025

@sbeskin-redhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@ousleyp
Copy link
Member

ousleyp commented Sep 17, 2025

LGTM!

@ousleyp ousleyp merged commit 3ce2244 into openshift:main Sep 17, 2025
2 checks passed
@ousleyp
Copy link
Member

ousleyp commented Sep 17, 2025

/cherrypick enterprise-4.20

@openshift-cherrypick-robot

@ousleyp: new pull request created: #99257

Details

In response to this:

/cherrypick enterprise-4.20

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

branch/enterprise-4.20 CNV Label for all CNV PRs jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants