Please create a repo under fedora namespace on quay.io named like fedora/kickstart-artifacts and share the access to it so new assets can be pushed to via a delivery pipeline that resides here as of today with the plan to move to konflux https://gitlab.com/fedora/bootc/artifacts/kickstart-artifacts
fedora/kickstart-artifacts
As soon as folks can get to it. The proposal https://discussion.fedoraproject.org/t/f42-change-proposal-distributing-kickstart-files-as-oci-artifacts-self-contained/131150 got accepted, pushing the assets to the registry would be the last outstanding item.
Previous pagure ticket https://pagure.io/fedora-infrastructure/issue/12152
cc @kevin @adamwill @lzap
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
I have created the repo... who should have access to push to it?
Metadata Update from @kevin: - Issue assigned to kevin
That would be me @lzap and @ipanova. Please confirm, Ina. Thank you!
Yes, please!
ok. I think I have added you for write access.
However, ideally we should get something in place to push this as part of the release, not manually pushed by folks.
I guess we could discuss that in a release engineering meeting/ticket/context?
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Created meeting ticket
https://pagure.io/releng/issue/12454
tho I am unable to assign "meeting" label, permissions issue?
Could be. We added the label. ;) Thanks!
Summary of RELENG meeting from 2024-11-18
We will start pushing (unsigned) artifacts into "rawhide" tag on a weekly basis. Then we want to create a stable branch for F41 and do the same. Once we are done, we will come back to you guys with further steps.
We will use the following public gitlab.com repo with a simple CICD pipeline:
https://gitlab.com/fedora/bootc/artifacts/kickstart-artifacts/-/tree/main?ref_type=heads
Hello, we are unable to push to the repo from gitlab we need a token generated. Can you share it with us?
https://quay.io/repository/fedora/kickstart-artifacts?tab=info
Here is my GPG key: https://lukas.zapletalovi.com/LUKAS-ZAPLETAL-GPG-KEY-2012
Thanks
Metadata Update from @kevin: - Issue status updated to: Open (was: Closed)
ok, but to do that we need to make a robot account right? I don't think I can make a token for your accounts.
How about a 'fedora+kickstart-artifacts' robot with write perms ?
@kevin yes, robot account with write perms would be fine :thumbsup: Thank you.
So, quay doesn't allow - in names, so I just did 'fedora+kickstartartifacts'
So, I made a fedora_kickstart_artifiacts_publisher account.
I sent gpg encrypted file to lzap.
Please let us know if you need anything further.
Hello,
for some reason it does not work:
+ buildah manifest push --all --rm quay.io/fedora/kickstart-artifacts:39 Getting image list signatures Copying 2 images generated from 2 images in list Copying image sha256:b25f3d035f9f8fa39f331e2bb65f03ce44717c5f210088d871c1d33e1d6851c8 (1/2) Getting image source signatures Copying blob sha256:66f17788811d978badc598b106b7f791f4ebaf530ef25918e2e40277810a6b66 Copying blob sha256:ce7e6c0ff58ca4729983f04b88e70b01e77b5eccdd5de6ad6ddd8a099ae2541c Copying blob sha256:31595ea8d8b400855031b224097a1cac4b2af79824aba3d32171adcd2bf4345a Copying blob sha256:c50881f9170b53f88d3c142473d332aaf20606ce9cdb4a68be36ec1bdf7a16cf Copying blob sha256:3efb9f54443d099237215b134c9c02c2c7e27ea286815b3d378827e91e4c4f36 Copying blob sha256:4773d74d87c2371a25883b59a3b6d98d157de46933676706d215015b1130f2d1 Copying blob sha256:5f2ef0de47f8d79d5ee9bf8b0ee6d5ba4d987c2f9a16b8b511a7c69e53931fe3 Error: copying image 1/2 from manifest list: writing blob: initiating layer upload to /v2/fedora/kickstart-artifacts/blobs/uploads/ in quay.io: unauthorized: access to the requested resource is not authorized
Does the account have push permissions?
perms adjusted, solved.
All works fine, thank you.
To create similar repository for CentOS Stream, where do I ask? Thanks.
@lzap I assume opening issue on CS project in JIRA is a good start.
Log in to comment on this ticket.