Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to vsphere.newClient #5281

Closed
yesnault opened this issue Jun 28, 2020 · 0 comments · Fixed by #5282
Closed

Unable to vsphere.newClient #5281

yesnault opened this issue Jun 28, 2020 · 0 comments · Fixed by #5282
Labels
bug

Comments

@yesnault
Copy link
Member

from Gitter

@sdorsett juin 26 16:57
the error didn't make it into the above post:
Jun 26 09:52:32 cds-engine cds-engine[5777]: 2020-06-26 09:52:32 [ERROR] hatchery:vsphere> Serve: Create> Init error: Unable to vsphere.newClient: Post "https:///sdk": http: no Host in request URL

@sdorsett juin 27 06:01
as a test I updated /opt/cds/conf.toml to have an empty api.vsphere.endpoint and restarted the hatchery. I got the expected error:
Jun 26 22:58:35 cds-engine cds-engine[6388]: Unable to init service hatchery:vsphere: vsphere-endpoint is mandatory
'hatchery.vsphere.endpoint' that was.

@sdorsett juin 27 06:19
so it looks like the /opt/cds/conf.toml hatchery.vsphere values are not being properly passed to vsphere.newClient
@yesnault yesnault added the bug label Jun 28, 2020
yesnault added a commit that referenced this issue Jun 28, 2020
@yesnault
fix(hatchery/vsphere): init endpoint
5d84cb9 
close #5281

initial commit c389564

Signed-off-by: Yvonnick Esnault <[email protected]>
@yesnault yesnault mentioned this issue Jun 28, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(hatchery/vsphere): init endpoint ovh/cds
1 participant
@yesnault