Error filling in template `settings.yml.erb''

[cloudfoundry]

Error filling in template `settings.yml.erb''

[jhellan]

Backtrace in https://gist.github.com/jhellan/8435013

[dajulia3]

@jhellan we are unable to reproduce this issue using cf-mysql version 5 and BOSH 1.1761.0 with HEAD of master of cf-mysql-release. Are you using an older cf-mysql-release?

[jhellan]

On 15. jan. 2014 22:56, David Julia wrote:

@jhellan https://github.com/jhellan we are unable to reproduce this
issue using cf-mysql version 5 and BOSH 1.1761.0 with HEAD of master of
cf-mysql-release. Are you using an older cf-mysql-release?

No, it's cf-mysql 5 from releases/cf-mysql-5.yml. cf-mysql-release git
is at 984648. We have the same issue on bosh-lite hosted on OS-X and a
"real" bosh + cloud foundry deployment.

Jon

[dbailey]

We were able to reproduce with:

git clone [email protected]:cloudfoundry/cf-mysql-release.git
cd cf-mysql-release/
git submodule update --init
bosh upload release releases/cf-mysql-5.yml
./bosh-lite/make_manifest_spiff_mysql
bosh deploy

@shalako Are we doing something wrong or if not can you look into this?

• @dbailey && @dajulia3

[shalako]

Known issues with cf-mysql-release and bosh-lite. We're working through them in https://www.pivotaltracker.com/story/show/60887904

Current advice is to use latest bosh-lite (uses BOX_VERSION: 147 in Vagrantfile) and master of cf-release which includes a networking fix.

[dajulia3]

Great, thanks Shannon. @jhellan We're going to close this since there's work underway on the issue and you should be able to use the work-around that @shalako provided above.

[jhellan]

Glad to hear that other people have found a workaround.
Here, we have been using vagrant box 147 all along. I deleted the vagrant vm today and tried with cf-release head. Same error. I received an email suggesting that a newer spiff might help. But it turns out that spiff 0.2.0 from github and spiff 0.0.0 from spiff.cfapps.io produce the exact same manifest, both for cf and cf-mysql-release.

No big deal though. I already have the broker deployed without bosh assistance.

I reported the issue mostly because I've seen the same type of error before, and never understood precisely what made it go away. Any explanation about what exectly goes wrong here?

[shalako]

@jhellan This is fixed by deploying cf-release from head and deploying cf-mysql-release from head or using final release 6.