Original description from https://bugzilla.redhat.com/show_bug.cgi?id=2121491
Description of problem (please be detailed as possible and provide log
snippests):
Creating a PVC with e.g. 200MB size, results in a PV of 1GB created.
On a small edge device with limited storage (e.g. only 32GB sd card), this creates an issue leading to PVs not being created (despite enough space available technically). Thin provisioning does not really help, because just "by the book", the disk would be full.

Version of all relevant components (if applicable):
ODF-LVM V4.10.4

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, see above

Is there any workaround available to the best of your knowledge?
No.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
easy, just create a PVC with 200MB and see the PV size.

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
1. create a pvc with 200MB size (and bind it to a pod)
2. check size of PV - see 1GB
3.

Actual results:
1GB pv size

Expected results:
200MB pv size

Additional info:
LVM does support LV with MB sizes.
The issue seems to be the lvmd rest API, which requires Size in GB as INT, causing the size. See here where the rounding up happens:
https://github.com/topolvm/topolvm/blob/5df9e7cede433d41c9c77827b0f26dacfa8a2a59/controllers/logicalvolume_controller.go#L219