cloudfoundry / cf-mysql-release

Cloud Foundry MySQL Release
Apache License 2.0
58 stars 106 forks source link

Bosh deploy hangs on compiling packages. #152

Closed keenemaverick closed 7 years ago

keenemaverick commented 7 years ago

So I'm trying to deploy this on a fresh CF deployment on Openstack. When I get to the step to deploy, I get this:

  Started compiling packages > cluster-schema-verifier/a2f8659250e5b51a7f5d0b0fdff5dbdc5ee98895
  Started compiling packages > cli/8b1ad6b02cd78fc4950b7ed83d1d83c12d6a99cb
  Started compiling packages > mysqlclient/ce95f8ac566f76b650992987d5282ee473356e43
  Started compiling packages > ruby/a57562f234ecf56581a73f2e18715f19ea74e9f1
   Failed compiling packages > cli/8b1ad6b02cd78fc4950b7ed83d1d83c12d6a99cb: Timed out pinging to 8b2e8505-d1b8-443f-b263-b0c643246507 after 600 seconds (00:11:16)
   Failed compiling packages > mysqlclient/ce95f8ac566f76b650992987d5282ee473356e43: Timed out pinging to 46c3a52f-4441-4e4e-8fd0-1aebb5781f09 after 600 seconds (00:11:20)
   Failed compiling packages > ruby/a57562f234ecf56581a73f2e18715f19ea74e9f1: Timed out pinging to 7d009ff7-4ce5-45e9-86fd-67378ba101f5 after 600 seconds (00:11:20)
   Failed compiling packages > cluster-schema-verifier/a2f8659250e5b51a7f5d0b0fdff5dbdc5ee98895: Timed out pinging to f0c58c26-aac7-467f-9bcb-05d7e8aff78a after 600 seconds (00:11:21)

Error 450002: Timed out pinging to 8b2e8505-d1b8-443f-b263-b0c643246507 after 600 seconds

Here's the manifest I'm using to deploy...

cf-mysql.yml.txt

I can't figure out what's going wrong, and I'm not too sure where to look. Digging through the debug logs I'll occasionally see things like this:

DEBUG -- : excon.error {:error=>#<Excon::Errors::NotFound: Expected([200, 203]) <=> Actual(404 Not Found)
excon.error.response
  :body          => "{\"itemNotFound\": {\"message\": \"Instance c9db51c3-c249-4ffc-b391-aca544a0ac23 could not be found.\", \"code\": 404}}"
  :cookies       => [
  ]
  :headers       => {
    "Connection"           => "close"
    "Content-Length"       => "111"
    "Content-Type"         => "application/json; charset=UTF-8"
    "Date"                 => "Tue, 14 Mar 2017 20:02:34 GMT"
    "X-Compute-Request-Id" => "req-54a848bd-ae18-489e-8da1-797790b9673c"
  }
  :host          => "192.168.0.22"
  :local_address => "192.168.111.15"
  :local_port    => 54070
  :path          => "/v2/7809716d41f24e16bb71244008097120/servers/c9db51c3-c249-4ffc-b391-aca544a0ac23.json"
  :port          => 8774
  :reason_phrase => "Not Found"
  :remote_ip     => "192.168.0.22"
  :status        => 404
  :status_line   => "HTTP/1.1 404 Not Found\r\n"
>}

But, it's not even at the creating instances part yet, it's just compiling packages, so why is it trying to find instances? I'm quite confused...

cf-gitbot commented 7 years ago

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

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

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

keenemaverick commented 7 years ago

Ah, never mind. The issue was two-fold: When creating the networks in OpenStack, DHCP needs to be enabled, and a router interface must also be created.