cloud-image-uploader: update container image config for IoT changes #2580
No reviewers
Labels
No labels
freeze-break-request
post-freeze
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/ansible#2580
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ciu-iot-renames"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We finally merged https://pagure.io/fedora-iot/pungi-iot/pull-request/102
which changes the properties of the container images built in the
IoT compose. This should adjust to that and publish both the base
and IoT images, if we got it all right.
Signed-off-by: Adam Williamson awilliam@redhat.com
Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/6de7dd7ee3d846e9b21f38715a24d30f
merging this now as the pungi-iot commit is already merged so we need to be in line with it. @pwhalen and I will keep an eye on the next compose and try to ensure it's all right.
Pull-Request has been merged by adamwill
Is this related to https://pagure.io/fedora-infrastructure/issue/12508 ? or is that a seperate thing?
um, I'm not entirely sure. if IoT is using bootc/image mode/whatever you want to call it by default now and what you get from
rpm-ostree upgrade
on IoT is based on pulling the images from quay.io / registry.fp.o , this may fix that, yeah. it should result in every IoT container image build getting synced to the registry, and the f42 ones should get the 'latest' tag.so, no, I don't think so. Per https://pagure.io/fedora-iot/pungi-iot/blob/main/f/fedora-iot.conf , IoT does still compose and publish old-school ostrees, and that's what the user in 12508 is using, I think. so this doesn't affect that. I think the situation in 12508 is simply that there actually was no F42 IoT compose between 20250414 and 20250422.
Yeah, the nightly container still builds f41 for iot... but I am not sure if it's supposed to switch or just fo 42 or what. ;( Will wait for @pwhalen to look.