__wait_for_connect should inform it is waiting

[avelanarius]

For a beginner user of orchestrator, when running scripts it can be unclear what is happening, for example:

$ ./bm_cassandra.py 
[14:52:01]-------------[ Installing Cassandra: started ]--------------------------------------------------------
    [18.223.15.97] Update: started

(in my case) hangs for a few minutes after "Update: started", with no feedback. Behind the scenes, it is waiting in __wait_for_connect, but no feedback for a user is presented. Ideally, something like this should be printed:

$ ./bm_cassandra.py 
[14:52:01]-------------[ Installing Cassandra: started ]--------------------------------------------------------
    [18.223.15.97] Update: started
    [18.223.15.97] Waiting for a successful connection
    [18.223.15.97] Still waiting for a successful connection (10 seconds elapsed, X second timeout)
    [18.223.15.97] Still waiting for a successful connection (20 seconds elapsed, X second timeout)

[pveentjer]

There is a configurable silence period that defaults to 30s. So after 30s you will get logging that it is trying. So it you don't see any logging for more than 30s, then there is a bug.

[pveentjer]

The bug has been confirmed. Trying to figure out what is the cause.