Skip to content

DOCPLAN#108: [CQA Stories] Pre-migration corrections for live migration#108213

Merged
ousleyp merged 1 commit intoopenshift:mainfrom
aspauldi:DOCPLAN-108
Mar 16, 2026
Merged

DOCPLAN#108: [CQA Stories] Pre-migration corrections for live migration#108213
ousleyp merged 1 commit intoopenshift:mainfrom
aspauldi:DOCPLAN-108

Conversation

@aspauldi
Copy link

@aspauldi aspauldi commented Mar 11, 2026

Version(s): 4.16+

Issue: DOCPLAN-108

Link to docs preview:
The following live migration modules and assembly are updated in this PR:

QE review: N/A (DITA compliance only)

Additional information:
Tagged for Version 4.16+ following advice in Slack (https://redhat-internal.slack.com/archives/GN1MK7XQC/p1772807830949479)

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 11, 2026
@aspauldi
Copy link
Author

/retest

@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 11, 2026
@aspauldi aspauldi changed the title DOCPLAN#108: [CQA Stories] Pre-migration correction needed for virt-configuring-live-migration.adoc DOCPLAN#108: [CQA Stories] Pre-migration corrections for live migration Mar 12, 2026
Copy link
Contributor

Choose a reason for hiding this comment

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

Requirement Status Notes
Short Description Meets You successfully included the [role="_abstract"] attribute.+4
Terminology Meets Uses official names like "KubeVirt" and "CLI" correctly.
Structure Meets No level 2-5 nested sections are present.
Block Titles Meets The title on the YAML example (Line 95) will not trigger a Vale error.

@rheslop
Copy link
Contributor

rheslop commented Mar 13, 2026

/LGTM

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 is looking pretty good! Just a few comments. :)

Comment on lines +47 to +57
`<bandwidthPerMigration>`:: Specifies the bandwidth of each migration as a quantity-of-bytes-per-second value. For example, a value of 2048Mi means 2048 MiB/s. Default: 0, which is unlimited.
+
`<completionTimeoutPerGiB>`:: Specifies the length of time, in seconds per GiB of memory, at which the migration is canceled if it has not completed. For example, a VM with 6GiB memory times out if it has not completed migration in 4800 seconds. If the `Migration Method` is `BlockMigration`, the size of the migrating disks is included in the calculation.
+
`<parallelMigrationsPerCluster>`:: Specifies the number of migrations running in parallel in the cluster. Default: `5`.
+
`<parallelOutboundMigrationsPerNode>`:: Specifies the maximum number of outbound migrations per node. Default: `2`.
+
`<progressTimeout>`:: Specifies the length of time, in seconds, at which the migration is canceled if memory copy fails to make progress. Default: `150`.
+
`<allowPostCopy>`:: Specifies whether the post copy mode is enabled. You can enable post copy mode to allow the migration of one node to another to converge, even if a VM is running a heavy workload and the memory dirty rate is too high. By default, `allowPostCopy` is set to `false`.
Copy link
Member

Choose a reason for hiding this comment

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

Same comment about < >s

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 16, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link

openshift-ci bot commented Mar 16, 2026

@aspauldi: 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 ousleyp merged commit 54ea91d into openshift:main Mar 16, 2026
2 checks passed
@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.22

@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.21

@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.20

@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.19

@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.18

@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.17

@ousleyp
Copy link
Member

ousleyp commented Mar 16, 2026

/cherrypick enterprise-4.16

@openshift-cherrypick-robot

@ousleyp: new pull request created: #108409

Details

In response to this:

/cherrypick enterprise-4.22

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.

@openshift-cherrypick-robot

@ousleyp: new pull request created: #108410

Details

In response to this:

/cherrypick enterprise-4.21

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.

@openshift-cherrypick-robot

@ousleyp: new pull request created: #108411

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.

@openshift-cherrypick-robot

@ousleyp: #108213 failed to apply on top of branch "enterprise-4.19":

Applying: DITA compliance
Using index info to reconstruct a base tree...
M	modules/virt-configuring-a-live-migration-policy.adoc
M	modules/virt-configuring-live-migration-heavy.adoc
M	modules/virt-configuring-live-migration-limits.adoc
M	virt/live_migration/virt-configuring-live-migration.adoc
Falling back to patching base and 3-way merge...
Auto-merging virt/live_migration/virt-configuring-live-migration.adoc
CONFLICT (content): Merge conflict in virt/live_migration/virt-configuring-live-migration.adoc
Auto-merging modules/virt-configuring-live-migration-limits.adoc
CONFLICT (content): Merge conflict in modules/virt-configuring-live-migration-limits.adoc
Auto-merging modules/virt-configuring-live-migration-heavy.adoc
Auto-merging modules/virt-configuring-a-live-migration-policy.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 DITA compliance

Details

In response to this:

/cherrypick enterprise-4.19

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.

@openshift-cherrypick-robot

@ousleyp: #108213 failed to apply on top of branch "enterprise-4.18":

Applying: DITA compliance
Using index info to reconstruct a base tree...
M	modules/virt-configuring-a-live-migration-policy.adoc
M	modules/virt-configuring-live-migration-heavy.adoc
M	modules/virt-configuring-live-migration-limits.adoc
M	virt/live_migration/virt-configuring-live-migration.adoc
Falling back to patching base and 3-way merge...
Auto-merging virt/live_migration/virt-configuring-live-migration.adoc
CONFLICT (content): Merge conflict in virt/live_migration/virt-configuring-live-migration.adoc
Auto-merging modules/virt-configuring-live-migration-limits.adoc
CONFLICT (content): Merge conflict in modules/virt-configuring-live-migration-limits.adoc
Auto-merging modules/virt-configuring-live-migration-heavy.adoc
Auto-merging modules/virt-configuring-a-live-migration-policy.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 DITA compliance

Details

In response to this:

/cherrypick enterprise-4.18

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.

@openshift-cherrypick-robot

@ousleyp: #108213 failed to apply on top of branch "enterprise-4.17":

Applying: DITA compliance
Using index info to reconstruct a base tree...
M	modules/virt-configuring-a-live-migration-policy.adoc
M	modules/virt-configuring-live-migration-heavy.adoc
M	modules/virt-configuring-live-migration-limits.adoc
M	virt/live_migration/virt-configuring-live-migration.adoc
Falling back to patching base and 3-way merge...
Auto-merging virt/live_migration/virt-configuring-live-migration.adoc
CONFLICT (content): Merge conflict in virt/live_migration/virt-configuring-live-migration.adoc
Auto-merging modules/virt-configuring-live-migration-limits.adoc
CONFLICT (content): Merge conflict in modules/virt-configuring-live-migration-limits.adoc
Auto-merging modules/virt-configuring-live-migration-heavy.adoc
Auto-merging modules/virt-configuring-a-live-migration-policy.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 DITA compliance

Details

In response to this:

/cherrypick enterprise-4.17

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.

@openshift-cherrypick-robot

@ousleyp: #108213 failed to apply on top of branch "enterprise-4.16":

Applying: DITA compliance
Using index info to reconstruct a base tree...
M	modules/virt-configuring-a-live-migration-policy.adoc
A	modules/virt-configuring-live-migration-heavy.adoc
M	modules/virt-configuring-live-migration-limits.adoc
M	virt/live_migration/virt-configuring-live-migration.adoc
Falling back to patching base and 3-way merge...
Auto-merging virt/live_migration/virt-configuring-live-migration.adoc
CONFLICT (content): Merge conflict in virt/live_migration/virt-configuring-live-migration.adoc
Auto-merging modules/virt-configuring-live-migration-limits.adoc
CONFLICT (content): Merge conflict in modules/virt-configuring-live-migration-limits.adoc
CONFLICT (modify/delete): modules/virt-configuring-live-migration-heavy.adoc deleted in HEAD and modified in DITA compliance. Version DITA compliance of modules/virt-configuring-live-migration-heavy.adoc left in tree.
Auto-merging modules/virt-configuring-a-live-migration-policy.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 DITA compliance

Details

In response to this:

/cherrypick enterprise-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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants