To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
On Thu, 14 Mar 2019 at 09:55, Peter Robinson pbrobinson@gmail.com wrote:
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
This will need to be coordinated on the 2 ppc builders that do image builds because they require an older kernel/libvirt/someother stuff and when I was doing updates on them oz would not upgrade because it was built against the newer versions (I am not sure if it was directly or a dependency chain issue).
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
This will need to be coordinated on the 2 ppc builders that do image builds because they require an older kernel/libvirt/someother stuff and when I was doing updates on them oz would not upgrade because it was built against the newer versions (I am not sure if it was directly or a dependency chain issue).
We can exclude power64 if it's easier as there's no change there, it really only affect x86/aarch64 builders. What version of oz do they currently have?
P
On Thu, 14 Mar 2019 at 10:02, Peter Robinson pbrobinson@gmail.com wrote:
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
This will need to be coordinated on the 2 ppc builders that do image builds because they require an older kernel/libvirt/someother stuff and when I was doing updates on them oz would not upgrade because it was built against the newer versions (I am not sure if it was directly or a dependency chain issue).
We can exclude power64 if it's easier as there's no change there, it really only affect x86/aarch64 builders. What version of oz do they currently have?
I guess Kevin fixed the problem I was having with upgrading last week and it is currently oz-0.17.0-0.1.fc29.noarch with qemu-2.12.0-4.fc29.ppc64le
P _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On 3/14/19 9:58 AM, Stephen John Smoogen wrote:
On Thu, 14 Mar 2019 at 09:55, Peter Robinson pbrobinson@gmail.com wrote:
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
This will need to be coordinated on the 2 ppc builders that do image builds because they require an older kernel/libvirt/someother stuff and when I was doing updates on them oz would not upgrade because it was built against the newer versions (I am not sure if it was directly or a dependency chain issue).
For context here is the ticket that led to the downgrade: https://pagure.io/fedora-infrastructure/issue/7598
It has an associated bug I think: https://bugzilla.redhat.com/show_bug.cgi?id=1676475
Would love to have whatever issues there are there to be resolved so we don't need to do this in the future. I'll add a comment to the issue to see if we can get any more info.
Dusty
Given the minimal impact of the latest patch unless the config is updated to use the F30 config, +1 from me. Also, if it does in fact break stuff, it's easy enough to revert.
On 3/14/19 6:55 AM, Peter Robinson wrote:
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
+1. I assume there will be a pungi-fedora PR to switch from Fedora-22 to Fedora-30 for those things that want to use this? :)
kevin
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
+1. I assume there will be a pungi-fedora PR to switch from Fedora-22 to Fedora-30 for those things that want to use this? :)
Eventually yes, as it only affects x86 ATM it doesn't affect any of the standard Fedora deliverables so no actual need of change and we want it left as F-22. The IoT pungi config is currently elsewhere. In the case of ARMv7/aarch64 it works as for both those arches UEFI is the only way they've ever worked so they don't need change either.
Eventually I might get the enthusiasm and come cycles to make the cloud images more generic and able to run on UEFI platforms but ATM I don't have the cycles to begin to care about that so I'll leave that, at least for the time being, to those that might.
P
On Thu, Mar 14, 2019 at 1:55 PM Peter Robinson pbrobinson@gmail.com wrote:
To deal with the cloud image issue I was originally going to resolve it slightly differently, I've not dealt with it in oz. the current "Fedora version" that pungi specifies (F-22) now retains BIOS by default, to use UEFI you can specify F-30 and if edk2 is available it will use that by default.
So I'd like to upgrade the builders to oz-0.17.0-0.2.fc29
This is now complete, let me know if any issues are seen
infrastructure@lists.fedoraproject.org
-
Dusty Mabe -
Kevin Fenzi -
Patrick マルタインアンドレアス Uiterwijk -
Peter Robinson -
Stephen John Smoogen