cloudfoundry-attic / bootstrap-cf-plugin Goto Github PK

Link to the thread: https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/TPdWxT8LH8w

Running bosh deploy...
Current target is https://54.209.29.217:25555 (micro-manu)
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Compiling deployment manifest...
Latest version for stemcell `bosh-aws-xen-ubuntu' is unknown
Time of crash:
  2013-11-06 15:24:02 -0800

RuntimeError: Failed to run: bosh -n deploy

03:56 PM $ bosh stemcells

+---------------+---------+--------------+
| Name          | Version | CID          |
+---------------+---------+--------------+
| bosh-stemcell | 992     | ami-fdeca594 |
+---------------+---------+--------------+

Stemcells total: 1

https://github.com/cloudfoundry/bootstrap-cf-plugin/blob/master/bootstrap-cf-plugin.gemspec#L19

I can PR this repo & http://docs.cloudfoundry.com/docs/running/deploying-cf/ec2/ docs.

@pivotal-vmware will need to update its internal CI systems to add this gem explicitly to the Gemfile.

In cf-aws.yml, the default network's subnet range does not match the CIDR in the assigned AWS VPC subnet. In the example below, subnet-71a2aa1c has a CIDR of 10.10.2.0/23.

networks:

• name: default
  type: manual
  subnets:
  • range: 10.10.1.0/24
    name: default_unused
    reserved:
    • 10.10.1.2 - 10.10.1.9
      static:
    • 10.10.1.10 - 10.10.1.30
      gateway: 10.10.1.1
      dns:
    • 10.10.0.2 # amazon has only 1 DNS server for the whole VPC at x.x.0.2
      cloud_properties:
      security_groups:
      • cf
        subnet: subnet-71a2aa1c

Deploying this manifest results in the error;

Compiling packages
mysql/13: Address 10.10.1.51 does not fall within the subnet's address range (00:00:01)
mysql55/6: Address 10.10.1.50 does not fall within the subnet's address range (00:00:01)
redis26/1: Address 10.10.1.49 does not fall within the subnet's address range (00:00:04)
Error 3/43 00:00:04

Error 100: Address 10.10.1.51 does not fall within the subnet's address range

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.

This is continuation to #15: when cf bootstrap aws creates a release and that process fails because there is no disk space left, the error message does not make it clear
what step failed (and why):

New version copied to '/home/ubuntu/deployments-aws/mklishin/cf-aws.yml'
Running bosh deploy...
Current target is https://[redacted]:25555 (micro-mklishin)
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Compiling deployment manifest...
Release 'cf-release' not found on director. Unable to resolve 'latest' alias in manifest.Time of crash:
  2013-09-09 15:58:04 +0000

RuntimeError: Failed to run: bosh -n deploy

bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/infrastructure/aws.rb:87:in `sh'
bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/infrastructure/aws.rb:43:in `deploy_release'
bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/infrastructure/aws.rb:9:in `bootstrap'
bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/plugin.rb:15:in `bootstrap'

I suspect there is an error swallowed, which makes the bootstrap code continue even though release upload failed.

cf bootstrap aws no longer finishes successfully when you follow the steps in the docs.

The failure is

New version copied to '/home/ubuntu/deployments-aws/mklishin/cf-aws.yml'
Running bosh deploy...
Current target is https://[redacted]:25555 (micro-mklishin)
Getting deployment properties from director...
Unable to get properties list from director, trying without it...
Compiling deployment manifest...
Release 'cf-release' not found on director. Unable to resolve 'latest' alias in manifest.Time of crash:
  2013-09-09 15:58:04 +0000

RuntimeError: Failed to run: bosh -n deploy

bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/infrastructure/aws.rb:87:in `sh'
bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/infrastructure/aws.rb:43:in `deploy_release'
bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/infrastructure/aws.rb:9:in `bootstrap'
bootstrap-cf-plugin-124afe8619bd/lib/bootstrap-cf-plugin/plugin.rb:15:in `bootstrap'

Exactly the same steps succeeded a couple of weeks ago.

Preparing configuration
binding configuration: Error filling in template loggregator_trafficcontroller.json.erb' forloggregator-trafficcontroller_z1/0' (line 5: Can't find property `["ssl.skip_cert_verify"]') (00:00:04)
Error 1/1 00:00:04

Error 80006: Error filling in template loggregator_trafficcontroller.json.erb' forloggregator-trafficcontroller_z1/0' (line 5: Can't find property `["ssl.skip_cert_verify"]')

Task 4 error

For a more detailed error report, run: bosh task 4 --debug
Time of crash:
2013-11-04 17:40:39 -0500

RuntimeError: Failed to run: bosh -n deploy

bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/infrastructure/aws.rb:87:in sh' bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/infrastructure/aws.rb:43:indeploy_release'
bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/infrastructure/aws.rb:9:in bootstrap' bootstrap-cf-plugin-ee90e91d0309/lib/bootstrap-cf-plugin/plugin.rb:15:inbootstrap'
mothership-0.5.1/lib/mothership/base.rb:66:in run' mothership-0.5.1/lib/mothership/command.rb:72:inblock in invoke'
mothership-0.5.1/lib/mothership/command.rb:86:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:86:ininvoke'
mothership-0.5.1/lib/mothership/base.rb:55:in execute' cf-5.2.2/lib/cf/cli.rb:195:inblock (2 levels) in execute'
cf-5.2.2/lib/cf/cli.rb:206:in save_token_if_it_changes' cf-5.2.2/lib/cf/cli.rb:194:inblock in execute'
cf-5.2.2/lib/cf/cli.rb:123:in wrap_errors' cf-5.2.2/lib/cf/cli.rb:190:inexecute'
mothership-0.5.1/lib/mothership.rb:45:in start' cf-5.2.2/bin/cf:18:in<top (required)>'
ruby-1.9.3-p392/bin/cf:19:in load' ruby-1.9.3-p392/bin/cf:19:in