Anas Khan 7ee65e13be core: parse subvolumegroup bytes_quota reported as "infinite" ...

Ceph reports bytes_quota in `ceph fs subvolumegroup info` as the JSON
string "infinite" when no quota is set, and as a number otherwise. The
subvolumeGroupInfo.BytesQuota field is typed int64, so json.Unmarshal
fails with "cannot unmarshal string into Go value of type int64" for any
subvolume group without a quota (the default).

That unmarshal error is returned from getCephFSSubVolumeGroupInfo and
swallowed in CreateCephFSSubVolumeGroup: exec.ExitStatus reports ok=false
for the wrapped error, so the non-ENOENT guard does not fire and the
dedicated resize path (which enforces --no-shrink) is skipped.

Add an UnmarshalJSON on subvolumeGroupInfo that accepts either a number
or the "infinite" sentinel, mapping "infinite" to 0 (unlimited) so the
existing CmpInt64 comparison keeps working. Add a table-driven test
covering the finite and infinite cases.

Signed-off-by: Anas Khan <83116240+anxkhn@users.noreply.github.com>

2026-07-15 11:34:57 +05:30

..

ceph

core: parse subvolumegroup bytes_quota reported as "infinite"

2026-07-15 11:34:57 +05:30

discover

operator: add missing udev env to discover pod

2025-07-08 17:13:01 +05:30

multus

multus: remove unused validation test config constructor

2026-06-11 15:40:10 -07:00

util

build(deps): bump the k8s-dependencies group with 6 updates

2026-01-07 07:59:21 -07:00