A recent blivet fix for LVM VG size calculation (see RHEL-74076) uncovered a bug in the storage role breaking the grow_to_fill feature.

Steps to reproduce:
1. Create a VG on a PV with size smaller than the size of the underlying block device:

1. pvcreate /dev/vdb
2. pvresize --setphysicalvolumesize 10g /dev/vdb
3. vgcreate myvg /dev/vdb

2. Try to grow the PV using the grow_to_fill feature
roles:

• name: linux-system-roles.storage
  storage_pools:
• name: myvg
  disks: ["vdb"]
  type: lvm
  grow_to_fill: true

3. Run the playbook and check the PV size after.

Result:
The PV is not resized

1. pvs
   PV VG Fmt Attr PSize PFree
   /dev/vdb myvg lvm2 a-- <10,00g <10,00g

Expected result:
The PV is resized to its max size (size of the underlying block device):

1. pvs
   PV VG Fmt Attr PSize PFree
   /dev/vdb myvg lvm2 a-- <20,00g <20,00g