As far as I am aware the cf-secrets.yml is pulled in from the templates section within cf-aws-tiny.yml. See Gist<https://gist.github.com/mminges/c69cdbcaac33aa94b4bf>. Then spiff merge would combine the templates into a .stub cf-aws-tiny.yml, is that correct?

Thanks,

Michael Minges

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Tuesday, August 11, 2015 3:01 PM
To: Discussions about the Cloud Foundry BOSH project. <cf-bosh(a)lists.cloudfoundry.org>
Subject: [cf-bosh] Re: Upgrading CF to 214 Release Fails During Configuration

Does your deployment manifest (deployments/cf-was-tiny.yml) have the required property? What's in that gist is not guaranteed to be in your manifest unless we know how you use that gist in your manifest generation.

On Tuesday, August 11, 2015, Michael Minges <mminges(a)ecsteam.com<mailto:mminges(a)ecsteam.com>> wrote:
Hello,

We had deployed CloudFoundry, release 208, on AWS using Terraform. Since then, we had successfully upgraded to release 210 and subsequently to release 212. Currently, we are working through upgrading from release 212 to the latest 214 release. After updating the deployment manifest to use the 214 release as well as to use the latest stemcell, bosh-aws-xen-hvm-ubuntu-trusty-go_agent version 3033, we used the following bosh commands to deploy:

bosh deployment deployments/cf-aws-tiny.yml (target the correct deployment)
bosh prepare deployment (resolve deployment requirements)
bosh deploy

The deploy ran for about twenty minutes then failed with the following:

Started preparing configuration > Binding configuration. Failed: Error filling in template `gorouter.yml.erb' for `api/0' (line 50: Can't find property `["uaa.clients.gorouter.secret"]') (00:00:03)

Error 100: Error filling in template `gorouter.yml.erb' for `api/0' (line 50: Can't find property `["uaa.clients.gorouter.secret"]')

Within the director VM, /home/ubuntu/workspace/deployments/cf-boshworkspace/templates/cf-secrets.yml shows that the property, uaa.clients.gorouter.secret, does exist. See Gist<https://gist.github.com/mminges/0525c8d87c176e31f0fe>.

Any suggestions on where to start with troubleshooting?

Michael Minges
Associate Consultant
303.815.6471 m
mminges(a)ECSTeam.com<mailto:mminges(a)ECSTeam.com>

ECS Team
Technology Solutions Delivered
ECSTeam.com<http://www.ecsteam.com/>
LinkedIn<http://www.linkedin.com/company/ecsteam> | Twitter<https://twitter.com/ecsteam>