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
When creating a new VM fails (in this case due to an invalid memory specification), the error isn't properly handled and samutev attempts to continue:
$ samutev.sh -s 'master:c1:m0.5:d3 minion:c1:m0.5:d3'
launching master (master with cpu=1 mem=0.5G disk=3G and image 'focal')
launch failed: Invalid arguments supplied
Invalid memory size value supplied: 0.5G.
exec failed: instance "master" does not exist
exec failed: instance "master" does not exist
mount failed: The following errors occurred:
instance "master" does not exist
mount failed: The following errors occurred:
instance "master" does not exist
exec failed: instance "master" does not exist
mount failed: The following errors occurred:
instance "master" does not exist
exec failed: instance "master" does not exist
mount failed: The following errors occurred:
instance "master" does not exist
exec failed: instance "master" does not exist
info failed: The following errors occurred:
instance "master" does not exist
launched master in 0 minutes and 0 seconds.
info failed: The following errors occurred:
instance "master" does not exist
launching minion (minion with cpu=1 mem=0.5G disk=3G and image 'focal')
launch failed: Invalid arguments supplied
Invalid memory size value supplied: 0.5G.
info failed: The following errors occurred:
instance "minion" does not exist
launched minion in 0 minutes and 0 seconds.
ssh: Could not resolve hostname : Name or service not known
alltogether: 00:00 min.
READY to go:
ssh root@
salt '*' test.ping
This is most likely due to multipass being launched unconditionally in line 271:
When creating a new VM fails (in this case due to an invalid memory specification), the error isn't properly handled and samutev attempts to continue:
This is most likely due to
multipass
being launched unconditionally in line 271:This could be prevented by chaining the abort handling to it using
&&
.The text was updated successfully, but these errors were encountered: