The check for the validity if partition sizing is only taking in mind the format limitations. https://github.com/rhinstaller/anaconda/blob/2882e818dc890b4242312b887c56b146fdde4d4f/pyanaconda/modules/storage/bootloader/base.py#L402

We need to check the sizes specified here https://github.com/rhinstaller/anaconda/blob/main/pyanaconda/modules/storage/platform.py#L228

This will resolve: https://bugzilla.redhat.com/show_bug.cgi?id=2351824

— UPDATE after task scoping:

After scoping the task (see the comments) I think the goal here is:

For all partitioning scenarios:

• Warn user about not enough space on relevant mount points / partitions (perhaps '/', '/usr') for the required system (payload) size. (This will naturally include original motivation of developers being able to discover easily that insufficient place was the reason of failed installation)
• Make it only non-fatal warning allowing to continue with the installation. Main reason is it is just an estimate with limited (and maybe varied per payload type) precision and we shouldn't prevent it in tight situations or when user knows what he is doing.

Also including the approach discussion I suggest setting the Story Points to 5 at least.

And we should change the name