Current robosignatory code cannot sign base modules, because the base module is not active in PDC in the time of tagging. This is caused by following ordering of events when MBS is finishing the module build:
MBS is going to finish the base module build - it starts tagging all the module RPMs to final tag.
When everything is tagged, it sends fedmsg message that module is "done".
PDC-updater handles that message and marks module as active=True in PDC.
But current robosignatory code queries for active=True base module in the time of signing. There is no such module in PDC - it has active=False in PDC.
This PR solves that by not including "active" key in PDC query. Therefore we can sign base module in the time of tagging before it is marked as "done" in PDC.
Current robosignatory code cannot sign base modules, because the base module is not active in PDC in the time of tagging. This is caused by following ordering of events when MBS is finishing the module build:
But current robosignatory code queries for active=True base module in the time of signing. There is no such module in PDC - it has active=False in PDC.
This PR solves that by not including "active" key in PDC query. Therefore we can sign base module in the time of tagging before it is marked as "done" in PDC.