dajulia3
commented
10 years ago @RobAtSGH As an organization we have decided that we are no longer supporting or maintaining cf bootstrap aws. We will be moving the repo into the cloudfoundry-attic.
Thanks for your issue report, and sorry no one got back to you on this sooner!
I have a hosted domain in AWS - whoisrnovak.net - with a subdomain cftest.whoisrnovak.net, where I am targeting to execute "cf bootstrap aws". The micro-BOSH instance deploys properly, the deployment builds and compiles, and all the VMs start. However, cf-services deployment fails with "Error 400007: mysql_gateway/0' is not running after update." Attempting to execute "cf target" results in "Setting target to https://api.cftest.whoisrnovak.net... FAILED CFoundry::NotFound: 404: 404 Not Found: Requested route ('api.cftest.whoisrnovak.net') does not exist."
The only network element that was created outside of the bootstrap process (and therefore under my control) is the DNS zone delegation. The AWS deployment README essentially hints that if the api call fails, it's probably a network issue, hinting at proper DNS config. All other elements, configurations, bindings, etc. are created by the automated deploy.
The registrar NS entries point to the nameservers of the whoisrnovak.net hosted zone: Domain servers in listed order: ns-1107.awsdns-10.org ns-1809.awsdns-34.co.uk ns-920.awsdns-51.net ns-248.awsdns-31.com
A separate hosted zone cftest.whoisrnovak.net is the VPC target, and NS records exist in the whoisrnovak.net zone config. Fetching the NS records for the subdomain gives the expected results. ;; QUESTION SECTION: ;cftest.whoisrnovak.net. IN NS
;; ANSWER SECTION: cftest.whoisrnovak.net. 3600 IN NS ns-1196.awsdns-21.org. cftest.whoisrnovak.net. 3600 IN NS ns-1870.awsdns-41.co.uk. cftest.whoisrnovak.net. 3600 IN NS ns-447.awsdns-55.com. cftest.whoisrnovak.net. 3600 IN NS ns-581.awsdns-08.net.
;; ADDITIONAL SECTION: ns-1870.awsdns-41.co.uk. 115086 IN A 205.251.199.78 ns-447.awsdns-55.com. 42765 IN A 205.251.193.191 ns-581.awsdns-08.net. 96967 IN A 205.251.194.69 ns-1196.awsdns-21.org. 109253 IN A 205.251.196.172
Querying for a known host gives the proper answer. ;; QUESTION SECTION: ;micro.cftest.whoisrnovak.net. IN A
;; ANSWER SECTION: micro.cftest.whoisrnovak.net. 60 IN A 54.209.33.68
As does the wildcard CNAME for the router. ;; QUESTION SECTION: ;api.cftest.whoisrnovak.net. IN A
;; ANSWER SECTION: api.cftest.whoisrnovak.net. 60 IN CNAME cfrouter-495439923.us-east-1.elb.amazonaws.com. cfrouter-495439923.us-east-1.elb.amazonaws.com. 60 IN A 54.236.146.108 cfrouter-495439923.us-east-1.elb.amazonaws.com. 60 IN A 107.23.170.112
Something seems broken in the way the router is being deployed/configured during the process, from the looks of it.