title: Why are Celery + RabbitMQ creating queues automatically when I've disabled that behavior explicitly?
body: <p>First things first: I have <code>CELERY_CREATE_MISSING_QUEUES = False</code> in my celeryconfig, and I launch a celery worker with <code>celery worker -Q queue1</code>. I can see by monitoring that <code>queue1</code> is created, and that the worker is listening on it. Now, when I launch a task that is routed (via <code>CELERY_ROUTES</code>) to <code>queue2</code>, I can see that <code>queue2</code> is created; can someone explain this behavior? Note: I think that what I'm asking is different from <a href="https://stackoverflow.com/questions/7144025/temporary-queue-made-in-celery">this question</a>, because I see, understand, and can control the lifetime of the temporary queues created to store the results. What I want to know is why auxiliary queues are being created.</p>