RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1455023 - Give a warning when using --timeout-postcopy without --postcopy
Summary: Give a warning when using --timeout-postcopy without --postcopy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: zhe peng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-24 05:04 UTC by yafu
Modified: 2018-04-10 10:46 UTC (History)
7 users (show)

Fixed In Version: libvirt-3.8.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 10:44:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0704 0 None None None 2018-04-10 10:46:10 UTC

Description yafu 2017-05-24 05:04:06 UTC
Description of problem:
Since the option --timeout-postcopy does not take effect without option --postcopy, so it's better to give a warning when using --timeout-postcopy without --postcopy.

How reproducible:
100%


Version-Release number of selected component (if applicable):
libvirt-3.2.0-5.virtcov.el7.x86_64
qemu-kvm-rhev-2.9.0-5.el7.x86_64

Steps to reproduce:
#virsh migrate rhel7.3 rhel7.3 qemu+ssh://10.66.144.29/system --live --verbose --timeout-postcopy --timeout 5

Actual results:
Migration completed with precopy.

Expected results:
Give a warning like:
warning: Option --postcopy is required by option --timeout-postcopy

Comment 2 Jiri Denemark 2017-09-11 14:33:15 UTC
Fixed upstream by

commit ecd53ca43a7512621066e6c3c3964b805d3debb1
Refs: v3.7.0-41-gecd53ca43a
Author:     Jiri Denemark <jdenemar>
AuthorDate: Fri Sep 8 18:15:13 2017 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Mon Sep 11 16:29:05 2017 +0200

    virsh: migrate --timeout-postcopy requires --postcopy

    Requesting an automated switch to a post-copy migration (using
    --timeout-postcopy) without actually enabling post-copy migration (using
    --postcopy) doesn't really do anything. Let's make this dependency
    explicit to avoid unexpected behavior.

    https://bugzilla.redhat.com/show_bug.cgi?id=1455023

    Signed-off-by: Jiri Denemark <jdenemar>

Comment 4 zhe peng 2017-11-28 03:31:43 UTC
verify with build:
libvirt-3.9.0-3.el7.x86_64

step:
# virsh migrate --live rhel7.2 qemu+ssh://$target_host/system --verbose --timeout-postcopy --timeout 5
error: Option --postcopy is required by option --timeout-postcopy

Comment 8 errata-xmlrpc 2018-04-10 10:44:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0704


Note You need to log in before you can comment on or make changes to this bug.