Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1232664

Summary:	A hostname change breaks neutron-openvswitch-agent / neutron-server tunneling updates.
Product:	Red Hat OpenStack	Reporter:	Miguel Angel Ajo <majopela>
Component:	openstack-neutron	Assignee:	Miguel Angel Ajo <majopela>
Status:	CLOSED ERRATA	QA Contact:	Alexander Stafeyev <astafeye>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.0 (Kilo)	CC:	chrisw, fdinitto, ihrachys, mburns, nyechiel, oblaut, sclewis, tfreger, yeylon
Target Milestone:	ga
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2015.1.0-11.el7ost	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:27:17 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:
Bug Blocks:	1185030, 1251948, 1261487

Description Miguel Angel Ajo 2015-06-17 09:16:13 UTC

Description of problem:

When using tunnelling, if one of the hosts changed the hostname and tries to sync tunnels to neutron-server, this will throw an exception due to an unnecessary constraint, breaking the network.

Hostname changes are something neutron-server may survive to. Probably a log warning is enough, and the old hostname endpoint should be deleted.

Version-Release number of selected component (if applicable):

openstack-neutron-2015.1.0-8

How reproducible:

Always

Steps to Reproduce:
1. Install a single node AIO with tunnelling for tenant networks.
2. openstack-config --set /etc/neutron/neutron.conf DEFAULT host newhostname
3. service neutron-openvswitch-agent restart


Actual results:

 The exceptions keep happening for neutron-server in a loop as the agent tries to sync the tunnel, and fail.

Expected results:
 The hostname change doesn't break anything.

Additional info:
The bug was introduced by this commit
https://github.com/openstack/neutron/commit/3db0e619c83892a7aab61807969205253833ff8d

Comment 4 Alexander Stafeyev 2015-07-14 07:13:14 UTC

verified with the reproduction steps 

openstack-neutron-common-2015.1.0-11.el7ost.noarch
python-neutron-lbaas-2015.1.0-5.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-11.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
python-neutron-2015.1.0-11.el7ost.noarch
openstack-neutron-2015.1.0-11.el7ost.noarch
openstack-neutron-ml2-2015.1.0-11.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-5.el7ost.noarch

Comment 6 errata-xmlrpc 2015-08-05 13:27:17 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/RHEA-2015:1548