Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1597997 - [OSP10]Failed to host-evacuate-live VM after migration port change in BZ1573796
[OSP10]Failed to host-evacuate-live VM after migration port change in BZ1573796
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
10.0 (Newton)
Unspecified Unspecified
urgent Severity urgent
: z9
: 10.0 (Newton)
Assigned To: Martin Schuppert
Archit Modi
: Triaged, ZStream
Depends On: 1597313
Blocks: 1573796
  Show dependency tree / graph
 
Reported: 2018-07-04 02:20 EDT by Martin Schuppert
Modified: 2018-11-05 18:47 EST (History)
20 users (show)

See Also:
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 12:56:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1779820 None None None 2018-07-04 02:20 EDT
Red Hat Product Errata RHBA-2018:2670 None None None 2018-09-17 12:57 EDT

  None (edit)
Comment 11 Alex 2018-09-03 04:04:07 EDT 
Hi there,

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field.

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Thanks,
Alex
Comment 13 errata-xmlrpc 2018-09-17 12:56:14 EDT 
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
Comment 14 Bryan J. Smith 2018-11-05 18:47:34 EST 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.