Per pbrobinson, we have a problem caused by incomplete landing of this FE in F29 Beta RC1:
it seems that for RC1, the update was included, but the associated change to fedora-kickstarts was not. According to Peter, a consequence of this is that the ARM images will not boot at all on Raspberry Pi systems.
As the Pi is a supported platform per https://fedoraproject.org/wiki/Architectures/ARM/Supported_Platforms , that makes this a clear blocker under criterion "All release-blocking images must boot in their supported configurations" - https://fedoraproject.org/wiki/Basic_Release_Criteria#Release-blocking_images_must_boot . Note footnote "Supported ARM platforms are those listed by the ARM team at Architectures/ARM/Supported_Platforms."
The PR has since been merged, so all we need to do if this is accepted as a blocker is run an RC2 compose (with any other blocker/FE fixes required).
The above is correct. +1 to blocker
I guess its only arm 32 images on RPi, which is still a blocker.
I mean, +1 to blocker. This is important.
+1 to blocker
That's + several, setting accepted.
Setting MODIFIED to indicate the PR has been merged and the next successful compose should be fixed.
(In reply to Adam Williamson from comment #8)
> Setting MODIFIED to indicate the PR has been merged and the next successful
> compose should be fixed.
For the records, beta RC2 works.
RC2 compose ultimately failed - can you confirm with RC3?
then we can close this. Thanks!
RC3 boots just fine on RPI2.
(In reply to František Zatloukal from comment #11)
> RC3 boots just fine on RPI2.
It boots fine also on RPi3 as well.