kubernetes/test/e2e_node/runner/remote
Odin Ugedal c04ead5fb1
Add error check for instance insert
Not all errors will happen in sync during Instances.Insert(...).Do(), so
it is important to verify the operation object to see why insert fails.
An example is when exceeding the resource quota.

Eg.
could not create instance test-cos-beta-80-12739-29-0: [&{Code:QUOTA_EXCEEDED Location: Message:Quota 'CPUS' exceeded.  Limit: 24.0 in region europe-west6. ForceSendFields:[] NullFields:[]}

This fixes the issue where tests will fail "silently" when instance
insert fails.
2020-01-09 09:49:38 +01:00
..
BUILD migrate callers to g/g/uuid 2019-11-04 23:15:29 -08:00
run_remote.go Add error check for instance insert 2020-01-09 09:49:38 +01:00