The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #15532

RabbitMQ User Permissions

Added by Daneyon Hansen about 2 years ago. Updated about 1 year ago.

Status:ClosedStart date:07/16/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:module dependenciesSpent time:-
Target version:-
Keywords: Branch:

We've Moved!

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.


Description

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[1364]: (/Stage[main]/Nova/Exec[nova-db-sync]/returns) executed successfully Jul 13 13:25:52 control01 puppet-agent[1364]: Finished catalog run in 10.10 seconds Jul 13 13:56:01 control01 puppet-agent[1364]: (/Stage[main]/Nova::Rabbitmq/Rabbitmq_user_permissions[openstack_rabbit_use r@/]/ensure) create

History

#1 Updated by Anonymous about 1 year ago

  • Status changed from Unreviewed to Closed
  • Assignee changed from Dan Bode to Anonymous

OpenStack development and tracking has moved to review.openstack.org. If this issue persists, please submit a new report there.

Also available in: Atom PDF