Open sxiii opened 4 months ago
I was thinking if the Go version installed on the server matters or not, maybe it's wrong (too new) version of it?
The panic
is coming from within the virtualbox CPI (cloud provider interface):
based on the code there it seems like an issue with the value being returned when the CPI tries to determine the virtualbox version.
Have you validated that you have all of the requirements for that CPI?
Hi @aramprice ! Thanks for quick answer.
Yes, I think you might be right about Virtualbox CPI issue. I followed the link you provided and couldn't find list of requirements for CPI there. Can you point me to the right direction? I've read these documents: See [bosh-deployment's BOSH Lite on VirtualBox](https://github.com/cloudfoundry/bosh-deployment/blob/master/docs/bosh-lite-on-vbox.md) or [Concourse deployment](https://github.com/cppforlife/concourse-deployment) for example usage.
but couldn't see what is extra on requirements list that I don't match.
Maybe I should try with extra small/demo VM like "hello world" and go from there? Or are there any other debug steps?
Another (maybe related) point is that I'm trying to deploy this in a OVH Machine that apparently uses OpenStack for it's own configuration. I don't know if I'm OK in following the steps I'm following or if I should instead follow the steps in the manual for OpenStack? Or maybe even make a new debian/ubuntu based VM for this... (Edit: tried with Terraform and OpenStack, but this way looks so much more complicated and I'm stuck on earlier stage (auth) with OpenStack).
Thanks!
Hi @sxiii - unfortunately that's about all I can contribute. I can't remember if I've ever used the virtualbox CPI, or what expectations it might have.
For some reason the n.driver.Execute("--version") line of code isn't getting a three-part .
separated string. Maybe the executable isn't being found? Maybe the output isn't the same as it used to be?
-aram
Can this be closed?
Describe the bug Bosh director deployment bug. Regardless if I'm trying to deploy "manually" with:
Or "automagically" with:
I'm getting the same error:
To Reproduce Steps to reproduce the behavior (example):
Expected behavior Bosh director should be deployed.
Logs Logs are provided in the error description.
Versions (please complete the following information):
Deployment info: N/A (just deploying the default director with no changes in config)