Created attachment 875134 [details]
YaST logs

I've tuned the Storage proposal to contain two encrypted XFS file systems for
/var and /usr:

    - partition:
        size: 500 MiB
        start: 405466 MiB (395.96 GiB)
        name: "/dev/nvme0n1p8"
        type: primary
        id: linux
        file_system: xfs
        mount_point: "/var"
        encryption:
          type: luks
          name: "/dev/mapper/cr_var"
          password: "***"

    - partition:
        size: 500 MiB
        start: 405966 MiB (396.45 GiB)
        name: "/dev/nvme0n1p9"
        type: primary
        id: linux
        file_system: xfs
        mount_point: "/usr"
        encryption:
          type: luks
          name: "/dev/mapper/cr_usr"
          password: "***"

These partitions really have 500 MiB, but XFS takes the first 300 MiB just for
metadata/log (see bug #1220728) and before this, the encryption itself also
takes something. The result is that these partitions have just a tiny free
space for real data.

The information (and counting) about free space probably belongs to
Storage/libstorage-ng, but Software should use it and check if the list of
selected packages really fits. Or at least guess that and report back a warnig
(?) if the doesn't.