Authorization/routing_policy error. Topic u'org.fedoraproject.prod.compose.29.complete'. Signer u'releng-branched-composer.phx2.fedoraproject.org'.
Does this mean that releng-branched-composer.phx2.fedoraproject.org is sending a message on a topic that bodhi-backend02 doesn't believe it is allowed to do? If so, I suppose we should tell Bodhi that that topic is OK for that host.
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If that problem goes away.
If we cannot complete your request, what is the impact?
I'll keep getting noisy e-mail errors.
Fixed in ansible commit 99fc4985c9bce5e7deffa1d66c575104df598089
syncing it out to all the machines now...
Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata Update from @bowlofeggs:
- Issue status updated to: Open (was: Closed)
This has been happening again recently. Here's an example e-mail I got on bodhi-backend02 today:
Authorization/routing_policy error. Topic 'org.fedoraproject.prod.compose.29.start'. Signer 'releng-compose-x86-01.phx2.fedoraproject.org'.
to comment on this ticket.