Bug 1573796

Summary:	[OSP10] 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:	Archit Modi <amodi>
Severity:	low	Docs Contact:
Priority:	low
Version:	10.0 (Newton)	CC:	achernet, berrange, dbecker, jcoufal, jschluet, kchamart, madgupta, mbooth, mburns, morazi, mschuppe, owalsh, ratailor, rhel-osp-director-maint, sgordon, slee
Target Milestone:	z9	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-5.3.10-11.el7ost puppet-nova-9.6.0-6.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-09-17 16:54:55 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, 1597997
Bug Blocks:	1573787, 1573791, 1573793

Comment 13 Alex McLeod 2018-09-03 07:57:51 UTC

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 15 errata-xmlrpc 2018-09-17 16:54:55 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