timing window Rawhide tests and f32 release

[Normand]

Hello Adam,

seem there is a timing window problem between Rawhide tests and f32 
release as per failure https://openqa.fedoraproject.org/tests/587422
===
Cannot find HDD_1 asset hdd/disk_f32_support_5_x86_64.img!
===
failed Fedora-Rawhide-20200426.n.1	about an hour ago ( 0 )
failed Fedora-Rawhide-20200425.n.0	2 days ago ( 0 )
passed Fedora-Rawhide-20200423.n.0	4 days ago ( 02:00 minutes )
===

There is not yet a f32 in 
https://fr2.rpmfind.net/linux/fedora/linux/releases/
===
[DIR]	30/ 	2019-04-26 22:58 	- 	
[DIR]	31/ 	2019-10-25 17:05 	- 	
[DIR]	test/ 	2020-03-13 21:00 	- 	
===

I experienced similar problem trying createhdds for ppc64le

[Adam Williamson]

On Mon, 2020-04-27 at 11:19 +0200, Normand wrote:
> Hello Adam,
>
> seem there is a timing window problem between Rawhide tests and f32 
> release as per failure https://openqa.fedoraproject.org/tests/587422
> ===
> Cannot find HDD_1 asset hdd/disk_f32_support_5_x86_64.img!
> ===
> failed Fedora-Rawhide-20200426.n.1	about an hour ago ( 0 )
> failed Fedora-Rawhide-20200425.n.0	2 days ago ( 0 )
> passed Fedora-Rawhide-20200423.n.0	4 days ago ( 02:00 minutes )
> ===
>
> There is not yet a f32 in 
> https://fr2.rpmfind.net/linux/fedora/linux/releases/
> ===
> [DIR]	30/ 	2019-04-26 22:58 	- 	
> [DIR]	31/ 	2019-10-25 17:05 	- 	
> [DIR]	test/ 	2020-03-13 21:00 	- 	
> ===
>
> I experienced similar problem trying createhdds for ppc64le

It's because of
https://gitlab.gnome.org/GNOME/gnome-software/issues/214 , basically.
fedora_openqa and createhdds think F32 is 'stable' prematurely (because
Bodhi is telling them it is), so fedora_openqa is scheduling for it
that way and createhdds is using the stable release path when trying to
build F32 images, and that's failing because it's locked till release
time. The timing is sufficiently close that I'm just going to let it
ride, I think.