Bug 1106509

Summary: Instances will not boot after upgrade because of missing required config for neutron/nova notifications
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: openstack-neutronAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: chrisw, ihrachys, lars, nyechiel, yeylon
Target Milestone: ga   
Target Release: 5.0 (RHEL 6)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1093879 Environment:
Last Closed: 2014-06-09 17:37:58 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: 1093879    
Bug Blocks: 1093877    

Description Stephen Gordon 2014-06-09 14:02:24 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.

--- Additional comment from Alan Pevec on 2014-05-29 05:37:06 EDT ---

> 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 2 Nir Yechiel 2014-06-09 17:37:58 UTC

*** This bug has been marked as a duplicate of bug 1094506 ***