Bug 1448806
| Summary: | Missing doc of tls migrate in man virsh help | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | zhe peng <zpeng> |
| Component: | libvirt | Assignee: | John Ferlan <jferlan> |
| Status: | CLOSED ERRATA | QA Contact: | Yanqiu Zhang <yanqzhan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.4 | CC: | dyuan, rbalakri, xuzhang, yanqzhan |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-3.2.0-5.el7 | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-02 00:08:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
zhe peng
2017-05-08 08:36:14 UTC
Patch posted upstream: https://www.redhat.com/archives/libvir-list/2017-May/msg00270.html Now pushed upstream:
commit c390f55e4b8cbdd3262d367ca477f6489ae69239
Author: John Ferlan <jferlan>
Date: Wed May 10 10:07:31 2017 -0400
virsh: Add --tls description for the virsh man page
...
Commit id '6a8d898d' neglected to update the man page.
$ git describe c390f55e4b8cbdd3262d367ca477f6489ae69239
v3.3.0-31-gc390f55
$
Verify with libvirt-3.2.0-5.el7.x86_64.
# man virsh
migrate [--live] [--offline] [--direct] ... [--tls]
...
Providing --tls causes the migration to use the host configured TLS setup (see
migrate_tls_x509_cert_dir in /etc/libvirt/qemu.conf) in order to perform the migration of the domain.
Usage requires proper TLS setup for both source and target.
Since the result is as expected, mark this bug as verified.
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-2017:1846 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-2017:1846 |