bosh deployment in Azure is not accessable on ssh after installation
mchudinov opened this issue · 3 comments
Describe the bug
Bosh is not accessable after installation in Azure.
To Reproduce
Steps to reproduce the behavior (example):
Generally follow installation instruction for Azure https://bosh.io/docs/init-azure
- Setup environment VM using this template https://github.com/Azure/azure-quickstart-templates/tree/master/bosh-setup
- Create components https://bosh.io/docs/azure-resources
- then run
bosh create-envcommand
Expected behavior
A functioning instance of bosh director.
Logs
Deployment finished with the following errors in logs:
Cleaning up rendered CPI jobs... Finished (00:00:00)
Deploying:
Creating instance 'bosh/0':
Waiting until instance is ready:
Starting SSH tunnel:
Starting SSH tunnel:
Failed to connect to remote server:
dial tcp 10.0.0.6:22: connect: no route to host
Exit code 1
The IP 10.0.0.6 is used by VM, but it is not exposed.
Command bosh -e bosh-1 env gives error:
mikael@bosh-vm-setup$ bosh -e bosh-1 env
Fetching info:
Performing request GET 'https://bosh-1:25555/info':
Performing GET request:
Retry: Get https://bosh-1:25555/info: dial tcp: lookup bosh-1 on 168.63.129.16:53: no such host
Exit code 1
Versions (please complete the following information):
- Infrastructure: Azure cloud West Eurpe region
- BOSH CLI version 5.2.2
- Stemcell version ubuntu-xenial
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/175048976
The labels on this github issue will be updated when the story is started.
This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.
This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.