Concourse plugin requires --web-ip

[guidowb]

+1 to @haydonryan #37. Saw that exact error. Then after uploading the stemcell, I got the exact same error again. This time, the root cause was:

==> beacon_ctl.log <==
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'
/var/vcap/jobs/groundcrew/bin/beacon_ctl: line 51: syntax error near unexpected token `}'

Turns out that happens when you don't provide the --web-ip parameter, because then the number of web instances defaults to 0 and that breaks a shell script. This time, even the bosh task logs wouldn't have been very helpful in identifying the root cause:

2016/11/09 12:56:50 D1109 12:56:50.526933 10963 api.go:177] rest resp:  {"id":23,"state":"error","description":"create deployment","timestamp":1478717809,"started_at":1478717482,"result":"'worker/0 (4837b190-e7b7-41d4-8ff2-144743ba6b0d)' is not running after update. Review logs for failed jobs: beacon,...","user":"director","deployment":"concourse"}

Seems the the concourse plugin should require the --web-ip parameter since omitting it leads to an obscure failure.

[zmb3]

The --web-ip flag is required as of this commit, which will be available in the next release.