I used to be able to run osbuild-image tasks in staging Koji and create and tag builds for the Fedora-Cloud package (just a random one, there's no reason why we used just this one).
That no longer works, calling stg-koji osbuild-image ... gives me:
stg-koji osbuild-image ...
2022-09-21 19:26:36,537 [ERROR] koji: ActionNotAllowed: image permission required (logged in as obudai)
Can you add me the permissions back? Is it possible that these get wiped by db resync from prod? If that's the case, can we prevent that somehow?
Ftr, I need to be able to run osbuild-image quite rarely because I'm responsible for the Image Builder integration with Koji.
Make obudai able to run osbuild-image in staging koji.
The sooner, the better, this blocks us from getting Image Builder and Fedora IoT integrated, so ideally tomorrow - 2022/09/22
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Done.
I think this will fix our sync moving forward: https://pagure.io/fedora-infra/ansible/c/cd851b93508b9da28126ee6fd303c1799d9dd563?branch=main
Can you test and confirm?
I'm still getting
2022-09-21 20:15:06,306 [ERROR] koji: ActionNotAllowed: image permission required (logged in as obudai)
I even tried refreshing my kerberos TGT and it didn't help.
I have granted you image perm too.
I didn't set this up orig, so I am not sure what permissions you need. Do you have a list? Or is image and cg osbuild enough?
Yeah, that's what was needed, thanks!
Now I'm getting a different error though:
2022-09-21 20:23:04,285 [ERROR] koji: Fault: <Fault 1: '<class \'psycopg2.errors.UniqueViolation\'>: duplicate key value violates unique constraint "task_pkey"\nDETAIL: Key (id)=(90000007) already exists.\n'>
I guess you need to adjust the next auto-increment value?
Adjusted. Can you try again now?
It works, thanks a lot! :) Sadly, I have hit yet another issue 'caused by our side, that needs updating/sync plugin versions in both stage and prod koji: https://pagure.io/fedora-infrastructure/issue/10909
Cool. Thanks for testing.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.