openstack/puppet-tripleo
Code Issues Proposed changes

Do not force provider in rabbitmq base profile

Browse Source 
We cannot force the provider when defining the rabbitmq_user on
stack update operation, because otherwise the noop_resource [1]
function cannot override the resource behaviour and the config
generation fails with unexpected calls to /usr/bin/rabbitmqctl.

We don't need to force the provider, so stop doing so.

[1] tripleo/lib/puppet/parser/functions/noop_resource.pp

Change-Id: If718dd50147b3430f9f72fa59c297ae65440f71a
Closes-Bug: #1739771
This commit is contained in:
Damien Ciabrini
2017-12-22 13:47:26 +01:00
parent 8f86587d06
commit a9f059f540
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
manifests/profile/base/rabbitmq.pp
View File

@@ -163,7 +163,6 @@ class tripleo::profile::base::rabbitmq (
# called explicity, if the rabbitmq service is already running. # called explicity, if the rabbitmq service is already running.
rabbitmq_user { $rabbitmq_user : rabbitmq_user { $rabbitmq_user :
password => $rabbitmq_pass, password => $rabbitmq_pass,
provider => 'rabbitmqctl',
admin => true, admin => true,
} }
} }