You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could it be that the check of the disc size with the fact size_available is not correct? In my view, the size_available value is returned in bytes instead of kilobytes.
If I define the following variables, I don't get an error even though the free space is too small:
- name: /
gigabytes_available: 50
When I query the disc size on the host, I get the following values:
thomas@docker101-lxc:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/pve-vm--101--disk--0 20466256 2234004 17167292 12% /
thomas@docker101-lxc:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-vm--101--disk--0 20G 2.2G 17G 12% /
thomas@docker101-lxc:~$ df -B1
Filesystem 1B-blocks Used Available Use% Mounted on
/dev/mapper/pve-vm--101--disk--0 20957446144 2287628288 17579298816 12% /
Describe the bug
Could it be that the check of the disc size with the fact size_available is not correct? In my view, the size_available value is returned in bytes instead of kilobytes.
If I define the following variables, I don't get an error even though the free space is too small:
When I query the disc size on the host, I get the following values:
Playbook
I use the following playbook:
Output
I receive this issue as verbose:
Workaround
If I adjust the file mount.yml (lines 20-22) as follows, the check works:
Output:
Environment
Please consider sponsoring me.
The text was updated successfully, but these errors were encountered: