Bug in Start Cluster

[stephens336]

Issue: If an invalid cluster id is sent to Start Cluster, the task does not exit with an error. The error shows in the log, but then get's hung in a retry loop.

Steps to reproduce:

• Create or use an existing Databricks cluster.
• Add the Configure Databricks CLI task with correct settings.
• Add the Start Cluster task, setting an invalid cluster id (lorumipsum, for example)
• Run the build or release.

It should produce a log like this, never exiting until the task for force-cancelled:

2019-09-11T22:19:32.5433396Z ##[section]Starting: Starting Cluster lorumipsum
2019-09-11T22:19:32.5539474Z ==============================================================================
2019-09-11T22:19:32.5539630Z Task         : Start a Databricks Cluster
2019-09-11T22:19:32.5539723Z Description  : Make sure a Databricks Cluster is started
2019-09-11T22:19:32.5539823Z Version      : 0.5.2
2019-09-11T22:19:32.5539898Z Author       : Microsoft DevLabs
2019-09-11T22:19:32.5539996Z Help         : 
2019-09-11T22:19:32.5540104Z ==============================================================================
2019-09-11T22:19:37.5287181Z parse error: Invalid numeric literal at line 1, column 6
2019-09-11T22:19:37.5382200Z Cluster lorumipsum not running, turning on...
2019-09-11T22:19:38.3798571Z Error: b'{"error_code":"INVALID_PARAMETER_VALUE","message":"Cluster lorumipsum does not exist"}'
2019-09-11T22:19:39.2306530Z parse error: Invalid numeric literal at line 1, column 6
2019-09-11T22:20:09.5652770Z Starting...
2019-09-11T22:20:10.2523779Z parse error: Invalid numeric literal at line 1, column 6
2019-09-11T22:20:40.3022300Z Starting...
2019-09-11T22:20:41.2190210Z parse error: Invalid numeric literal at line 1, column 6
2019-09-11T22:21:11.2460626Z Starting...
2019-09-11T22:21:12.1989743Z parse error: Invalid numeric literal at line 1, column 6
2019-09-11T22:21:24.5662474Z ##[error]The operation was canceled.
2019-09-11T22:21:24.5667493Z ##[section]Finishing: Starting Cluster lorumipsum