2018-09-05 00:49:31 [ERROR ] Compose run failed: [Errno 2] No such file or directory: '/mnt/koji/vol/prod/packages/openblas/0.3.2/2.fc28/data/signed/9db62fb1/aarch64/openblas-Rblas-0.3.2-2.fc28.aarch64.rpm'
Could/should we sync production koji to staging koji to get me going again? If there's an alternative solution that will get a Bodhi compose to work in staging, that's my true goal.
When do you need this? (YYYY/MM/DD)
As soon as convenient.
When is this no longer needed or useful? (YYYY/MM/DD)
If we stop using Koji, Bodhi, Pungi, or the heat death of the universe happens.
If we cannot complete your request, what is the impact?
I am unable to continue testing fixes for a bodhi 3.10 blocker bug.
Metadata Update from @bowlofeggs:
- Issue tagged with: bodhi, koji, staging
This RPM is not signed in production either, so Koji sync won't help.
[mizdebsk@compose-x86-01 ~][PROD]$ koji -p compose_koji --noauth list-signed --debug --rpm openblas-Rblas-0.3.2-2.fc28.aarch64
No copy: /mnt/koji/packages/openblas/0.3.2/2.fc28/data/signed//aarch64/openblas-Rblas-0.3.2-2.fc28.aarch64.rpm
No copy: /mnt/koji/packages/openblas/0.3.2/2.fc28/data/signed/9db62fb1/aarch64/openblas-Rblas-0.3.2-2.fc28.aarch64.rpm
@mohanboddu Are you able to sign the RPM referenced above?
The package actually still has a sigcache, just the signed rpms were garbage collected.
I have written them out again:
koji write-signed-rpm 9db62fb1 openblas-0.3.2-2.fc28
Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
to comment on this ticket.