releng

#10712 container image registry.fedoraproject.org/fedora:latest still points to f34
Closed: Fixed by cverna. Opened by lsm5.

Closed: Fixed
Reopen Issue
  • Describe the issue

The current fedora:latest container image still points to f34 (f35 is the latest at the time of this filing).

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

asap I guess (if it's gonna take a lot longer then might be worth switching straight to f36.

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

whenever f36 releases, where we'll need to switch again.

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

People will continue pulling fedora N-1

This seems to be fixed now https://bugzilla.redhat.com/show_bug.cgi?id=2065870#c2

But @cverna how did you fix it?

Metadata Update from @mohanboddu:
- Issue tagged with: low-gain, low-trouble, ops

That's my bad, I did an update on Friday and the repo I used to run the sync script was not rebased to the latest man branch.
I have rerun the sync script and that should be fixed.

Please re-open if that's not the case

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

That's my bad, I did an update on Friday and the repo I used to run the sync script was not rebased to the latest man branch.
I have rerun the sync script and that should be fixed.

Please re-open if that's not the case

So, if I understand it correctly, you ran this sync script on Friday but it wasn't rebased to the latest main branch and accidentally you pushed f34 image as the latest image? And then today you rebased your script and ran again to fix f35 as the latest image?
Metadata
None

low-gain low-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.