+++ 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.
*** Bug 1106509 has been marked as a duplicate of this bug. ***
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.
@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?
@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.
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
(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.