Bug 1093879

Summary:	Instances will not boot after upgrade because of missing required config for neutron/nova notifications
Product:	[Community] RDO	Reporter:	Lars Kellogg-Stedman <lars>
Component:	openstack-neutron	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ofer Blaut <oblaut>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	chrisw, ihrachys, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2014.1.1-3.el6 openstack-neutron-2014.1.1-5.el7 openstack-neutron-2014.1.1-5.fc21	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1094506 1106509 (view as bug list)		Environment:
Last Closed:	2015-03-14 02:10: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:
Bug Blocks:	1093877, 1106509

Description Lars Kellogg-Stedman 2014-05-03 00:48:09 UTC

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?

Comment 1 Lars Kellogg-Stedman 2014-05-05 20:56:19 UTC

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 2 Alan Pevec 2014-05-29 09:37:06 UTC

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

Default notify_nova_on_port_status_changes = True is wrong IMHO, and we should change it to False in dist.conf.
That way upgrades would work and be functionally no worse than the previous release while still allowing installers to change it to True along with all required parameters.
Startup script could issue a warning that configuration is sub-optional, but should not abort.

Comment 3 Ihar Hrachyshka 2014-06-27 15:56:36 UTC

Jakub, I think it was you who fixed that in RHOSP 5. Can you make sure the fix arrives to RDO too?

Comment 4 Ihar Hrachyshka 2014-07-02 10:40:37 UTC

The fix in RHOSP is cb937956c9bcc703ca00f0c916daa9b1b56b1237 for RHEL7, and e18deeab2fc171d0a3843f1476c24295151052d6 for RHEL6. They should be cherry-picked to RDO.