Puppet does not detect that RabbitMQ is up in time

[Dmitry Mescheryakov]

Version: 10.0

Steps to reproduce:
1. Deploy env consisting of 3 controllers and 3 computes

The deployment fails with message
AssertionError: Task 'deploy' has incorrect status. error != ready, 'Deployment has failed. All nodes are finished. Failed tasks: Task[primary-rabbitmq/3] Stopping the deployment process!'

In the puppet.log on the node-3 one can see that astute killed task while puppet was waiting for RabbitMQ master to come up: http://paste.openstack.org/show/561434/

At the same time on the reverted environment it could be clearly seen that RabbitMQ master is up, while Puppet is still trying to check that. After some time passes, puppet finally sees that RabbitMQ is up and successfully finishes (puppet timeout is 30 minutes, while astute's is 15 minutes, that is why puppet succeeds, while astute fails).

Attached is snapshot and 'cibadmin -Q' output before puppet detected that RabbitMQ master is up (cibadmin.before) and after that (cibadmin.after). That output is used by puppet to find out about RabbitMQ master.

Failed job: https://product-ci.infra.mirantis.net/view/10.0/job/10.0.main.ubuntu.bvt_2/563/console

[Maksim Malchuk (mmalchuk)]

related or even duplicate of the: https://bugs.launchpad.net/fuel/+bug/1606258

[Kyrylo Galanov (kgalanov)]

Is this issue still reproduced? It should be already fixed by multiple commits.

[Oleksiy Molchanov (omolchanov)]

Marking as Invalid, because of no update for more than a month.