Failed to run 'boosh resources --name $stack_name' when trying to deploy cf/diego to AWS

[StanleyShen]

when trying to deploy CF to AWS based on https://github.com/cloudfoundry/diego-release/tree/develop/examples/aws
It fails to get stack resource with below error message

boosh resources --name $stack_name > a.yml
Get https://cloudformation.amazonaws.com?AWSAccessKeyId=xxxxxx&Action=ListStackResources&SignatureMethod=HmacSHA256&SignatureVersion=2&StackName=xxxxxxxx&Timestamp=2017-07-05T05%3A43%3A04&Version=2010-05-15&Signature=xxxxxx: dial tcp: lookup cloudformation.amazonaws.com: no such host

any idea on it?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/148318747

The labels on this github issue will be updated when the story is started.

[emalm]

Hi, @StanleyShen,

I see you received some assistance with this issue in the Cloud Foundry Slack, starting at https://cloudfoundry.slack.com/archives/C02FL4A2K/p1499233640176790. Did that help resolve this issue?

Thanks,
Eric, CF Diego PM

[StanleyShen]

I didn't go through the step from scratch yet, and it works for me for now.
I can create a new ticket if I can reproduce the issue again.

Another thing is that from the page, we are required to use bosh v2, but when deploying cf/diego, we are using bosh v1 again (like bosh create release, bosh upload release) , should we be consistent with that?

[emalm]

Thanks, @StanleyShen , glad to hear the issue resolved itself with the correct environmental setup. Since that problem is resolved, I'll close out this issue.

You're right, the v2 BOSH CLI doesn't currently build release tarballs or dev releases correctly for cf-release, although there is ongoing work in cloudfoundry/bosh-cli#232 to fix that discrepancy. It does work to upload an existing final release tarball (such as one obtained from https://bosh.io/releases/github.com/cloudfoundry/cf-release) or final release manifest (such as https://github.com/cloudfoundry/cf-release/blob/v266/releases/cf-266.yml), though. I've added https://www.pivotaltracker.com/story/show/148375009 to the Diego tracker for us to update the examples/aws docs to note the compatibility issue and some workarounds, or to document the minimum required version of the v2 BOSH CLI once that PR is merged.

Best,
Eric