The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
RabbitMQ User Permissions
|Assignee:||Chris Hoge||% Done:|
|Category:||module dependencies||Spent time:||-|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
RabbitMQ loads the correct user permissions the first time a Node is built. On the next puppet run, it doesn’t load the current set of permissions again, but rather recycles the old list of them, and determines (wrongfully) that it needs to add a new permission and does so. Here is syslog snippet:
Jul 13 13:25:49 control01 puppet-agent: (/Stage[main]/Nova/Exec[nova-db-sync]/returns) executed successfully Jul 13 13:25:52 control01 puppet-agent: Finished catalog run in 10.10 seconds Jul 13 13:56:01 control01 puppet-agent: (/Stage[main]/Nova::Rabbitmq/Rabbitmq_user_permissions[openstack_rabbit_use r@/]/ensure) create