Bug 1297859

Summary: Rabbitmq users other that default are lost when disable/enable rabbitmq-cluster pacemaker resource
Product: Red Hat OpenStack Reporter: Alfredo Moralejo <amoralej>
Component: rabbitmq-serverAssignee: Peter Lemenkov <plemenko>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: apevec, jeckersb, jparrill, lhh, michele, srevivo, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 8.0 (Liberty)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-11 09:03:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alfredo Moralejo 2016-01-12 16:23:41 UTC 
Description of problem:

When creating different users in rabbitmq as shown in https://access.redhat.com/articles/1167113 kbase in standard HA configuration, users are lost after disable/enable users.

Version-Release number of selected component (if applicable):

RHEL OSP7 

How reproducible:

Allways

Steps to Reproduce:
1. Create a rabbitmq cluster using rabbitmq-cluster pacemaker resource 
2. Create different users, different that default guest:

# rabbitmqctl add_user cinder CINDER_PASS
# rabbitmqctl add_user nova NOVA_PASS
# rabbitmqctl add_user neutron NEUTRON_PASS
# rabbitmqctl add_user heat HEAT_PASS
# rabbitmqctl add_user glance GLANCE_PASS
# rabbitmqctl add_user ceilometer CEILOMETER_PASS

3. Disable and enable resouce

pcs resource disable rabbitmq-cluster
pcs resource enable rabbitmq-cluster



Actual results:

Users just created are lost.

Expected results:

Users should be kept on pacemaker resources stop/start

Additional info:

rabbitmq-cluster has a wipe function to cleanup all the data dir when bootstraping a cluster. It seems that users are only persisted there and can not be created in rabbitmq.config.
Comment 2 Peter Lemenkov 2016-04-11 09:03:50 UTC 

*** This bug has been marked as a duplicate of bug 1303803 ***