Rabbitmq fails with error that user nova already exist on compute reinstallation

Bug #1569890 reported by Alexandr Kostrikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Dmitry Burmistrov
Mitaka
Fix Released
High
Dmitry Burmistrov
Newton
Fix Committed
High
Dmitry Burmistrov

Bug Description

Detailed description:

During swarm ran at CI[0] with scenario
        Scenario:
            1. Revert the snapshot
            2. Create an OS volume and OS instance
            3. Mark 'cinder' partition to be preserved
            4. Mark 'vm' partition to be preserved
            5. Reinstall the compute node
            6. Run network verification
            7. Run OSTF
            8. Verify that the volume is present and has 'available' status
               after the node reinstallation
            9. Verify that the VM is available and pingable
               after the node reinstallation

there were failure [1]:
2016-04-12 23:56:40 +0000 Puppet (err): Execution of '/usr/sbin/rabbitmqctl add_user nova h69rVcAgTJheTAWzPXaRzxFF' returned 70: Creating user "nova" ...
Error: user_already_exists: nova

Also, there were an error before that[2]:
2016-04-12 23:47:37 +0000 Puppet (notice): Compiled catalog for node-2.test.domain.local in environment production in 2.73 seconds
2016-04-12 23:51:15 +0000 /Stage[main]/Rabbitmq::Management/Rabbitmq_user[guest] (err): Could not evaluate: Command is still failing after 180 seconds expired!

[0] https://product-ci.infra.mirantis.net/job/9.0.system_test.ubuntu.partition_preservation/76/console
[1] http://paste.openstack.org/show/493931/
[2] http://paste.openstack.org/show/493933/

Revision history for this message
Alexandr Kostrikov (akostrikov-mirantis) wrote :
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

RabbitMQ users are created from nova module, moving to MOS Puppet

tags: added: life-cycle-management
tags: added: area-mos
removed: area-library
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → MOS Puppet Team (mos-puppet)
Changed in fuel:
assignee: MOS Puppet Team (mos-puppet) → Dmitry Burmistrov (dmburmistrov)
status: New → Confirmed
Revision history for this message
Mikhail Samoylov (msamoylov) wrote :
Revision history for this message
Dmitry Burmistrov (dmburmistrov) wrote :

The cause of this problem is fixed in puppet pacemaker module here - https://github.com/fuel-infra/puppet-pacemaker/commit/8780696d6f1367f1a3b3c0ef737a89167e61732e

So, fix is commited, in new tests problem shouldn't appear. Otherwise please reopen this bug.

Revision history for this message
Evgeny Sikachev (esikachev) wrote :

verified on 484 iso, mos 9.0

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.