For running mass rebuilds and mass branching of modules, we used a mbs token. AFAIK it was manually created. IIRC, it was placed under my home dir in branched-composer.phx2.fp.o.
During the reinstall of the box, I lost the token, can you help with recovering it and probably we have to create the ansible task to put it in some better location for future use.
I am not sure what this token was... it might have been an OATH token?
Is there a ticket or the like where it was requested? Otherwise we may have to ask @puiterwijk how to make a new one...
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Here's the first ticket that I requested and it is an OAUTH token.
https://pagure.io/fedora-infrastructure/issue/7532
Metadata Update from @mizdebsk: - Issue assigned to mizdebsk
I've put what I believe the token is in /home/fedora/mohanboddu/mbs-oidc-token on branched-composer.phx2.fedoraproject.org. This is OIDC token for @releng user and it has proper scopes required to submit module builds. Please test and if it works I will put it in private variables.
/home/fedora/mohanboddu/mbs-oidc-token
branched-composer.phx2.fedoraproject.org
Metadata Update from @mizdebsk: - Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)
@mizdebsk do let us know where you found it, so we can know where to issue/get them... feel free to reply out of ticket on that. :)
I found the token in ipsilon database on db-fas01 host.
ipsilon
db-fas01
ssh db-fas01.phx2.fedoraproject.org sudo -u postgres psql ipsilon SELECT * FROM token WHERE uuid IN (SELECT uuid FROM token WHERE name='username' AND value='releng');
I believe that the token should be equal to concatenation of value of userinfocode field, an underscore and value of security_check field.
userinfocode
security_check
Ah ha. Great. Thanks.
This should be all done.
:tokyo_tower:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.