Bug 1094506

Summary:	Instances will not boot after upgrade because of missing required config for neutron/nova notifications
Product:	Red Hat OpenStack	Reporter:	Lars Kellogg-Stedman <lars>
Component:	openstack-neutron	Assignee:	Jakub Libosvar <jlibosva>
Status:	CLOSED ERRATA	QA Contact:	Toni Freger <tfreger>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 6)	CC:	breeler, chrisw, ihrachys, jlibosva, lpeer, mkolesni, nyechiel, oblaut, sclewis, sgordon, yeylon
Target Milestone:	rc
Target Release:	5.0 (RHEL 6)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2014.1-27.el6ost	Doc Type:	Bug Fix
Doc Text:	In Red Hat Enterprise Linux OpenStack Platform 5.0, OpenStack Networking notifies Compute about port status changes, and to do so it requires Identity credentials in the file neutron.conf. Prior to this update, an instance's network ports were not created if the Compute (nova) API configuration was missing from neutron.conf. This update addresses this issue by disabling 'nova-neutron' notifications by default in Red Hat Enterprise Linux OpenStack Platform 5.0. As a result, instances will boot without dependency on the notification feature. Enabling Compute's notifications is recommended in order to mitigate race behavior issues. This is managed in the following neutron.conf parameters: notify_nova_port_status_changes=true notify_nova_on_port_data_changes=true nova_url=http://[nova_api]:[nova_api_port]/v2 nova_admin_username=[admin_username] nova_admin_password=[admin_password] nova_admin_tenant_id=[admin_tenant_id] nova_admin_auth_url=http://[keystone_service_ip]:[keystone_port]/v2.0 With this workaround in place, OpenStack Networking will correctly notify Compute of port changes.	Story Points:	---
Clone Of:	1093879	Environment:
Last Closed:	2014-07-28 18:58:12 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:	1114291
Bug Blocks:	1067211, 1093877

Description Lars Kellogg-Stedman 2014-05-05 20:57:17 UTC

+++ This bug was initially created as a clone of Bug #1093879 +++

As identified in https://bugzilla.redhat.com/show_bug.cgi?id=1087529 and probably elsewhere, Neutron in Icehouse notifies Nova about port status changes, and to do so it requires keystone credentials in neutron.conf.

After an upgrade for Havana to Icehouse, instances will fail to spawn because the required configuration is missing.

Our packages should do something to make this process more transparent.  Maybe modify the neutron-server startup to abort with an error if the appropriate configuration cannot be found?

--- Additional comment from Lars Kellogg-Stedman on 2014-05-05 16:56:19 EDT ---

We could handle this as we handled the database versioning check in the RHEL Havana packages, by running a check script prior to starting the service and exiting with an explanatory message if the appropriate configuration is not in place.

Comment 4 Nir Yechiel 2014-06-09 17:37:58 UTC

*** Bug 1106509 has been marked as a duplicate of this bug. ***

Comment 9 Toni Freger 2014-07-21 11:02:34 UTC

From Havana:
http://download.lab.bos.redhat.com/rel-eng/OpenStack/4.0/2014-07-15.2
To Icehouse :
http://download.lab.bos.redhat.com/rel-eng/OpenStack/5.0-RHEL-6/2014-07-18.1

All-in-one + Compute node, GRE

After manual configuration of the neutron.conf new VMs launched successfully.

Comment 15 Ihar Hrachyshka 2014-07-24 08:54:07 UTC

@Jakub, what do you mean by saying that 'That sounds to me like notifications will be also disabled if you have a clean install which is not true.'? I thought that we disable it in neutron-dist.conf unconditionally, and it's a matter of user or installer to enable those notifications back.

Meaning, even for new installations it will be disabled.

Or am I missing smth?

Comment 17 Ihar Hrachyshka 2014-07-24 10:07:22 UTC

@Jakub, I think we still don't have Staypuft in the wild. And packstack is a PoC tool. And AFAIK we recommend users to deploy manually if they need a real setup. So, it's not that we should not make customers aware of that fact that notifications are disabled by default.

Comment 19 errata-xmlrpc 2014-07-28 18:58:12 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.

http://rhn.redhat.com/errata/RHEA-2014-0953.html

Comment 20 Jakub Libosvar 2014-09-01 11:16:53 UTC

(In reply to Ihar Hrachyshka from comment #17)
> @Jakub, I think we still don't have Staypuft in the wild. And packstack is a
> PoC tool. And AFAIK we recommend users to deploy manually if they need a
> real setup. So, it's not that we should not make customers aware of that
> fact that notifications are disabled by default.

You're right, for deployment done manually administrator needs to enable notifications by himself.