Clint Branham 6181c8ce77 fix: normalize -DiskSize and -RootFsSize before sending to PVE ...

Disk and rootfs size strings were interpolated directly into the disk
spec as "<storage>:<size>", so "60G" produced "local-lvm:60G". On
LVM/LVM-thin storages PVE parses the value after the colon as a volume
name unless it is a bare integer, returning "unable to parse lvm volume
name '60G'". File-backed storages mask this by accepting either form.

SizeParser.NormalizeToGibibytes() now strips G/GB/T/TB suffixes and
returns a bare GiB integer string, so the documented "32G" call shape
works on every storage type. Sub-GB units are rejected with a clear
error rather than being silently truncated.

Tracked as F086. Closes #58.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-20 17:59:21 -05:00

..

infrastructure

fix: always use shared mount for WORK_DIR, never RUNNER_TEMP

2026-03-25 17:22:00 -05:00

PSProxmoxVE.Core.Tests

fix: normalize -DiskSize and -RootFsSize before sending to PVE

2026-05-20 17:59:21 -05:00

PSProxmoxVE.Tests

fix: resolve issues #43, #44, #45

2026-03-27 10:22:37 -05:00

.env.test.example

fix: apply review feedback on Docker storage and security documentation

2026-03-24 18:53:30 +00:00

dev.ps1

fix: address Copilot review round 3

2026-03-25 16:27:14 -05:00

docker-compose.test.yml

fix: use shared host mount for answer files + rename to pve-integration

2026-03-25 14:49:59 -05:00

Dockerfile.test

fix: apply review feedback on Docker storage and security documentation

2026-03-24 18:53:30 +00:00