Our configs agree, our deployments may not. We're running a cluster
here. Taking a closer look at the back trace. I'm missing the failure
messages for parsing the the availabilityzone. There are a few
conditionals in there that just return Trace (I don't know what that
means) and doesn't send anyth
This is how mine looks
clouds:
vsphere:
type: vsphere
auth-types: [userpass]
endpoint:
regions:
dc0: {}
On Mon, Oct 24, 2016 at 2:10 PM, Peter Petrakis
wrote:
> On Mon, Oct 24, 2016 at 12:19 PM, Horacio Duran
> wrote:
> > Chance seems to be in the right path there.
>
On Mon, Oct 24, 2016 at 12:19 PM, Horacio Duran
wrote:
> Chance seems to be in the right path there.
> In the example "dc0" is the name of our data center, to figure out yours you
> can access the vsphere web client and in there go to:
> Home->Vcenter inventory lists->Resources->Datacenters (all
Beware, current release has a bug that might affect you where many
connections are open and never closed to the vcenter, it is being worked as
we speak and will most likely be included in the next release, sorry for
that.
On Mon, Oct 24, 2016 at 1:19 PM, Horacio Duran
wrote:
> Chance seems to be
Chance seems to be in the right path there.
In the example "dc0" is the name of our data center, to figure out yours
you can access the vsphere web client and in there go to:
Home->Vcenter inventory lists->Resources->Datacenters (all this in the
left tree like menu)
And you will be presented with
Hi Peter,
Is your vsphere data center actually named dc0?
“15:38:47 ERROR cmd supercommand.go:458 failed to create new client: datacenter
'dc0' not found”
The page you referenced gave an example with a data center named dc0. I imagine
yours is named something different?
On 10/24/16, 12:06
