Bug 1597997
Summary: | [OSP10]Failed to host-evacuate-live VM after migration port change in BZ1573796 | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Martin Schuppert <mschuppe> |
Component: | openstack-tripleo-heat-templates | Assignee: | Martin Schuppert <mschuppe> |
Status: | CLOSED ERRATA | QA Contact: | Archit Modi <amodi> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 10.0 (Newton) | CC: | amcleod, augol, berrange, b.j.smith, ccamacho, dasmith, eglynn, jhakimra, kchamart, madgupta, mburns, mschuppe, nova-maint, owalsh, sbauza, sferdjao, sgordon, srevivo, vromanso, yprokule |
Target Milestone: | z9 | Keywords: | Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | puppet-tripleo-5.6.8-10.el7ost openstack-tripleo-heat-templates-5.3.10-11.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 also be consumed by any other service.
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).
With this update, the new libvirtd live-migration range of 61152-61215 is not in the ephemeral range and the related failures no longer occur.
This completes the port change work started in BZ1573796.
|
Story Points: | --- |
Clone Of: | 1597313 | Environment: | |
Last Closed: | 2018-09-17 16:56:14 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: | 1597313 | ||
Bug Blocks: | 1573796 |
Comment 11
Alex McLeod
2018-09-03 08:04:07 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:2670 It actually looks like RHBA-2018:2670 causes an issue on *new* compute nodes deployed without re-deployment of *all* compute nodes that existed prior to RHBA-2018:2670, even if those compute nodes were updated and rebooted. See Case 02246671 - https://access.redhat.com/support/cases/#/case/02246671 |