releng

#11324 create quay.io/fedora/fedora-{silverblue,kinoite} repositories
Closed: It's all good by walters. Opened by walters.

Closed: It's all good
Reopen Issue
  • Describe the issue

See https://pagure.io/releng/pull-request/11180 specifically https://pagure.io/releng/pull-request/11180#comment-184550

Basically someone with perms needs to log into quay.io/fedora and use the GUI or API to create these "repositories" (in quay terms) for these new base container images.

  • When do you need this? (YYYY/MM/DD)

Sometime in 2013 would be nice =)

  • When is this no longer needed or useful? (YYYY/MM/DD)

At some point our competitors will move past us, but it's hard to pinpoint an exact date...

  • If we cannot complete your request, what is the impact?

I guess we could keep doing things outside of Fedora infra, but that's not great

I have created 

https://quay.io/repository/fedora/fedora-silverblue
https://quay.io/repository/fedora/fedora-kinoite

I think the bot has access to fedora org, so it should be good to go.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Hi, the most recent run failed slightly past that now:
https://lists.fedoraproject.org/archives/list/releng-cron@lists.fedoraproject.org/thread/CHDJVD7D4NZFRECKNHGLBNETY5WMPORA/

Can someone please double check that the bot has access to the newly created repositories in the same way it can push to quay.io/fedora/fedora?

Metadata Update from @walters:
- Issue status updated to: Open (was: Closed)

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

I have added fedora-publisher bot write permissions to those 2 repos. So, fingers crossed and lets see what it looks like tomorrow?

So, perhaps we are missing some cleanup?

compose-rawhide01 tmp][PROD-IAD2]# du -sh /var/tmp/tmp.*ostree
15G     /var/tmp/tmp.2fDHTI4g63.sync-ostree
15G     /var/tmp/tmp.3k9dHcVCor.sync-ostree
4.3G    /var/tmp/tmp.jREyeMos68.sync-ostree
4.3G    /var/tmp/tmp.q4TKjJQpyA.sync-ostree
15G     /var/tmp/tmp.QydSXiIKJd.sync-ostree
4.0K    /var/tmp/tmp.SJyRHkbC1O.sync-ostree
15G     /var/tmp/tmp.xjBbi6DK4j.sync-ostree
15G     /var/tmp/tmp.ZkwpEUWSK4.sync-ostree

Otherwise I do see content there now, can you see if it looks ok?

Looks like we don't clean up the tempdir on failure. I think that's fixable.

  • skopeo copy docker://docker://quay.io/fedora/fedora-silverblue:39
    docker://quay.io/fedora/fedora-silverblue:rawhide
    time="2023-03-10T10:31:25Z" level=fatal msg="Invalid source name
    docker://docker://quay.io/fedora/fedora-silverblue:39: invalid reference format"

Ahhh....close! So close.

Two fixes in https://pagure.io/releng/pull-request/11331

Merged. Will see tomorrow. ;)

OK, latest rawhide run works.

I think the next step is to do this for branched, then we can close this ticket?

Well, I'll spit that to a new ticket.

Metadata Update from @walters:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

OK, I think based on current discussion we can mark this as closed. There's...a lot more to do, such as actually running tests on these images before we push them to the world (as we do for FCOS). But this is a useful start.

Great!

Sorry it's been a slog... let me know if I can help move it forward more.

We'll need the same thing for Fedora Sericea cc @jkonecny

Thanks for doing this!

Yes please. CC @alebastr

Metadata
None

medium-gain medium-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.