Can't set bosh target, error message "cannot access director"

[YoBetty]

I had been trying to do it on the local machine using the private IP address, then from another machine using the public IP address. The problem appears to be that nothing is listening on port 25555. Did something go wrong during bosh deploy?

[AbelHu]

What is your environment? Do you follow our guidance to use template to deploy it? If you can your bosh manifest to me (chou.hu@microsoft.com), I can help you to investigate it.

[YoBetty]

Yes - it is attached.

Of note - I used the ARB template and the Azure Portal to enter the additional information I generated from creating service principal (client ID and client secret). I did not alter anything else in the manifest file.

I noticed that the private IP address that was created for the bosh vm is 10.0.0.100 while the bosh yml file appears to be looking for 10.0.0.4. Nothing is listening on port 25555 on the bosh vm, which is probably why the director is not running.

Thanks,
Beth

On Feb 1, 2016, at 8:04 PM, Chou Hu notifications@github.com wrote:

What is your environment? Do you follow our guidance to use template to deploy it? If you can your bosh manifest to me (chou.hu@microsoft.com mailto:chou.hu@microsoft.com), I can help you to investigate it.

—
Reply to this email directly or view it on GitHub #87 (comment).

[AbelHu]

@YoBetty I cannot see your any attached file. I guess you cannot attach it when you reply GitHub comments.
10.0.0.100 is the dev-box IP address. 10.0.0.4 is for BOSH director VM. 25555 should be listened in BOSH director VM.
You can send the ~/bosh.yml and ~/run.log to me if you follow our template guidance to deploy it.

[YoBetty]

Chou - I'm asking Pivotal on their end as well, but the pertinent error message in the run.log seems to be that there is "no route to host" over 10.0.0.4:22. My assumption is this probably caused some of the configuration to fail.

[AbelHu]

@YoBetty Which datacenter are you testing? We have a known issue about network. After the VM is created, the network is not ready so that you cannot ssh to the VM. Maybe you hit this issue. If so, please try it in east us. This issue is fixed and east us has been patched.

[YoBetty]

Ok - thanks for letting me know. It was deployed in US Central.

On Feb 4, 2016, at 6:44 AM, Chou Hu notifications@github.com wrote:

@YoBetty Which datacenter are you testing? We have a known issue about network. After the VM is created, the network is not ready so that you cannot ssh to the VM. Maybe you hit this issue. If so, please try it in east us. This issue is fixed and east us has been patched.

—
Reply to this email directly or view it on GitHub.

[YoBetty]

That must have been the problem. I installed it in East and it worked. I looked to see if this was reported on the health page and I didn’t see anything. Going forward, how can I tell if it’s a platform issue?

Thanks for your help!!

On Feb 4, 2016, at 6:44 AM, Chou Hu notifications@github.com wrote:

@YoBetty https://github.com/YoBetty Which datacenter are you testing? We have a known issue about network. After the VM is created, the network is not ready so that you cannot ssh to the VM. Maybe you hit this issue. If so, please try it in east us. This issue is fixed and east us has been patched.

—
Reply to this email directly or view it on GitHub #87 (comment).

[AbelHu]

@YoBetty Normally we need to check bosh-init logs, task logs and bosh-agent logs to identify whether it is a platform issue. Since this issue has been fixed, close it.