Open vkurup opened 8 years ago
Just FYI, the workaround for this issue is to delete the rabbitmq project user and redeploy:
vkurup@localhost:~$ dpkg -l | grep rabbit
ii rabbitmq-server 3.6.0-1 all Multi-protocol messaging broker
vkurup@localhost:~$ sudo rabbitmqctl list_users
Listing users ...
epicallieshq_staging []
vkurup@localhost:~$ sudo rabbitmqctl delete_user epicallieshq_staging
Deleting user "epicallieshq_staging" ...
vkurup@localhost:~$ logout
Connection to staging.epicallies.com closed.
vkurup@caktus014:~/dev/ea $ fab staging deploy
182 seems to have been fixed at some point, but now I'm seeing a similar, though silent problem. During the RabbitMQ upgrade from 3.5 -> 3.6.0, multiple people noted that they had to delete and then recreate the RabbitMQ user, which means that our RabbitMQ state which is supposed to force the user to have the new specified password is working. It also doesn't seem to throw an error
After doing that, I restarted the celery processes and continued to see connection errors in the celery logs, with this in the RabbitMQ log:
This suggests to me that the salt state is not successfully changing the password, but it's also not throwing an error.