Apologies for the short notice.
= phenomenon = Fedora Cloud images are (again) not bootable, well into Fedora 25 Alpha Freeze.
= reason =
Looking at the official test results in https://apps.fedoraproject.org/autocloud/jobs/?family=b&arch=x86_64&image_type=qcow2&status=f , it would appear that the failures have been going on since at least June and that either no one has been checking the results or else they have not been actively trying to fix the situation.
= recommendation =
Before tomorrow's Go/No-Go decision, FESCo should have a roll-call vote (in this ticket is fine) to decide whether we should continue to treat cloud images as blocking deliverables for Fedora 25.
= Additional Information = The Cloud WG is moving away from its classic role and more towards delivering [https://fedoraproject.org/wiki/Objectives/ProjectFAO Project FAO]. With that in mind, I expect that the Fedora Server will pick up and replace the traditional cloud image with a Fedora Server-based image in F26 and onwards.
Forgot additional relevant information: https://bugzilla.redhat.com/show_bug.cgi?id=1369794
Replying to [ticket:1618 sgallagh]:
= recommendation = Before tomorrow's Go/No-Go decision, FESCo should have a roll-call vote (in this ticket is fine) to decide whether we should continue to treat cloud images as blocking deliverables for Fedora 25.
I'd vote non-blocking for Alpha, but I'm not ready to make the declaration for the entire release. I'd really like to give the Cloud WG a final chance to get things in shape and make the full release determination at Beta.
In any case, the Cloud WG needs to be accountable for their images. If we ship any milestone without cloud images working, they need to have something drafted as to why, how they're going to address it, and when.
I agree we need to have folks looking after and accountable for this image if it's going to be release blocking.
I think we have worked around all the issues for Alpha hopefully, so I'm fine leaving it blocking until we sort out who is responsible for it in f26+
I think considering already a week slip, don't make cloud images blocking for Alpha release and have this issue fixed soon post Alpha release. But keep it blocking for F25 Final release.
Its surprising to see images were failing from some time and they have not got it fixed before Alpha freeze.
We have this page https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fedora25 which says Fedora Cloud base image is release blocking but its not yet signed off by Cloud WG. I have filed new ticket #1626 to get all respective WG to sign off their release deliverables.
sgallagh, Can this ticket be closed?
Login to comment on this ticket.