Date   

Execute scripts / tests inside bosh-managed VMs

Michael Grifalconi <michael.grifalconi@...>
 

Hello all, 

I'd like to run some scripts inside VMs deployed by BOSH, is it possible?

Like: with bosh IP address, credentials, deployment name and VM name, run this script, without doing it manually with bosh ssh command.



Thank you

Regards,
Michael

****************
Per destinare il 5x1000 all'Universita' degli Studi di Milano: indicare nella dichiarazione dei redditi il codice fiscale 80012650158.

http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille


does bosh delete VMs in error state [nova] on OpenStack?

Lukas Lehner <weblehner@...>
 

Hi

does bosh delete VMs in error state on OpenStack?

I am doing a bosh deploy and see with "nova list" that bosh creates VMs.

They fail in error state and then gone. Is that some bosh mechanism?

I need this error state VMs for OpenStack troubleshooting

$ nova list | grep -v ACTIVE
+--------------------------------------+-----------------------------------------+--------+---------------------------
-------------------+
| ID | Name
| Status | Networks
|
+--------------------------------------+-----------------------------------------+--------+---------------------------
-------------------+
| 0f09b6aa-4baa-4182-b3d2-e9c86d085d2a |
vm-3e129693-7ae6-438a-9e9d-61fec93abf02 | ERROR |
|
| d04e7611-4e55-4c86-854a-31b4df2fda5c |
vm-ddf9862b-1858-4904-bfb3-0c57c37b53c7 | BUILD |
|
+--------------------------------------+-----------------------------------------+--------+---------------------------
-------------------+


ten seconds later the error state VM is gone:

$ nova list | grep 0f09b6aa-4baa-4182-b3d2-e9c86d085d2a
$ nova list | grep -v ACTIVE
+--------------------------------------+-----------------------------------------+--------+---------------------------
-------------------+
| ID | Name
| Status | Networks
|
+--------------------------------------+-----------------------------------------+--------+---------------------------
-------------------+
| d04e7611-4e55-4c86-854a-31b4df2fda5c |
vm-ddf9862b-1858-4904-bfb3-0c57c37b53c7 | BUILD |
|
+--------------------------------------+-----------------------------------------+--------+---------------------------
-------------------+


Re: Execute scripts / tests inside bosh-managed VMs

Dr Nic Williams
 

I don't think there is anything in bosh to get this done - Perhaps look at including consul agent and using consul exec? Or perhaps ansible?

On Mon, Jun 15, 2015 at 12:03 AM, Michael Grifalconi
<michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all, 
I'd like to run some scripts inside VMs deployed by BOSH, is it possible?
Like: with bosh IP address, credentials, deployment name and VM name, run this script, without doing it manually with bosh ssh command.
Thank you
Regards,
Michael
****************
Per destinare il 5x1000 all'Universita' degli Studi di Milano: indicare nella dichiarazione dei redditi il codice fiscale 80012650158.
http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille


Re: Execute scripts / tests inside bosh-managed VMs

Kamil Burzynski <nopik@...>
 

There is a chance that errands would do the job here?

On 15/06/15 15:20 , Dr Nic Williams wrote:
I don't think there is anything in bosh to get this done - Perhaps
look at including consul agent and using consul exec? Or perhaps ansible?




On Mon, Jun 15, 2015 at 12:03 AM, Michael Grifalconi
<michael.grifalconi(a)studenti.unimi.it
<mailto:michael.grifalconi(a)studenti.unimi.it>> wrote:

Hello all,


I'd like to run some scripts inside VMs deployed by BOSH, is it
possible?

Like: with bosh IP address, credentials, deployment name and VM
name, run this script, without doing it manually with bosh ssh
command.


Thank you

Regards,
Michael
------------------------------------------------------------------------

5xmilleUniMi
<http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille>

/*La tua firma per la sua idea. Per tutti noi*

Per destinare il 5x1000 all'Università degli Studi di Milano:
indicare nella dichiarazione dei redditi il codice fiscale
*80012650158*.

/




_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
--
Best regards from
Kamil Burzynski


Re: Execute scripts / tests inside bosh-managed VMs

Dr Nic Williams
 

Errands run their script on a new VM

On Mon, Jun 15, 2015 at 6:30 AM, Kamil Burzynski <nopik(a)data.pl> wrote:

There is a chance that errands would do the job here?
On 15/06/15 15:20 , Dr Nic Williams wrote:
I don't think there is anything in bosh to get this done - Perhaps
look at including consul agent and using consul exec? Or perhaps ansible?




On Mon, Jun 15, 2015 at 12:03 AM, Michael Grifalconi
<michael.grifalconi(a)studenti.unimi.it
<mailto:michael.grifalconi(a)studenti.unimi.it>> wrote:

Hello all,


I'd like to run some scripts inside VMs deployed by BOSH, is it
possible?

Like: with bosh IP address, credentials, deployment name and VM
name, run this script, without doing it manually with bosh ssh
command.


Thank you

Regards,
Michael
------------------------------------------------------------------------

5xmilleUniMi
<http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille>

/*La tua firma per la sua idea. Per tutti noi*

Per destinare il 5x1000 all'Università degli Studi di Milano:
indicare nella dichiarazione dei redditi il codice fiscale
*80012650158*.

/




_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
--
Best regards from
Kamil Burzynski


Re: Execute scripts / tests inside bosh-managed VMs

Kamil Burzynski <nopik@...>
 

Right!I stand corrected.

On 15/06/15 15:31 , Dr Nic Williams wrote:
Errands run their script on a new VM




On Mon, Jun 15, 2015 at 6:30 AM, Kamil Burzynski <nopik(a)data.pl
<mailto:nopik(a)data.pl>> wrote:

There is a chance that errands would do the job here?

On 15/06/15 15:20 , Dr Nic Williams wrote:
I don't think there is anything in bosh to get this done -
Perhaps look at including consul agent and using consul exec? Or
perhaps ansible?




On Mon, Jun 15, 2015 at 12:03 AM, Michael Grifalconi
<michael.grifalconi(a)studenti.unimi.it
<mailto:michael.grifalconi(a)studenti.unimi.it>> wrote:

Hello all,


I'd like to run some scripts inside VMs deployed by BOSH, is
it possible?

Like: with bosh IP address, credentials, deployment name and
VM name, run this script, without doing it manually with bosh
ssh command.


Thank you

Regards,
Michael
------------------------------------------------------------------------

5xmilleUniMi
<http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille>

/*La tua firma per la sua idea. Per tutti noi*

Per destinare il 5x1000 all'Università degli Studi di Milano:
indicare nella dichiarazione dei redditi il codice fiscale
*80012650158*.

/




_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
--
Best regards from
Kamil Burzynski




_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
--
Best regards from
Kamil Burzynski


Deploying CloudFoundry on AWS - bosh deploy returns timed out pinging

Flávio Henrique Schuindt da Silva <flavio.schuindt at gmail.com...>
 

Hi, guys!

I'm trying to deploy CF on aws and I'm following strictly this tutorial:
http://docs.cloudfoundry.org/deploying/ec2/aws_steps.html

I completed succesfully steps 1, 2 and 3, but I'm stuck on step 4. When I
run bosh deploy, I got it:

bosh deploy

Processing deployment manifest
------------------------------
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully

Deploying
------------------------------
Deployment name: `minimal-aws.yml'
Director name: `microbosh'
Are you sure you want to deploy? (type 'yes' to continue): yes

Director task 33
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done (00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

Started compiling packages
Started compiling packages >
rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4
Started compiling packages >
haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613
Started compiling packages >
buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4
Started compiling packages >
buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3
Failed compiling packages >
rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4: Timed out
pinging to 0d86a715-5035-4d2d-a7d8-62b17026d3fc after 600 seconds (00:11:04)
Failed compiling packages >
buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3: Timed out
pinging to 435b8765-8e9a-4615-8328-6f7b30bca3c0 after 600 seconds (00:11:04)
Failed compiling packages >
haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613: Timed out pinging to
4c86e063-3c06-497d-829b-12b5455679e9 after 600 seconds (00:11:04)
Failed compiling packages >
buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4: Timed out
pinging to 0a734427-f633-420e-94da-8d20ddc1d0be after 600 seconds (00:11:04)

Error 450002: Timed out pinging to 0d86a715-5035-4d2d-a7d8-62b17026d3fc
after 600 seconds

I see on ec2 dashboard that the compilation vms workers start to run, but
in a couple of minutes they suddently got terminated (the terminated ation
is made by bosh, of course). The problem here, I think, is that the bosh
director aren't communicating properly with compilation vms and so they got
a timeout error. But I followed exactly the same steps from tutorial.

Also, I checked all the network config on aws console and nothing seems to
be wrong. How can i solve it? Thanks in advance, guys!


Re: Job is not running after update - agent/monit race issue?

Danny Berger <dpb587@...>
 

Hi again - I still haven't been able to track down why the monit processes
are sometimes not restarted. Does anybody have ideas for other things I can
try or do to further debug this issue?

Any help is appreciated - thanks!

Danny

On Thu, Jun 4, 2015 at 5:31 PM, Danny Berger <dpb587(a)gmail.com> wrote:

Frequently when doing a deploy (happens in multiple deployments) a job
will randomly fail with "job/0 is not running after update" for no logical
reason. I can just rerun `bosh deploy` and it will succeed on that job and
move onto the next job for update (which might also fail). Alternatively, I
can SSH in and monit will show one or more processes as "not monitored",
yet if I run `monit start all` it does start the remaining processes
without fail. Looking into this behavior more today, I think it might be
some strange interaction between bosh-agent and monit.

In a good job, everything updates/restarts as expected (logs here [1]),
but on a problem job, I've noticed a key difference: monit receives `start
service` very early [2] but never actually invokes the start action for it.
In the bad log [3] you'll see there are only 3 "start: " and "start action
done" messages, yet there are 4 "start service" messages. In the good job
logs, there would always be 4 of each of those messages. Here is a second
example [4] where two services fail to start.

In all cases that I'm seeing, if the "start service" call(s) are logged
before those final "monit HTTP server stopped/started" occur, then they
appear to get lost and the start command never run. Theorizing... is it
possible that bosh-agent is asynchronously sending start commands alongside
SIGHUP? Or perhaps that monit is randomly, strangely slow to process the
SIGHUP vs HTTP request? Or perhaps those monit starts are just sent to
quickly after a reload?

These logs were from a deployment using
bosh-aws-xen-ubuntu-trusty-go_agent/2798 with the logsearch +
logsearch-shipper releases. Sorry the stemcell isn't newer - looking
through bosh-agent and bosh commit logs though I don't see messages which
reference a fix for this sort of thing, so hopefully the log details are
still relevant. I don't think it's release or deployment specific given the
log message, but I don't have much experience deploying many other things
to know for sure.

If anybody has any insight into this strangeness, I'd definitely
appreciate it. The while loop workaround we've been using works, but it's
not so great for automation.

Thanks!

Danny

[1]
https://gist.github.com/dpb587/ad44bb34aabab1c4a98e#file-monit-good-summary-log
[2]
https://gist.github.com/dpb587/ad44bb34aabab1c4a98e#file-monit-bad-log-L44
[3] https://gist.github.com/dpb587/ad44bb34aabab1c4a98e#file-monit-bad-log
[4]
https://gist.github.com/dpb587/ad44bb34aabab1c4a98e#file-monit-bad2-log


--
Danny Berger
http://dpb587.me
--
Danny Berger
http://dpb587.me


Re: Execute scripts / tests inside bosh-managed VMs

Dmitriy Kalinin
 

Can you give us a bit more details about what you are trying to do?

On Mon, Jun 15, 2015 at 6:51 AM, Kamil Burzynski <nopik(a)data.pl> wrote:

Right! I stand corrected.


On 15/06/15 15:31 , Dr Nic Williams wrote:

Errands run their script on a new VM




On Mon, Jun 15, 2015 at 6:30 AM, Kamil Burzynski <nopik(a)data.pl> wrote:

There is a chance that errands would do the job here?

On 15/06/15 15:20 , Dr Nic Williams wrote:

I don't think there is anything in bosh to get this done - Perhaps look
at including consul agent and using consul exec? Or perhaps ansible?




On Mon, Jun 15, 2015 at 12:03 AM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Hello all,

I'd like to run some scripts inside VMs deployed by BOSH, is it
possible?

Like: with bosh IP address, credentials, deployment name and VM name,
run this script, without doing it manually with bosh ssh command.


Thank you

Regards,
Michael
------------------------------

[image: 5xmilleUniMi]
<http://www.unimi.it/13084.htm?utm_source=firmaMail&utm_medium=email&utm_content=linkFirmaEmail&utm_campaign=5xmille>


* La tua firma per la sua idea. Per tutti noi Per destinare il 5x1000
all'Università degli Studi di Milano: indicare nella dichiarazione dei
redditi il codice fiscale 80012650158. *


_______________________________________________
cf-bosh mailing listcf-bosh(a)lists.cloudfoundry.orghttps://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


--
Best regards from
Kamil Burzynski


_______________________________________________
cf-bosh mailing listcf-bosh(a)lists.cloudfoundry.orghttps://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


--
Best regards from
Kamil Burzynski


_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: Deploying CloudFoundry on AWS - bosh deploy returns timed out pinging

James Bayer
 

sounds like some sort of firewall or security groups issue, where the VMs
that are created are not able to talk to the BOSH Director. did you perform
this step: http://bosh.io/docs/deploy-microbosh-to-aws.html#create-security

On Mon, Jun 15, 2015 at 6:59 AM, Flávio Henrique Schuindt da Silva <
flavio.schuindt(a)gmail.com> wrote:

Hi, guys!

I'm trying to deploy CF on aws and I'm following strictly this tutorial:
http://docs.cloudfoundry.org/deploying/ec2/aws_steps.html

I completed succesfully steps 1, 2 and 3, but I'm stuck on step 4. When I
run bosh deploy, I got it:

bosh deploy

Processing deployment manifest
------------------------------
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully

Deploying
------------------------------
Deployment name: `minimal-aws.yml'
Director name: `microbosh'
Are you sure you want to deploy? (type 'yes' to continue): yes

Director task 33
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done (00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)

Started compiling packages
Started compiling packages >
rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4
Started compiling packages >
haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613
Started compiling packages >
buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4
Started compiling packages >
buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3
Failed compiling packages >
rootfs_cflinuxfs2/3e1f990a4a77b3daf012fdb278ece231150182b4: Timed out
pinging to 0d86a715-5035-4d2d-a7d8-62b17026d3fc after 600 seconds (00:11:04)
Failed compiling packages >
buildpack_staticfile/f6c501e6e86abbd0620074d67c2aac2e49225ee3: Timed out
pinging to 435b8765-8e9a-4615-8328-6f7b30bca3c0 after 600 seconds (00:11:04)
Failed compiling packages >
haproxy/630ad6d6e1d3cab4547ce104f3019b483f354613: Timed out pinging to
4c86e063-3c06-497d-829b-12b5455679e9 after 600 seconds (00:11:04)
Failed compiling packages >
buildpack_binary/816fc3f418dd9e6f3fd8a1dd0de4812c53a729d4: Timed out
pinging to 0a734427-f633-420e-94da-8d20ddc1d0be after 600 seconds (00:11:04)

Error 450002: Timed out pinging to 0d86a715-5035-4d2d-a7d8-62b17026d3fc
after 600 seconds

I see on ec2 dashboard that the compilation vms workers start to run, but
in a couple of minutes they suddently got terminated (the terminated ation
is made by bosh, of course). The problem here, I think, is that the bosh
director aren't communicating properly with compilation vms and so they got
a timeout error. But I followed exactly the same steps from tutorial.

Also, I checked all the network config on aws console and nothing seems to
be wrong. How can i solve it? Thanks in advance, guys!

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


--
Thank you,

James Bayer


`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


Re: `bosh upload release` times out creating packages

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,
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
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: `bosh upload release` times out creating packages

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?

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


Re: `bosh upload release` times out creating packages

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,
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
_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: `bosh upload release` times out creating packages

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.

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


Re: `bosh upload release` times out creating packages

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.

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


Re: cf-stub.yml example with minimum or required info

CF Runtime
 

Hi Ahmed,

This property is coming from the "templates/cf-lamb.yml" within cf-release.
You are able to overwrite this property in your stub like so:

meta:
environment: [name-of-environment]

Hope this helps,
Dan && James, CF Runtime Team

On Sun, Jun 14, 2015 at 7:13 PM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com>
wrote:

What should be the value then, it is generated by spiff?

should I place this in cf-stub.yml under properties to overwrite what
spiff doing as following:

properties:
metron_agent:
deployment: <???>

I found this link talking about same issue:
https://github.com/cloudfoundry/bosh-lite/issues/265 but could not find
an answer

Thanks Gwenn



From: Gwenn Etourneau <getourneau(a)pivotal.io>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Sunday, June 14, 2015 at 6:58 PM
To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info

Seems this could not be null in deployment.yml

metron_agent:
deployment: null

On Mon, Jun 15, 2015 at 10:50 AM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com>
wrote:

Both cf-stub.yml and the spiff generated cf-deployment.yml are attached.

I noticed in cf-deployment.yml a section called “- default_networks:”
inserted between jobs, does this look normal?

Note: I did not edit cf-deployment, it is what I get from spiff.

Environment info:
Ubuntu 14

BOSH 1.2977.0

cf version 6.11.3-cebadc9-2015-05-20T19:00:58+00:00

spiff version 1.0.6

ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
vSphere 5.5


#bosh status

Config

/root/.bosh_config


Director

Name bosh2

URL https://10.195.166.12:25555

Version 1.2976.0 (00000000)

User admin

UUID b9a1bf7b-952f-48e1-a496-f6543d7a782c

CPI vsphere

dns enabled (domain_name: bosh)

compiled_package_cache disabled

snapshots enabled


Deployment

Manifest /root/deployment/cf-deployment.yml

#bosh releases


+------+------------+-------------+

| Name | Versions | Commit Hash |

+------+------------+-------------+

| cf | 211+dev.1* | 2121dc64+ |

+------+------------+-------------+

(*) Currently deployed

(+) Uncommitted changes




Thank you!

From: Gwenn Etourneau <getourneau(a)pivotal.io>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Sunday, June 14, 2015 at 5:35 PM
To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info

Please show us you manifest, seems something is missing.



On Mon, Jun 15, 2015 at 4:08 AM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com>
wrote:

Hi Joseph,

Thank you! I changed to using two different networks and now "bosh
deploy” works and all VMs are deployed successfully, but looks like there
is a binding configuration error:

Binding configuration. Failed: Error filling in template
`metron_agent.json.erb' for `ha_proxy_z1/0' (line 5: Can't find property
`["metron_agent.deployment"]') (00:00:00)


Error 100: Error filling in template `metron_agent.json.erb' for
`ha_proxy_z1/0' (line 5: Can't find property `["metron_agent.deployment"]')


Also tried to connect using CF and could not connect:

root(a)cloudfoundry:~/deployment# cf api --skip-ssl-validation
foundry-appx.domain.com

Setting api endpoint to *foundry-app.domain.com
<http://foundry-app.domain.com>*...

*FAILED*
Error performing request: Get http://foundry-appx.domain.com/v2/info:
dial tcp x.x.166.18:80: connection refused


Full run console log:

root(a)cloudfoundry:~/deployment# bosh deploy


Processing deployment manifest

------------------------------

Getting deployment properties from director...

Unable to get properties list from director, trying without it...

Compiling deployment manifest...

Cannot get current deployment information from director, possibly a new
deployment

Please review all changes carefully


Deploying

---------

Deployment name: `cf-deployment.yml'

Director name: `bosh2'

Are you sure you want to deploy? (type 'yes' to continue): yes


Director task 172

Started unknown

Started unknown > Binding deployment. Done (00:00:00)


Started preparing deployment

Started preparing deployment > Binding releases. Done (00:00:00)

Started preparing deployment > Binding existing deployment. Done
(00:00:00)

Started preparing deployment > Binding resource pools. Done (00:00:00)

Started preparing deployment > Binding stemcells. Done (00:00:00)

Started preparing deployment > Binding templates. Done (00:00:00)

Started preparing deployment > Binding properties. Done (00:00:00)

Started preparing deployment > Binding unallocated VMs. Done
(00:00:00)

Started preparing deployment > Binding instance networks. Done
(00:00:00)


Started preparing package compilation > Finding packages to compile.
Done (00:00:00)


Started preparing dns > Binding DNS. Done (00:00:00)


Started creating bound missing vms

Started creating bound missing vms > small_z1/0

Started creating bound missing vms > small_z1/1

Started creating bound missing vms > small_z1/2

Started creating bound missing vms > small_z2/0

Started creating bound missing vms > small_z2/1

Started creating bound missing vms > medium_z1/0

Started creating bound missing vms > medium_z1/1

Started creating bound missing vms > medium_z1/2

Started creating bound missing vms > medium_z1/3

Started creating bound missing vms > medium_z1/4

Started creating bound missing vms > medium_z1/5

Started creating bound missing vms > medium_z1/6

Started creating bound missing vms > medium_z1/7

Started creating bound missing vms > medium_z1/8

Started creating bound missing vms > medium_z2/0

Started creating bound missing vms > medium_z2/1

Started creating bound missing vms > medium_z2/2

Started creating bound missing vms > medium_z2/3

Started creating bound missing vms > medium_z2/4

Started creating bound missing vms > large_z1/0

Started creating bound missing vms > large_z2/0

Started creating bound missing vms > runner_z1/0

Started creating bound missing vms > runner_z2/0

Started creating bound missing vms > router_z1/0

Started creating bound missing vms > router_z1/1

Started creating bound missing vms > router_z2/0

Done creating bound missing vms > medium_z1/0 (00:00:30)

Done creating bound missing vms > medium_z1/5 (00:00:32)

Done creating bound missing vms > small_z2/1 (00:00:34)

Done creating bound missing vms > medium_z1/2 (00:00:34)

Done creating bound missing vms > medium_z2/4 (00:00:35)

Done creating bound missing vms > medium_z1/1 (00:00:45)

Done creating bound missing vms > medium_z1/7 (00:00:45)

Done creating bound missing vms > small_z1/0 (00:00:46)

Done creating bound missing vms > router_z1/1 (00:00:47)

Done creating bound missing vms > medium_z2/2 (00:00:49)

Done creating bound missing vms > medium_z2/3 (00:00:49)

Done creating bound missing vms > large_z2/0 (00:00:51)

Done creating bound missing vms > medium_z1/4 (00:00:52)

Done creating bound missing vms > router_z1/0 (00:00:52)

Done creating bound missing vms > small_z1/1 (00:00:55)

Done creating bound missing vms > router_z2/0 (00:00:55)

Done creating bound missing vms > small_z2/0 (00:00:59)

Done creating bound missing vms > large_z1/0 (00:00:59)

Done creating bound missing vms > medium_z2/1 (00:01:00)

Done creating bound missing vms > medium_z1/6 (00:01:00)

Done creating bound missing vms > medium_z1/3 (00:01:01)

Done creating bound missing vms > medium_z1/8 (00:01:01)

Done creating bound missing vms > medium_z2/0 (00:01:01)

Done creating bound missing vms > runner_z2/0 (00:01:02)

Done creating bound missing vms > runner_z1/0 (00:01:02)

Done creating bound missing vms > small_z1/2 (00:01:03)

Done creating bound missing vms (00:01:03)


Started binding instance vms

Started binding instance vms > ha_proxy_z1/0

Started binding instance vms > nats_z1/0

Started binding instance vms > nats_z2/0

Started binding instance vms > etcd_z1/0

Started binding instance vms > etcd_z1/1

Started binding instance vms > etcd_z2/0

Started binding instance vms > stats_z1/0

Started binding instance vms > nfs_z1/0

Started binding instance vms > postgres_z1/0

Started binding instance vms > uaa_z1/0

Started binding instance vms > uaa_z2/0

Started binding instance vms > api_z1/0

Started binding instance vms > api_z2/0

Started binding instance vms > clock_global/0

Started binding instance vms > api_worker_z1/0

Started binding instance vms > api_worker_z2/0

Started binding instance vms > hm9000_z1/0

Started binding instance vms > hm9000_z2/0

Started binding instance vms > runner_z1/0

Started binding instance vms > runner_z2/0

Started binding instance vms > loggregator_z1/0

Started binding instance vms > loggregator_z2/0

Started binding instance vms > loggregator_trafficcontroller_z1/0

Started binding instance vms > router_z1/0

Started binding instance vms > loggregator_trafficcontroller_z2/0

Started binding instance vms > router_z2/0

Done binding instance vms > etcd_z2/0 (00:00:00)

Done binding instance vms > ha_proxy_z1/0 (00:00:00)

Done binding instance vms > nats_z1/0 (00:00:00)

Done binding instance vms > nats_z2/0 (00:00:00)

Done binding instance vms > clock_global/0 (00:00:00)

Done binding instance vms > etcd_z1/0 (00:00:00)

Done binding instance vms > uaa_z1/0 (00:00:00)

Done binding instance vms > nfs_z1/0 (00:00:00)

Done binding instance vms > postgres_z1/0 (00:00:00)

Done binding instance vms > api_z2/0 (00:00:00)

Done binding instance vms > api_z1/0 (00:00:00)

Done binding instance vms > uaa_z2/0 (00:00:00)

Done binding instance vms > etcd_z1/1 (00:00:00)

Done binding instance vms > stats_z1/0 (00:00:00)

Done binding instance vms > hm9000_z2/0 (00:00:00)

Done binding instance vms > hm9000_z1/0 (00:00:00)

Done binding instance vms > runner_z1/0 (00:00:00)

Done binding instance vms > loggregator_z1/0 (00:00:00)

Done binding instance vms > loggregator_z2/0 (00:00:00)

Done binding instance vms > loggregator_trafficcontroller_z1/0
(00:00:00)

Done binding instance vms > loggregator_trafficcontroller_z2/0
(00:00:00)

Done binding instance vms > runner_z2/0 (00:00:00)

Done binding instance vms > router_z2/0 (00:00:00)

Done binding instance vms > router_z1/0 (00:00:00)

Done binding instance vms > api_worker_z1/0 (00:00:01)

Done binding instance vms > api_worker_z2/0 (00:00:01)

Done binding instance vms (00:00:01)


Started preparing configuration > Binding configuration. Failed: Error
filling in template `metron_agent.json.erb' for `ha_proxy_z1/0' (line 5:
Can't find property `["metron_agent.deployment"]') (00:00:00)


Error 100: Error filling in template `metron_agent.json.erb' for
`ha_proxy_z1/0' (line 5: Can't find property `["metron_agent.deployment"]')


Task 172 error


For a more detailed error report, run: bosh task 172 --debug

root(a)cloudfoundry:~/deployment# bosh cck

Performing cloud check...


Processing deployment manifest

------------------------------


Director task 173

Started scanning 26 vms

Started scanning 26 vms > Checking VM states. Done (00:00:00)

Started scanning 26 vms > 26 OK, 0 unresponsive, 0 missing, 0
unbound, 0 out of sync. Done (00:00:00)

Done scanning 26 vms (00:00:00)


Started scanning 0 persistent disks

Started scanning 0 persistent disks > Looking for inactive disks.
Done (00:00:00)

Started scanning 0 persistent disks > 0 OK, 0 missing, 0 inactive, 0
mount-info mismatch. Done (00:00:00)

Done scanning 0 persistent disks (00:00:00)


Task 173 done


Started2015-06-14 18:34:55 UTC

Finished2015-06-14 18:34:55 UTC

Duration00:00:00


Scan is complete, checking if any problems found...

No problems found

root(a)cloudfoundry:~/deployment# cf api --skip-ssl-validation
foundry-appx.domain.com

Setting api endpoint to *foundry-app.doamin.com
<http://foundry-app.doamin.com>*...

*FAILED*

Error performing request: Get http://foundry-appx.domain.com/v2/info:
dial tcp x.x.166.18:80: connection refused




Note: the cluster is done inside a lab environment with proxy, did not
configure CF with proxy and not sure if I need to do something specific.



Thanks!




From: CF Runtime <cfruntime(a)gmail.com>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Friday, June 12, 2015 at 5:39 PM
To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required info

Anything in the network section that is not static or reserved, BOSH
will assume it can use for any other instances in that zone. Because your
two subnets overlap, and you have not partitioned it off using the reserved
sections, BOSH is using that IP for something in the other zone.

Normally, if you only have a single network, it is easier to just set
the instance count for jobs in the second zone to zero, and scale up any in
the first zone to multiple if you want to have redundancy.

Joseph Palermo
CF Runtime Team

On Fri, Jun 12, 2015 at 1:29 PM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com>
wrote:

Sorry I did not see this reply from Gwenn Etourneau.

After “bosh cck”, it found 6 problems and then I tried option 2 to
reboot and also tried option 3 to recreate VM, none of them fixed the
issue, but I noticed the problematic VMs are using duplicate IPs, my
network section in the manifest has 2 networks (cf1 and cf2) and there is
no overlab, see network section below.

For example the VM router_z1/0
(vm-c36efd49-7ac7-4b90-9779-b5192408e4a6) got the ip 10.195.166.110,
and another VM from same deployment (
vm-2b532db0-36df-433d-8132-89c76a9c81c3) got the same ip 10.195.166.110

I tried also removing the section “jobs" and go with defaults which
is generated by spiff and run into same issue, do I have
to statically assign IP address to each job?


M-20JW:cf-release ahmeali$ bosh cck
Performing cloud check...

Processing deployment manifest
------------------------------

Director task 141
Started scanning 26 vms
Started scanning 26 vms > Checking VM states. Done (00:00:10)
Started scanning 26 vms > 20 OK, 6 unresponsive, 0 missing, 0
unbound, 0 out of sync. Done (00:00:00)
Done scanning 26 vms (00:00:10)

Started scanning 0 persistent disks
Started scanning 0 persistent disks > Looking for inactive disks.
Done (00:00:00)
Started scanning 0 persistent disks > 0 OK, 0 missing, 0 inactive, 0
mount-info mismatch. Done (00:00:00)
Done scanning 0 persistent disks (00:00:00)

Task 141 done

Started 2015-06-12 20:03:17 UTC
Finished 2015-06-12 20:03:27 UTC
Duration 00:00:10

Scan is complete, checking if any problems found...

Found 6 problems

Problem 1 of 6: Unknown VM (vm-e4da0933-52ba-473f-903d-a9ee09d1671f)
is not responding.
1. Ignore problem
2. Reboot VM
3. Recreate VM using last known apply spec
4. Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]: 2

Problem 2 of 6: hm9000_z1/0 (vm-5ea4c90d-247e-43ad-a189-ff4d2d781854)
is not responding.
1. Ignore problem
2. Reboot VM
3. Recreate VM using last known apply spec
4. Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]: 2

Problem 3 of 6: router_z1/0 (vm-c36efd49-7ac7-4b90-9779-b5192408e4a6)
is not responding.
1. Ignore problem
2. Reboot VM
3. Recreate VM using last known apply spec
4. Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]: 2

Problem 4 of 6: nfs_z1/0 (vm-868e2bb9-ac61-49f0-86fb-38d5c338201b) is
not responding.
1. Ignore problem
2. Reboot VM
3. Recreate VM using last known apply spec
4. Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]: 2

Problem 5 of 6: router_z2/0 (vm-773e83ee-c97f-4aa4-b163-d09a703a4678)
is not responding.
1. Ignore problem
2. Reboot VM
3. Recreate VM using last known apply spec
4. Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]: 2

Problem 6 of 6: ha_proxy_z1/0
(vm-643f3c80-93cb-4ccf-9239-1f85a407a317) is not responding.
1. Ignore problem
2. Reboot VM
3. Recreate VM using last known apply spec
4. Delete VM reference (DANGEROUS!)
Please choose a resolution [1 - 4]: 2

Below is the list of resolutions you've provided
Please make sure everything is fine and confirm your changes

1. Unknown VM (vm-e4da0933-52ba-473f-903d-a9ee09d1671f) is not
responding
Reboot VM

2. hm9000_z1/0 (vm-5ea4c90d-247e-43ad-a189-ff4d2d781854) is not
responding
Reboot VM

3. router_z1/0 (vm-c36efd49-7ac7-4b90-9779-b5192408e4a6) is not
responding
Reboot VM

4. nfs_z1/0 (vm-868e2bb9-ac61-49f0-86fb-38d5c338201b) is not
responding
Reboot VM

5. router_z2/0 (vm-773e83ee-c97f-4aa4-b163-d09a703a4678) is not
responding
Reboot VM

6. ha_proxy_z1/0 (vm-643f3c80-93cb-4ccf-9239-1f85a407a317) is not
responding
Reboot VM

Apply resolutions? (type 'yes' to continue): yes
Applying resolutions...

Director task 142
Started applying problem resolutions
Started applying problem resolutions > unresponsive_agent 154: Reboot
VM. Failed: Agent is responding now, skipping resolution (00:00:00)
Started applying problem resolutions > unresponsive_agent 184: Reboot
VM. Failed: Agent is responding now, skipping resolution (00:00:00)
Started applying problem resolutions > unresponsive_agent 177: Reboot
VM. Done (00:00:30)
Started applying problem resolutions > unresponsive_agent 179: Reboot
VM. Failed: Agent is responding now, skipping resolution (00:00:00)
Started applying problem resolutions > unresponsive_agent 185: Reboot
VM. Done (00:00:11)
Started applying problem resolutions > unresponsive_agent 180: Reboot
VM. Done (00:00:29)
Failed applying problem resolutions (00:01:10)

Task 142 done

Started 2015-06-12 20:04:01 UTC
Finished 2015-06-12 20:05:11 UTC
Duration 00:01:10
Cloudcheck is finished


Network section in cf-stub.yml


---
name: cf
director_uuid: b9a1bf7b-952f-48e1-a496-f6543d7a782c

releases:
- {name: cf, version: latest}

networks:

- name: cf1

subnets:

- range: 10.195.166.0/23

gateway: 10.195.166.1

static:

* - 10.195.166.105 - 10.195.166.135*

reserved:

# .1 is special

- 10.195.166.2 - 10.195.166.104

- 10.195.166.188 - 10.195.166.254

# .255 is special

dns: [10.166.168.183]

cloud_properties:

name: '10.195.166.x'

- name: cf2

subnets:

- range: 10.195.166.0/23

gateway: 10.195.166.1

static:

*- 10.195.166.136 - 10.195.166.166*

reserved:

# .1 is special

- 10.195.166.2 - 10.195.166.104

- 10.195.166.188 - 10.195.166.254

# .255 is special

dns: [10.166.168.183]

cloud_properties:

name: '10.195.166.x'


Thank you


From: Gwenn Etourneau <getourneau(a)pivotal.io>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Monday, June 8, 2015 at 6:16 PM

To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required
info

Try to make bosh cck before bosh deploy.

On Tue, Jun 9, 2015 at 3:43 AM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com>
wrote:

I was able to fix this by copying from the generated
cf-deployment.yml and use it in cf-stub.yml after changing cf release and
jobs section.


Now "bosh deploy" works but not complete, running into an issue I
think has to do with jobs/nodes misconfigured, not sure what are the list
of jobs/nodes I need to include and the properties of each one, any idea
where I can find information about the list of jobs/nodes and properties
for each such as templates/network ..etc?

"Bosh vms” shows some Vms in “unresponsive agent” and unknown job.


+------------------------------------+--------------------+---------------+----------------+

| Job/index | State | Resource
Pool | IPs |


+------------------------------------+--------------------+---------------+----------------+

| unknown/unknown | unresponsive agent |
| |

| unknown/unknown | unresponsive agent |
| |

| unknown/unknown | unresponsive agent |
| |

| unknown/unknown | unresponsive agent |
| |

| unknown/unknown | unresponsive agent |
| |

| unknown/unknown | unresponsive agent |
| |

| unknown/unknown | running | medium_z1
| 10.195.166.106 |

| unknown/unknown | running | router_z1
| 10.195.166.108 |

| unknown/unknown | running | small_z1
| 10.195.166.141 |

| api_z1/0 | running | large_z1
| 10.195.166.139 |

| api_z2/0 | running | large_z2
| 10.195.166.107 |

| clock_global/0 | running | medium_z1
| 10.195.166.140 |

| consul_z1/0 | running | medium_z1
| 10.195.166.122 |

| consul_z2/0 | running | medium_z2
| 10.195.166.153 |

| etcd_z1/0 | running | medium_z1
| 10.195.166.119 |

| etcd_z1/1 | running | medium_z1
| 10.195.166.120 |

| etcd_z2/0 | running | medium_z2
| 10.195.166.149 |

| hm9000_z1/0 | running | medium_z1
| 10.195.166.142 |

| hm9000_z2/0 | running | medium_z2
| 10.195.166.109 |

| loggregator_trafficcontroller_z1/0 | running | small_z1
| 10.195.166.145 |

| loggregator_trafficcontroller_z2/0 | running | small_z2
| 10.195.166.112 |

| loggregator_z1/0 | running | medium_z1
| 10.195.166.144 |

| loggregator_z2/0 | running | medium_z2
| 10.195.166.111 |

| login_z1/0 | running | medium_z1
| 10.195.166.138 |

| postgres_z1/0 | running | medium_z1
| 10.195.166.117 |

| routing_api_z1/0 | running | medium_z1
| 10.195.166.121 |

| routing_api_z2/0 | running | medium_z2
| 10.195.166.152 |

| runner_z1/0 | running | runner_z1
| 10.195.166.143 |

| runner_z2/0 | running | runner_z2
| 10.195.166.110 |

| stats_z1/0 | running | small_z1
| 10.195.166.136 |

| uaa_z1/0 | running | medium_z1
| 10.195.166.137 |

| uaa_z2/0 | running | medium_z2
| 10.195.166.105 |


+------------------------------------+--------------------+---------------+----------------+


VMs total: 32


Started preparing deployment > Binding existing deployment. Failed:
Timed out sending `get_state' to eabc55f7-b402-42f7-85b5-e3732306b813 after
45 seconds (00:02:15)
Error 450002: Timed out sending `get_state' to
eabc55f7-b402-42f7-85b5-e3732306b813 after 45 seconds


Thanks
Ali

From: AHMED ALI <ahmeali(a)cisco.com>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Friday, June 5, 2015 at 10:45 AM

To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required
info

That fixed the error, thank you!

And run into another error :)

M-20JW:cf-release ali00$ bosh deployment cf-deployment.yml
Deployment set to
`/Users/ali00/deployments/cf-release/cf-deployment.yml'
M-20JW:cf-release ali00$ ./generate_deployment_manifest vsphere
cf-stub.yml > cf-deployment.yml
M-20JW:cf-release ali00$ bosh deploy

Processing deployment manifest
------------------------------
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully

Deploying
---------
Deployment name: `cf-deployment.yml'
Director name: `bosh2'
Are you sure you want to deploy? (type 'yes' to continue): yes

Director task 38
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Error 140002: Template `consul_agent' (job `consul_z1') references
an unknown release `cf'

Task 38 error

For a more detailed error report, run: bosh task 38 --debug
M-20JW:cf-release ali00$


How can construct the section in cf-stub to provide correct cf
release which I think should be cf-210 in my case (not sure)?


Modified networks part in my cf-stub.yml
-------------------------------------------------------
releases:
- name: cf-210
version: latest

networks:

- name: cf1

subnets:

- range: 10.195.166.0/23

gateway: 10.195.166.1

static:

- 10.195.166.104 - 10.195.166.125

reserved:

# .1 is special

- 10.195.166.2 - 10.195.166.101

- 10.195.166.147 - 10.195.166.254

# .255 is special

dns: [10.166.168.183]

cloud_properties:

name: '10.195.166.x'

- name: cf2

subnets:

- range: 10.195.166.0/23

gateway: 10.195.166.1

static:

- 10.195.166.126 - 10.195.166.146

reserved:

# .1 is special

- 10.195.166.2 - 10.195.166.101

- 10.195.166.147 - 10.195.166.254

# .255 is special

dns: [10.166.168.183]

cloud_properties:

name: '10.195.166.x'


------------------------------------------------




Thanks
Ali


From: CF Runtime <cfruntime(a)gmail.com>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Friday, June 5, 2015 at 10:11 AM
To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required
info

Hi Ahmed,

It looks like you haven't allocated enough IPs in your network. The
line for reserved IPs "10.166.166.104 - 10.166.166.115" should be
increased to have at least 19 IPs. You'll need to decrease the number of
reserved addresses as well in order to increase the number of available IPs
in your network. We recommend "10.166.166.104 - 10.166.166.123" for
available IPs and "10.166.166.124 - 10.194.167.254" for your reserved
range. If you're tracking our current develop branch and not the final
releases you should look in cf-release/spec/fixtures/vsphere/cf-stub.yml
for the stub that we use to do our vsphere acceptance tests.

Best,
Zachary Auerbach + Dan Lavine CF Runtime Team

On Thu, Jun 4, 2015 at 2:18 PM, Ahmed Ali (ahmeali) <ahmeali(a)cisco.com
wrote:
Thanks Joseph for your help, please see the error below:

20JXXW:cf-release ali00$ ./generate_deployment_manifest vsphere
cf-stub.yml > cf-deployment.yml
2015/06/04 13:34:50 error generating manifest: unresolved nodes:
(( static_ips(12) )) in
./templates/cf-infrastructure-vsphere.yml
jobs.[5].networks.[0].static_ips
(( static_ips(16) )) in
./templates/cf-infrastructure-vsphere.yml
jobs.[8].networks.[0].static_ips
(( static_ips(14, 15) )) in
./templates/cf-infrastructure-vsphere.yml
jobs.[15].networks.[0].static_ips
(( static_ips(17, 18, 19) )) in
./templates/cf-infrastructure-vsphere.yml
jobs.[17].networks.[0].static_ips
(( jobs.postgres_z1.networks.cf1.static_ips.[0] )) in
dynaml properties.databases.address
(( properties.databases.address )) in dynaml
properties.ccdb.address
(( properties.databases.address )) in dynaml
properties.uaadb.address
M-2XX0JW:cf-release ali00$


I do not want to bug cf-bosh alias with every error I run into so
my ask is to find a sample of cf-stub.yml with all minimum required values,
Im sure Im missing a lot :), the sample online here
http://docs.cloudfoundry.org/deploying/cf-stub-vsphere.html, when I
first run it I got an error regarding “Error 40001: Required property
`range' was not specified in object”, then after I added “range” property I
got the error above.

Im looking for building a POC CF with minimum effort, do have one
network (10.166.166.0/23) and vSphere 5.x, I want to use it for both
CF networks (cf1 and cf2), not sure how many Ips I need on each network,
and if I have to specify nodes spec and vsphere info in cf-stub since I do
not see section for it?

I also tried bosh-lite and it worked fine on Ubuntu 14.

Here is my cf-stub.yml in case you want to have a look


# The following line helps maintain current documentation at
http://docs.cloudfoundry.org.
# code_snippet cf-stub-vsphere start
---
name: cloudfoundry
director_uuid: b9a1bf7b-952f-48e1-a496-f6543d7a782c

releases:
- name: cf-210
version: latest

networks:

- name: cf1

subnets:

- range: 10.166.166.0/23

gateway: 10.195.76.1

static:

- 10.166.166.104 - 10.166.166.115

reserved:

# .1 is special

- 10.166.166.2 - 10.166.166.101

- 10.166.166.120 - 10.194.167.254

# .255 is special

dns: [10.166.168.183]

cloud_properties:

name: '10.166.166.x'

- name: cf2

subnets:

- range: 10.166.166.0/23

gateway: 10.166.166.1

static:

- 10.166.166.120 - 10.166.166.140

reserved:

# .1 is special

- 10.166.166.2 - 10.166.166.101

- 10.166.166.120 - 10.195.167.254

# .255 is special

dns: [10.166.168.183]

cloud_properties:

name: '10.166.166.x'

jobs:
ha_proxy_z1:
properties:
ha_proxy:
disable_http: true
properties:
cc:
droplets:
droplet_directory_key: the_key
buildpacks:
buildpack_directory_key: bd_key
staging_upload_user: username
staging_upload_password: password
bulk_api_password: password
db_encryption_key: the_key
dea_next:
disk_mb: 2048
memory_mb: 1024
loggregator_endpoint:
shared_secret: loggregator_endpoint_secret
nats:
user: nats_user
password: nats_password
router:
enable_ssl: true
ssl_cert: |
-----BEGIN CERTIFICATE-----
MIIDBjCCAe4CCQCz3nn1SWrDdTANBgkqhkiG9w0BAQUFADBFMQswCQYDVQQGEwJB
VTETMBEGA1UECBMKU29tZS1TdGF0ZTEhMB8GA1UEChMYSW50ZXJuZXQgV2lkZ2l0
cyBQdHkgTHRkMB4XDTE1MDMwMzE4NTMyNloXDTE2MDMwMjE4NTMyNlowRTELMAkG
A1UEBhMCQVUxEzARBgNVBAgTClNvbWUtU3RhdGUxITAfBgNVBAoTGEludGVybmV0
IFdpZGdpdHMgUHR5IEx0ZDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AKtTK9xq/ycRO3fWbk1abunYf9CY6sl0Wlqm9UPMkI4j0itY2OyGyn1YuCCiEdM3
b8guGSWB0XSL5PBq33e7ioiaH98UEe+Ai+TBxnJsro5WQ/TMywzRDhZ4E7gxDBav
88ZY+y7ts0HznfxqEIn0Gu/UK+s6ajYcIy7d9L988+hA3K1FSdes8MavXhrI4xA1
fY21gESfFkD4SsqvrkISC012pa7oVw1f94slIVcAG+l9MMAkatBGxgWAQO6kxk5o
oH1Z5q2m0afeQBfFqzu5lCITLfgTWCUZUmbF6UpRhmD850/LqNtryAPrLLqXxdig
OHiWqvFpCusOu/4z1uGC5xECAwEAATANBgkqhkiG9w0BAQUFAAOCAQEAV5RAFVQy
8Krs5c9ebYRseXO6czL9/Rfrt/weiC1XLcDkE2i2yYsBXazMYr58o4hACJwe2hoC
bihBZ9XnVpASEYHDLwDj3zxFP/bTuKs7tLhP7wz0lo8i6k5VSPAGBq2kjc/cO9a3
TMmLPks/Xm42MCSWGDnCEX1854B3+JK3CNEGqSY7FYXU4W9pZtHPZ3gBoy0ymSpg
mpleiY1Tbn5I2X7vviMW7jeviB5ivkZaXtObjyM3vtPLB+ILpa15ZhDSE5o71sjA
jXqrE1n5o/GXHX+1M8v3aJc30Az7QAqWohW/tw5SoiSmVQZWd7gFht9vSzaH2WgO
LwcpBC7+cUJEww==
-----END CERTIFICATE-----
ssl_key: |
-----BEGIN RSA PRIVATE KEY-----
MIIEpAIBAAKCAQEAq1Mr3Gr/JxE7d9ZuTVpu6dh/0JjqyXRaWqb1Q8yQjiPSK1jY
7IbKfVi4IKIR0zdvyC4ZJYHRdIvk8Grfd7uKiJof3xQR74CL5MHGcmyujlZD9MzL
DNEOFngTuDEMFq/zxlj7Lu2zQfOd/GoQifQa79Qr6zpqNhwjLt30v3zz6EDcrUVJ
16zwxq9eGsjjEDV9jbWARJ8WQPhKyq+uQhILTXalruhXDV/3iyUhVwAb6X0wwCRq
0EbGBYBA7qTGTmigfVnmrabRp95AF8WrO7mUIhMt+BNYJRlSZsXpSlGGYPznT8uo
22vIA+ssupfF2KA4eJaq8WkK6w67/jPW4YLnEQIDAQABAoIBAQCDVqpcOoZKK9K8
Bt3eXQKEMJ2ji2cKczFFJ5MEm9EBtoJLCryZbqfSue3Fzpj9pBUEkBpk/4VT5F7o
0/Vmc5Y7LHRcbqVlRtV30/lPBPQ4V/eWtly/AZDcNsdfP/J1fgPSvaoqCr2ORLWL
qL/vEfyIeM4GcWy0+JMcPbmABslw9O6Ptc5RGiP98vCLHQh/++sOtj6PH1pt+2X/
Uecv3b1Hk/3Oe+M8ySorJD3KA94QTRnKX+zubkxRg/zCAki+as8rQc/d+BfVG698
ylUT5LVLNuwbWnffY2Zt5x5CDqH01mJnHmxzQEfn68rb3bGFaYPEn9EP+maQijv6
SsUM9A3lAoGBAODRDRn4gEIxjPICp6aawRrMDlRc+k6IWDF7wudjxJlaxFr2t7FF
rFYm+jrcG6qMTyq+teR8uHpcKm9X8ax0L6N6gw5rVzIeIOGma/ZuYIYXX2XJx5SW
SOas1xW6qEIbOMv+Xu9w2SWbhTgyRmtlxxjr2e7gQLz9z/vuTReJpInnAoGBAMMW
sq5lqUfAQzqxlhTobQ7tnB48rUQvkGPE92SlDj2TUt9phek2/TgRJT6mdcozvimt
JPhxKg3ioxG8NPmN0EytjpSiKqlxS1R2po0fb75vputfpw16Z8/2Vik+xYqNMTLo
SpeVkHu7fbtNYEK2qcU44OyOZ/V+5Oo9TuBIFRhHAoGACkqHhwDRHjaWdR2Z/w5m
eIuOvF3lN2MWZm175ouynDKDeoaAsiS2VttB6R/aRFxX42UHfoYXC8LcTmyAK5zF
8X3SMf7H5wtqBepQVt+Gm5zGSSqLcEnQ3H5c+impOh105CGoxt0rk4Ui/AeRIalv
C70AJOcvD3eu5aFq9gDe/1ECgYBAhkVbASzYGnMh+pKVH7rScSxto8v6/XBYT1Ez
7JOlMhD667/qvtFJtgIHkq7qzepbhnTv5x3tscQVnZY34/u9ILpD1s8dc+dibEvx
6S/gYLVorB5ois/DLMqaobRcew6Gs+XX9RPwmLahOJpZ9mh4XrOmCgPAYtP71YM9
ExpHCQKBgQCMMDDWGMRdFMJgXbx1uMere7OoniBdZaOexjbglRh1rMVSXqzBoU8+
yhEuHGAsHGWQdSBHnqRe9O0Bj/Vlw2VVEaJeL1ewRHb+jXSnuKclZOJgMsJAvgGm
SOWIahDrATA4g1T6yLBWQPhj3ZXD3eCMxT1Q3DvpG1DjgvXwmXQJAA==
-----END RSA PRIVATE KEY-----
cipher_suites:
TLS_RSA_WITH_RC4_128_SHA:TLS_RSA_WITH_AES_128_CBC_SHA
status:
user: router_user
password: router_password
login:
logout:
redirect:
parameter:
disable: false
uaa:
admin:
client_secret: admin_secret
batch:
username: batch_username
password: batch_password
cc:
client_secret: cc_client_secret
clients:
app-direct:
secret: app-direct_secret
developer_console:
secret: developer_console_secret
login:
secret: login_client_secret
notifications:
secret: notification_secret
doppler:
secret: doppler_secret
cloud_controller_username_lookup:
secret: cloud_controller_username_lookup_secret
gorouter:
secret: gorouter_secret

jwt:
verification_key: vk
signing_key: sk
scim:
users:
-
admin|fakepassword|scim.write,scim.read,openid,cloud_controller.admin,doppler.firehose

# code_snippet cf-stub-vsphere end
# The previous line helps maintain current documentation at
http://docs.cloudfoundry.org.




Thank you

Ahmed





From: CF Runtime <cfruntime(a)gmail.com>
Reply-To: "Discussions about the Cloud Foundry BOSH project." <
cf-bosh(a)lists.cloudfoundry.org>
Date: Wednesday, June 3, 2015 at 5:40 PM
To: "cf-bosh(a)lists.cloudfoundry.org" <cf-bosh(a)lists.cloudfoundry.org>
Subject: Re: [cf-bosh] cf-stub.yml example with minimum or required
info

Hi Ali,

We try to keep those docs up to date, but it is possible they are
missing some pieces.

Can you tell me what errors you are getting?

Joseph Palermo
CF Runtime Team

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh


Re: `bosh upload release` times out creating packages

Josh Ghiloni
 

That was it. A cautionary tale, I suppose.

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


Can I eliminate host access in esxi/vsphere environments?

Sean Keery <skeery@...>
 

Following up on this thread:
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/NokZ5H6b1Xs

It intimates that I can preload my stemcells on a shared vCenter
datastore. Can I do that and avoid having to open network access to all of
my esxi hosts?

--
Sean Keery
Senior Solutions Architect
PCF Solutions
Pivotal <http://www.pivotal.io>
Mobile: 970.274.1285 | skeery(a)pivotal.io
LinkedIn: @zgrinch <http://www.linkedin.com/in/zgrinch> | Twitter: @zgrinch
<https://twitter.com/zgrinch> | Github: @skibum55
<https://github.com/skibum55>


bosh micro deploy stuck at Started deploy micro bosh > Waiting for the agent

Dulanjalie Dhanapala <dulanjalie@...>
 

Hi all,
I am in the process of bringing up cloud foundry setup using BOSH for the
first time.

when i execute bosh micro deploy it got stuck at below point. I see a Vm
got created in AWS. I am not aware of which log file that i should check.
Please let me know how I can debug this?

Sincerely,
Dulanjalie

cfoundry(a)c-foundry:~/micro-deployment$ bosh micro deploy
light-bosh-stemcell-2986-aws-xen-hvm-ubuntu-trusty-go_agent.tgz


No `bosh-deployments.yml` file found in current directory.


Conventionally, `bosh-deployments.yml` should be saved in /home/cfoundry.

Is /home/cfoundry/micro-deployment a directory where you can save state?
(type 'yes' to continue): yes

Deploying new micro BOSH instance `manifest.yml' to `https://<VIP IP>:25555'
(type 'yes' to continue): yes


Verifying stemcell...

File exists and readable OK

Verifying tarball...

Read tarball OK

Manifest exists OK

Stemcell image file OK

Stemcell properties OK


Stemcell info

-------------

Name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent

Version: 2986


Started deploy micro bosh

Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)

Started deploy micro bosh > Uploading stemcell. Done (00:00:09)

Started deploy micro bosh > Creating VM from ami-3742b55c light. Done
(00:00:35)

Started deploy micro bosh > Waiting for the agent

241 - 260 of 2761