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

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #15532

RabbitMQ User Permissions

Added by Daneyon Hansen almost 3 years ago. Updated about 2 years ago.

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

0%

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

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 2 years 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