Bug 1106509 - Instances will not boot after upgrade because of missing required config for neutron/nova notifications
Summary: Instances will not boot after upgrade because of missing required config for ...
Keywords:
Status: CLOSED DUPLICATE of bug 1094506
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 5.0 (RHEL 7)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 5.0 (RHEL 6)
Assignee: RHOS Maint
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On: 1093879
Blocks: 1093877
TreeView+ depends on / blocked
 
Reported: 2014-06-09 14:02 UTC by Stephen Gordon
Modified: 2016-04-26 17:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1093879
Environment:
Last Closed: 2014-06-09 17:37:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.