Describe the issue createKiwiImage tasks still use F-40 GA buildroot in koji for producing "F-40 updates", which mean only kiwi-10.0.11-5.fc40 is contained and not the fixed kiwi-10.0.21-1.fc40, resulting in production of broken cloud images for ppc64le and s390x. See https://koji.fedoraproject.org/koji/taginfo?tagID=85427 and https://koji.fedoraproject.org/koji/taskinfo?taskID=119499260 for more details.
createKiwiImage
kiwi-10.0.11-5.fc40
kiwi-10.0.21-1.fc40
When do you need this? (YYYY/MM/DD) ASAP
When is this no longer needed or useful? (YYYY/MM/DD) when F-40 goes EOL
If we cannot complete your request, what is the impact? broken ppc64le and s390x cloud images even when the fixed kiwi tool exists
So, befire release we need this to use fN-compose (because we put overrided packages there).
After release we need it to use fN-build so it gets updates. ;(
I am not sure how to do both off hand.
I suppose we could just change it's inhertience at release? That would be a bit of a pain though...
Because we are releasing updated kiwi thru the lifetime of a release, then I believe we should change the inheritance at release, so the updates can be used to produce the new images.
Another option is use the fX-compose tag and only add select updates there ...
fX-compose
How are "non-kiwi" images produced today? Do they use the GA repo or a "updates" for running imagefactory?
They use updates, but kiwi has to have a completely sepeate build target because it needs a different tag that has new_chroot = 0 set on it. (ie, kiwi requires the old mock chroot). If we could remove this limitation it could use use the fN and fN-build targets like all the other images/containers.
thanks, now I see what makes kiwi special
In the mean time, while I ponder on a longer term solution, I just tagged that kiwi package into f40-compose... so tonight's composes should have it.
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
Log in to comment on this ticket.