So as one can see at the prints attached to the ticket this happens only in advanced, manual partition mode, neither in automatic or in select mount point modes.

@adamwill does this still violates the criterion "The installer must be able to create and install to any workable partition layout using any file system and/or container format combination offered in a default installer configuration."?

I think that depends on what we call a "default installer configuration", on my opinion the Advanced Storage Editor mode it's not default.

So.... I checked all the criteria and think this bug violates in fact another one, not the one pointed in the ticket but this: https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria#Custom_partitioning
"When using both the installer-native and the blivet-gui-based custom partitioning flow on the GTK-based installer, and the Cockpit-based "storage editor" flow on the webui-based installer, the installer must be able to: (...) Reject or disallow invalid disk and volume configurations without crashing."

So, after all:

FinalBlocker +1

This really seems to violate https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria#Custom_partitioning . In WebUI there's not even a hint that the configured /boot partition is too small (as oppposed to GTK, where there is a warning dialog).

FinalBlocker +1

OTOH, this doesn't appear to be a regression, so this might be a good candidate for marking as a Common issue and waiving it with the later blocker proposal exception, leaving it for F45.

I agree on it being a good candidate as a Common issue.

Yeah, I think the second criterion Geraldo cited is the strongest here, at which point it comes down to what we mean by an "invalid" configuration exactly. Is "too small" "invalid"?

This really seems to violate https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria#Custom_partitioning . In WebUI there's not even a hint that the configured /boot partition is too small (as oppposed to GTK, where there is a warning dialog).

FinalBlocker +1

OTOH, this doesn't appear to be a regression, so this might be a good candidate for marking as a Common issue and waiving it with the later blocker proposal exception, leaving it for F45.

Agree

FinalBlocker +1

Release F44 is no longer tracked by BlockerBugs, closing this ticket.