When failing to create machines (on digitalocean) the UX is confusing

Summary

When docker machine cannot spawn droplets (on digitalocean) the reason for this is hard to discover. I assume other providers might have similar issues

Steps to reproduce

• Configure gitlab runner to scale droplets based on docker-machine
• Configure it so that it tries to start in ams2 with a size of 2gb (at the time of this writing, your mileage might vary)
• Trigger a build in gitlab

Actual behaviour

• See that it times out without any good logging in the gitlab UX, I also couldn't find proper logs on the runner / gitlab host

Expected behaviour

• Instead of timing out after 2hours or more, it should fail almost immediately with "Failed to provision machine on digitalocean (Size 2gb is not available in region ams2)" or something similar

I had a similar problem a few months ago when I reached my droplet limit in Digitalocean, almost no output and I had to guess what was wrong.

Relevant logs and/or screenshots

Environment description

[root@gimel ~]# docker-machine version docker-machine version 0.13.0, build 9ba6da9 [root@gimel ~]#

Relevant gitlab runner configuration

    MachineDriver = "digitalocean"
    MachineName = "gitlab-ci-%s"
    MachineOptions = ["digitalocean-image=coreos-stable", "digitalocean-ssh-user=core", "digitalocean-access-token=thisissecret", "digitalocean-region=ams2", "digitalocean-size=2gb", "digitalocean-private-networking"]

Latest gitlab-ce and gitlab-runner for CentOS packages

Used GitLab Runner version

[root@gimel ~]# gitlab-runner --version
Version:      9.5.1
Git revision: 96b34cc
Git branch:   9-5-stable
GO version:   go1.8.3
Built:        Wed, 04 Oct 2017 16:26:27 +0000
OS/Arch:      linux/amd64