Bug 1573787
| Summary: | [OSP13] live-migration uses port range from ephemeral port range | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Rajesh Tailor <ratailor> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Rajesh Tailor <ratailor> |
| Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 13.0 (Queens) | CC: | achernet, berrange, dbecker, jcoufal, joflynn, jschluet, kchamart, lyarwood, mbooth, mburns, morazi, owalsh, ratailor, rhel-osp-director-maint, sgordon, slee, svanders |
| Target Milestone: | z2 | Keywords: | Triaged, ZStream |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-8.0.2-48.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, libvirtd live-migration used ports 49152 to 49215, as specified in the qemu.conf file. On Linux, this range is a subset of the ephemeral port range 32768 to 61000. Any port in the ephemeral range can be consumed by any other service as well.
As a result, live-migration failed with the error:
Live Migration failure: internal error: Unable to find an unused port in range 'migration' (49152-49215).
The new libvirtd live-migration range of 61152 to 61215 is not in the ephemeral range.
|
Story Points: | --- |
| Clone Of: | 1313507 | Environment: | |
| Last Closed: | 2018-08-29 16:35:54 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: | |||
| Bug Depends On: | 1313507, 1573791, 1573793, 1573796, 1597541 | ||
| Bug Blocks: | |||
|
Comment 14
Joanne O'Flynn
2018-08-15 08:06:09 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/RHBA-2018:2574 |