#7414 Wrong fedmsg signer for compose.29.start
Closed: Fixed 3 years ago Opened 3 years ago by abompard.

The fedmsg migration tools are picking up messages on topic org.fedoraproject.prod.compose.29.start signed by releng-compose-x86-01.phx2.fedoraproject.org. However, in our infra ansible, the invert_fedmsg_policy function is generating a list where this topic is supposed to be signed by either releng-branched-composer.phx2.fedoraproject.org or releng-compose-iot-01.phx2.fedoraproject.org.

As a result, those messages are considered invalid and dropped. This is either a misconfiguration of the sender or an error in the ansible-generated fedmsg policy.

The messages aren't archived in Datanommer either (for the same reason probably).


Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata