New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPI 'create_stemcell' method responded with error #125

Closed
shivamvarma opened this Issue Jul 5, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@shivamvarma

I am trying to setup bosh CPI environment on vsphere and I am getting the following error:-
creating stemcell (bosh-vsphere-esxi-ubuntu-trusty-go_agent 3421.9):
CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"getaddrinfo: Name or service not known (esxi-18.test.hytrust.com:443)","ok_to_retry":false}
please let know how do I fix it.

@mssh2001

This comment has been minimized.

Show comment
Hide comment
@mssh2001

mssh2001 Jul 11, 2017

exact same problem for me

exact same problem for me

@prashantgnet

This comment has been minimized.

Show comment
Hide comment
@prashantgnet

prashantgnet Jul 11, 2017

same issue for me as well

same issue for me as well

@prashantgnet

This comment has been minimized.

Show comment
Hide comment
@prashantgnet

prashantgnet Jul 11, 2017

Issue solved after changing dns entry under bosh.yml to local DNS server.

Issue solved after changing dns entry under bosh.yml to local DNS server.

@dpb587-pivotal

This comment has been minimized.

Show comment
Hide comment
@dpb587-pivotal

dpb587-pivotal Jul 11, 2017

Member

This error usually means DNS has not been correctly configured. If using bosh-deployment, you can use the misc/dns.yml ops file to specify your own internal DNS servers.

bosh create-env bosh.yml -o misc/dns.yml -v internal_dns=[10.0.0.10,10.0.10.10] ...

To investigate and verify further, you could connect to the failing VM and manually verify connectivity with dig/curl.

Member

dpb587-pivotal commented Jul 11, 2017

This error usually means DNS has not been correctly configured. If using bosh-deployment, you can use the misc/dns.yml ops file to specify your own internal DNS servers.

bosh create-env bosh.yml -o misc/dns.yml -v internal_dns=[10.0.0.10,10.0.10.10] ...

To investigate and verify further, you could connect to the failing VM and manually verify connectivity with dig/curl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment