Jaguirrev
Contributor
Contributor

Adding a NFS share using AWS Storage Gateway Break ESXi WebUI

Hello.

I'm Posting cause I search for all places and did'nt found any answer ( sorry for my english btw)

So I recently deploy a AWS storage gateway  on mi ESXi , all work good and create a NFS share on it ( reference info: Create an NFS file share - AWS Storage Gateway (amazon.com)), So I attached the NFS share to some VMs to check if the config is OK and it work fine , no issues, so I tried to attach to ESXi beside using NFS v4, all works ok, no issues, I can see al my ISO files that are on my share NFS: Captura de Pantalla 2022-06-12 a la(s) 20.52.36.png

 

but when I click on any icon (I.E Host icon to see all info), I get this message:

Captura de Pantalla 2022-06-12 a la(s) 20.55.17.pngCaptura de Pantalla 2022-06-12 a la(s) 20.55.53.png

 

Transcription:

Motivo: Possibly unhandled rejection: {}
Versión: 1.36.0
Compilación: 18403931
ESXi: 7.0.3
Explorador: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.63 Safari/537.36 Edg/102.0.1245.39

Pila de excepciones:

TypeError: Cannot mix BigInt and other types, use explicit conversions
    at https://10.10.252.245/ui/scripts/main.js:400:4172
    at Array.forEach (<anonymous>)
    at https://10.10.252.245/ui/scripts/main.js:400:4080
    at https://10.10.252.245/ui/scripts/main.js:328:25451
    at m.$digest (https://10.10.252.245/ui/scripts/main.js:328:31159)
    at https://10.10.252.245/ui/scripts/main.js:329:860
    at Yg.completeTask (https://10.10.252.245/ui/scripts/main.js:329:6949)
    at https://10.10.252.245/ui/scripts/main.js:327:12030

I can bypass this issue just hitting ESC, but  I cannot create a VM or change options cause I get this message, the only way to fis this is just deleting the NFS share and fixed,

I already tried restart the hypervisor and update, 

 

this is my version appliance

Captura de Pantalla 2022-06-12 a la(s) 21.04.49.png

 

Labels (1)
0 Kudos
2 Replies
GRotvik
Contributor
Contributor

I have this same issue. There is no AWS documentation regarding this issue. Is this an NFS issue or and AWS implementation issue?

0 Kudos
kgswift
Contributor
Contributor

we have the same problem, I suspect that it may be due to the huge size reported for AWS eg. in our case

 

[root@esx01:~] df
Filesystem               Bytes          Used           Available Use% Mounted on
NFS41      9223372036853727232 1284830130176 9223370752023597056   0% /vmfs/volumes/archive

 

I didn't see anything in AWS to make EFS smaller, is it possible?

0 Kudos