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
The tool seems to be failing over one of storage medium, looking at your cluster the culprit seems to be our S3FS disk that automatically gets mounted to each node and provides templates which the customer can use to easily deploy VM's.
This S3FS disk reports itself as 16 EiB (16 Exbibytes) which the tools seem to crash upon. Seen that more S3 mounts can report such huges size like these, the problems seems to exist in the tool itself.
Expected behavior
Accept large storage.
Relevant log output
Unhandled exception: Newtonsoft.Json.JsonSerializationException: Error converting value 18446744073692774400 to type'System.Int64'. Path '[8].maxdisk', line 1, position 1808. ---> System.InvalidOperationException: Can not convert from BigInteger to System.Int64. ---> System.OverflowException: Value was either too large or too small for an Int64. at System.Numerics.BigInteger.op_Explicit(BigInteger value) at Newtonsoft.Json.Utilities.ConvertUtils.FromBigInteger(BigInteger i, Type targetType) --- End of inner exception stack trace --- at Newtonsoft.Json.Utilities.ConvertUtils.FromBigInteger(BigInteger i, Type targetType) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.EnsureType(JsonReader reader, Object value, CultureInfo culture, JsonContract contract, Type targetType) --- End of inner exception stack trace ---
Proxmox VE Version
8.2.7
Version (bug)
Latest
Version (working)
Latest
On what operating system are you experiencing the issue?
Linux
Pull Request
I would like to do a Pull Request
The text was updated successfully, but these errors were encountered:
What happened?
The tool seems to be failing over one of storage medium, looking at your cluster the culprit seems to be our S3FS disk that automatically gets mounted to each node and provides templates which the customer can use to easily deploy VM's.
This S3FS disk reports itself as 16 EiB (16 Exbibytes) which the tools seem to crash upon. Seen that more S3 mounts can report such huges size like these, the problems seems to exist in the tool itself.
Expected behavior
Accept large storage.
Relevant log output
Proxmox VE Version
8.2.7
Version (bug)
Latest
Version (working)
Latest
On what operating system are you experiencing the issue?
Linux
Pull Request
The text was updated successfully, but these errors were encountered: