Unable to deploy latest diego release onto bosh-lite

[rahulkj]

I've been trying to install the latest release 0.1335.0 on my bosh-lite with cf release 212. Each time I run a bosh -n deploy for diego, I get the following error:

  Started binding instance vms
  Started binding instance vms > database_z1/0
  Started binding instance vms > brain_z1/0
  Started binding instance vms > cell_z1/0
  Started binding instance vms > cc_bridge_z1/0
  Started binding instance vms > route_emitter_z1/0
  Started binding instance vms > access_z1/0. Done (00:00:00)
     Done binding instance vms > cc_bridge_z1/0 (00:00:00)
     Done binding instance vms > database_z1/0 (00:00:00)
     Done binding instance vms > cell_z1/0 (00:00:00)
     Done binding instance vms > brain_z1/0 (00:00:00)
     Done binding instance vms > route_emitter_z1/0 (00:00:00)
     Done binding instance vms (00:00:00)

  Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array) (00:00:00)

Error 100: Error filling in template `agent_ctl.sh.erb' for `database_z1/0' (line 31: undefined method `tr' for ["bbs", {}]:Array)

Task 23 error

I'm not sure what should go in for the bbs configuration?
I get similar issues with cc_bridge_z1 and access_z1

bosh vms results with the following output

bosh vms
Acting as user 'admin' on 'Bosh Lite Director'
Deployment `cf-warden'

Director task 28

Task 28 done

+------------------------------------+---------+---------------+--------------+
| Job/index                          | State   | Resource Pool | IPs          |
+------------------------------------+---------+---------------+--------------+
| api_z1/0                           | running | large_z1      | 10.244.0.134 |
| consul_z1/0                        | running | medium_z1     | 10.244.0.54  |
| doppler_z1/0                       | running | medium_z1     | 10.244.0.142 |
| etcd_z1/0                          | running | medium_z1     | 10.244.0.42  |
| ha_proxy_z1/0                      | running | router_z1     | 10.244.0.34  |
| hm9000_z1/0                        | running | medium_z1     | 10.244.0.138 |
| loggregator_trafficcontroller_z1/0 | running | small_z1      | 10.244.0.146 |
| nats_z1/0                          | running | medium_z1     | 10.244.0.6   |
| postgres_z1/0                      | running | medium_z1     | 10.244.0.30  |
| router_z1/0                        | running | router_z1     | 10.244.0.22  |
| runner_z1/0                        | running | runner_z1     | 10.244.0.26  |
| uaa_z1/0                           | running | medium_z1     | 10.244.0.130 |
+------------------------------------+---------+---------------+--------------+

VMs total: 12
Deployment `cf-warden-diego'

Director task 29

Task 29 done

+--------------------+---------+------------------+---------------+
| Job/index          | State   | Resource Pool    | IPs           |
+--------------------+---------+------------------+---------------+
| access_z1/0        | running | access_z1        | 10.244.16.6   |
| brain_z1/0         | running | brain_z1         | 10.244.16.134 |
| cc_bridge_z1/0     | running | cc_bridge_z1     | 10.244.16.142 |
| cell_z1/0          | running | cell_z1          | 10.244.16.138 |
| database_z1/0      | running | database_z1      | 10.244.16.130 |
| route_emitter_z1/0 | running | route_emitter_z1 | 10.244.16.146 |

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/98076660.

[emalm]

Hi, @rahulkj,

Since CF v212, there's been a change to the manifest data that cf-release's consul_agent job consumes: it used to take a list of strings, and now it takes a map of strings to sets of tags. The diego-release manifest generation templates as of v0.1317.0 now produces this updated set of consul data, but v212 of cf-release still uses the old-style list data. This means that v0.1317.0 and later of diego-release will generate manifests incompatible with CF v212.

Based on the release notes for CF v212, Diego final version v0.1304.0 is compatible, so you may consider deploying that version instead. In general, Diego creates final releases much more frequently than CF does, so there's no guarantee that the master branch of diego-release will be compatible with the master branch of cf-release. The Diego-CF compatibility record tracks which combinations of cf-release and diego-release have passed our automated testing pipeline.

Thanks,
Eric, CF Runtime Diego PM

[rahulkj]

Ah makes complete sense. I'll give a shot with v0.1304.0.

Also thanks for the compatibility record link. That would be one helpful link.

Cheers!