Date
1 - 8 of 8
`bosh upload release` times out creating packages
|
Josh Ghiloni
Hi all,
I’m trying to set up a BOSH-managed Consul Cluster using the cloudfoundry-community Consul BOSH release [1] on OpenStack. I’ve been able to run all the steps through `bosh create release --force` but `bosh upload release` is failing on me. It appears that it’s trying to call out to the blobstore and timing out there. I created my environment using `bosh-init` and followed the instructions on bosh.io for doing that. I’ve included my bosh.yml [2] I used for `bosh-init`, as well as a log snippet from the bosh task debug command [3]. Please let me know what else I can do to help. Thanks! [1] https://github.com/cloudfoundry-community/consul-boshrelease [2] http://pastebin.com/BWT5apCW [3] http://pastebin.com/pp9KEFgE Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com ECS Team Technology Solutions Delivered ECSTeam.com |
|
|
|
Dr Nic Williams
Josh, to confirm - is uploading other bosh releases to your microbosh also failing? Eg uploading releases from bosh.io?
On Mon, Jun 15, 2015 at 11:10 AM, Josh Ghiloni <jghiloni(a)ecsteam.com> wrote: Hi all, |
|
|
|
Josh Ghiloni
That’s a good question. I’m not even sure this is a microbosh environment. I followed the steps to use `bosh-init`, which I was under the impression created a full-fledged BOSH environment. Should I be creating a microbosh to begin with?
toggle quoted message
Show quoted text
Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ECSTeam.com> On Jun 15, 2015, at 13:21, Dr Nic Williams <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote:
Josh, to confirm - is uploading other bosh releases to your microbosh also failing? Eg uploading releases from bosh.io? On Mon, Jun 15, 2015 at 11:10 AM, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote: Hi all, I’m trying to set up a BOSH-managed Consul Cluster using the cloudfoundry-community Consul BOSH release [1] on OpenStack. I’ve been able to run all the steps through `bosh create release --force` but `bosh upload release` is failing on me. It appears that it’s trying to call out to the blobstore and timing out there. I created my environment using `bosh-init` and followed the instructions on bosh.io for doing that. I’ve included my bosh.yml [2] I used for `bosh-init`, as well as a log snippet from the bosh task debug command [3]. Please let me know what else I can do to help. Thanks! [1] https://github.com/cloudfoundry-community/consul-boshrelease [2] http://pastebin.com/BWT5apCW [3] http://pastebin.com/pp9KEFgE Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ECSTeam.com> _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|
|
Dr Nic Williams
The first dozen lines of [2] show that you're deploying a bosh via bosh-init (which I'll call a microbosh).
On Mon, Jun 15, 2015 at 11:10 AM, Josh Ghiloni <jghiloni(a)ecsteam.com> wrote: Hi all, |
|
|
|
Josh Ghiloni
Thanks for the clarification of microbosh — sometimes I get a bit confused between bosh, bosh-lite, and microbosh. I did try uploading a different release directly from bosh.io (vs creating the release myself) and it failed in the same place. The backtrace indicates an error with the Blobstore — specifically the DavBlobstoreClient. I confirmed that the microbosh is listening on the port specified in bosh.yml (25250) for the blobstore. It seems to be trying to call out somewhere (perhaps to itself?) but a tcpdump didn’t really help much as the connection was never made.
toggle quoted message
Show quoted text
Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ECSTeam.com> On Jun 15, 2015, at 13:26, Dr Nic Williams <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote:
The first dozen lines of [2] show that you're deploying a bosh via bosh-init (which I'll call a microbosh). On Mon, Jun 15, 2015 at 11:10 AM, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote: Hi all, I’m trying to set up a BOSH-managed Consul Cluster using the cloudfoundry-community Consul BOSH release [1] on OpenStack. I’ve been able to run all the steps through `bosh create release --force` but `bosh upload release` is failing on me. It appears that it’s trying to call out to the blobstore and timing out there. I created my environment using `bosh-init` and followed the instructions on bosh.io for doing that. I’ve included my bosh.yml [2] I used for `bosh-init`, as well as a log snippet from the bosh task debug command [3]. Please let me know what else I can do to help. Thanks! [1] https://github.com/cloudfoundry-community/consul-boshrelease [2] http://pastebin.com/BWT5apCW [3] http://pastebin.com/pp9KEFgE Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ECSTeam.com> _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|
|
Josh Ghiloni
Welp, I’m an idiot. My bosh.yml had the solution the whole time and I didn’t even see it till reading things for the ten thousandth time. I should have been pointing everything to 192.168.245.2, not 192.168.254.2. I’m redeploying my microbosh now and will be trying the upload release again in a moment.
toggle quoted message
Show quoted text
Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ECSTeam.com> On Jun 15, 2015, at 13:38, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote:
Thanks for the clarification of microbosh — sometimes I get a bit confused between bosh, bosh-lite, and microbosh. I did try uploading a different release directly from bosh.io (vs creating the release myself) and it failed in the same place. The backtrace indicates an error with the Blobstore — specifically the DavBlobstoreClient. I confirmed that the microbosh is listening on the port specified in bosh.yml (25250) for the blobstore. It seems to be trying to call out somewhere (perhaps to itself?) but a tcpdump didn’t really help much as the connection was never made. Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ecsteam.com/> On Jun 15, 2015, at 13:26, Dr Nic Williams <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote: The first dozen lines of [2] show that you're deploying a bosh via bosh-init (which I'll call a microbosh). On Mon, Jun 15, 2015 at 11:10 AM, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote: Hi all, I’m trying to set up a BOSH-managed Consul Cluster using the cloudfoundry-community Consul BOSH release [1] on OpenStack. I’ve been able to run all the steps through `bosh create release --force` but `bosh upload release` is failing on me. It appears that it’s trying to call out to the blobstore and timing out there. I created my environment using `bosh-init` and followed the instructions on bosh.io for doing that. I’ve included my bosh.yml [2] I used for `bosh-init`, as well as a log snippet from the bosh task debug command [3]. Please let me know what else I can do to help. Thanks! [1] https://github.com/cloudfoundry-community/consul-boshrelease [2] http://pastebin.com/BWT5apCW [3] http://pastebin.com/pp9KEFgE Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ecsteam.com/> _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|
|
Josh Ghiloni
That was it. A cautionary tale, I suppose.
toggle quoted message
Show quoted text
Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ECSTeam.com> On Jun 15, 2015, at 14:51, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote:
Welp, I’m an idiot. My bosh.yml had the solution the whole time and I didn’t even see it till reading things for the ten thousandth time. I should have been pointing everything to 192.168.245.2, not 192.168.254.2. I’m redeploying my microbosh now and will be trying the upload release again in a moment. Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ecsteam.com/> On Jun 15, 2015, at 13:38, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote: Thanks for the clarification of microbosh — sometimes I get a bit confused between bosh, bosh-lite, and microbosh. I did try uploading a different release directly from bosh.io (vs creating the release myself) and it failed in the same place. The backtrace indicates an error with the Blobstore — specifically the DavBlobstoreClient. I confirmed that the microbosh is listening on the port specified in bosh.yml (25250) for the blobstore. It seems to be trying to call out somewhere (perhaps to itself?) but a tcpdump didn’t really help much as the connection was never made. Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ecsteam.com/> On Jun 15, 2015, at 13:26, Dr Nic Williams <drnicwilliams(a)gmail.com<mailto:drnicwilliams(a)gmail.com>> wrote: The first dozen lines of [2] show that you're deploying a bosh via bosh-init (which I'll call a microbosh). On Mon, Jun 15, 2015 at 11:10 AM, Josh Ghiloni <jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com>> wrote: Hi all, I’m trying to set up a BOSH-managed Consul Cluster using the cloudfoundry-community Consul BOSH release [1] on OpenStack. I’ve been able to run all the steps through `bosh create release --force` but `bosh upload release` is failing on me. It appears that it’s trying to call out to the blobstore and timing out there. I created my environment using `bosh-init` and followed the instructions on bosh.io for doing that. I’ve included my bosh.yml [2] I used for `bosh-init`, as well as a log snippet from the bosh task debug command [3]. Please let me know what else I can do to help. Thanks! [1] https://github.com/cloudfoundry-community/consul-boshrelease [2] http://pastebin.com/BWT5apCW [3] http://pastebin.com/pp9KEFgE Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions Delivered ECSTeam.com<http://ecsteam.com/> _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh _______________________________________________ cf-bosh mailing list cf-bosh(a)lists.cloudfoundry.org<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh |
|
|
|
Dr Nic Williams
Nice find.
On Mon, Jun 15, 2015 at 1:51 PM, Josh Ghiloni <jghiloni(a)ecsteam.com> wrote: Welp, I’m an idiot. My bosh.yml had the solution the whole time and I didn’t even see it till reading things for the ten thousandth time. I should have been pointing everything to 192.168.245.2, not 192.168.254.2. I’m redeploying my microbosh now and will be trying the upload release again in a moment. |
|
|