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
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
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