neutron::server::notifications settings are actually required

Bug #1344271 reported by Andrew Woodward
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-neutron
Won't Fix
Undecided
Unassigned

Bug Description

both notify_nova_on_port_status_changes and notify_nova_on_port_data_changes default to True in icehouse, however unless you call neutron::server::notifications, you wont have the required credentials set. This results in odd errors when attempting to sent port notifications and can result in instances failing to start.

Revision history for this message
Emilien Macchi (emilienm) wrote :

can you explain a bit more? Is it because we don't make sure some parameters are here?

Changed in puppet-neutron:
status: New → Incomplete
Revision history for this message
Matt Fischer (mfisch) wrote :

closing without update from submitter.

Changed in puppet-neutron:
status: Incomplete → Opinion
status: Opinion → Invalid
Revision history for this message
Alex Schultz (alex-schultz) wrote :

I think it's still valid because Andrew is saying that the default values for those settings are now true, but unless you know to include neutron::server::notifications we are not properly providing nova credentials for those settings to work. Might just be a documentation thing where a user should either set them to false or include the notification class.

Changed in puppet-neutron:
status: Invalid → Confirmed
Revision history for this message
Tobias Urdin (tobias-urdin) wrote :

Setting as wont fix, a long time ago, neutron::server::notifications will set those to true (by default unless changed) but the neutron.conf default is also true so unless an super old setup had false hardcoded in the config this shouldn't be an issue.

Changed in puppet-neutron:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.