And this is a standard pro saas deployment, the autoscaler scale up was triggered by the remote execution attempt of a pipeline
FierceHamster54 that's super-strange, we tested that some time ago (possibly with different account setting?) and got no error (and the instance was launched) - do you have any additional information that might help us reproduce it?
I checked the 'CPU-only' option in the auto-scaler config but that's seemed logic at the time
As specified in the initial message, the instance type used is
Perhaps it has something to do with the instance type?
It sounds like you can create the instance with
onHostMaintenance can be set to TERMINATE but can't be changed once you start it, but in actuality it fails creating with this value set...
FierceHamster54 so it seems the GCP documentation is somewhat misleading... See https://cloud.google.com/compute/docs/instances/setting-vm-host-options#limitations
This is funny cause the auto-scaler on GPU instances is working fine, but as the backtrace suggests it seems to be linked to this instance family
AnxiousSeal95 Okay it seems to work with a compute optimized
Ohwow, okay Ill test it with another type
Nice, thank you for the reactivity ❤
Hi FierceHamster54 can you try another instance type? I just tried with n1 and it works. We are looking to see if it's instance type related
Hi FierceHamster54 , I'll check it out
FierceHamster54 we'll fix it so that this option will be turned off if you choose E2