When installing the Juju controller I am unable to select my vCenter data store. Approximately 50 datastores are enumerated, but not the data store that I want to use for the Juju controller.
Bug #1886987 reported by
Luke Adams
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Undecided
|
Unassigned |
Bug Description
When attempting to create a Juju controller I receive the following error: failed to bootstrap model: cannot start bootstrap instance: could not find datastore "<name here>". It goes on to list accessible data stores, but only approximately the first 50 in alphabetical order. I believe there is a bug that doesn't allow the additional data stores past 50 to enumberate.
Changed in juju: | |
status: | New → Incomplete |
To post a comment you must log in.
Juju queries for all datastores under the data centre folder. Are you specifying a datastore located elsewhere?
You can try turning on trace debugging for Juju's interactions with vsphere and it will print some useful info about the path used in the data stores query, eg
juju bootstrap vsphere --config logging- config= "<root> =DEBUG; juju.provider. vmware= TRACE"
The data store you are trying to use if definitely accessible to your credential?