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.

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

vic-machine: validation failed if dvSwitch exists in ESXi target #729

Closed
emlin opened this issue May 19, 2016 · 7 comments
Closed

vic-machine: validation failed if dvSwitch exists in ESXi target #729

emlin opened this issue May 19, 2016 · 7 comments
Labels
component/install kind/defect Behavior that is inconsistent with what's intended priority/p2 resolution/incomplete Insufficint information is available to address this issue

Comments

@emlin
Copy link
Contributor

emlin commented May 19, 2016

root [ ~/vic/bin ]# ./vic-machine -target esxi-hp-08.rainpole.com -user root -passwd VMware123! -compute-resource /ha-datacenter/host/esxi-hp-08.rainpole.com/Resources -image-store esxi-hp-08-local -management-network "VM Network"
INFO[2016-05-19T11:49:38Z] ### Installing VCH ####
INFO[2016-05-19T11:49:38Z] Generating certificate/key pair - private key in ./docker-appliance-key.pem
INFO[2016-05-19T11:49:38Z] Validating supplied configuration
ERRO[2016-05-19T11:49:40Z] Unable to get network: SystemError
FATA[2016-05-19T11:49:40Z] Validating supplied configuration failed. Exiting...

[6:57]
In the hostd.log, I see the following:

[6:57]
2016-05-18T15:23:51.346Z error hostd[32EC4B70] [Originator@6876 sub=PropertyProvider opID=328016ee user=root] Unexpected fault reading property: vim.DistributedVirtualSwitch, GetNetworkResourcePool: N5Vmomi5Fault12NotSupported9ExceptionE(vmodl.fault.NotSupported)
2016-05-18T15:23:51.346Z error hostd[32EC4B70] [Originator@6876 sub=PropertyProvider opID=328016ee user=root] Unexpected fault reading property: vim.DistributedVirtualSwitch, GetRuntime: N5Vmomi5Fault12NotSupported9ExceptionE(vmodl.fault.NotSupported)

[7:00]
Could we get a better error message bubble up to vic-machine? Probably something along the lines of “VIC cannot use an ESXi host as a target when a DVS is present” or something to that effect

@emlin emlin added kind/defect Behavior that is inconsistent with what's intended component/install labels May 19, 2016
@emlin emlin self-assigned this May 19, 2016
@dougm
Copy link
Member

dougm commented May 19, 2016

Sounds like we should detect if the ESX host is managed by a VC and exit 1 with a friendly error message, before the installer would even get to this point.

@emlin
Copy link
Contributor Author

emlin commented May 19, 2016

This sounds good. Is there interface in govmomi?

@emlin emlin assigned dougm and unassigned emlin May 19, 2016
@mdubya66 mdubya66 added this to the VIC GA Release milestone Jun 27, 2016
@mhagen-vmware mhagen-vmware added the impact/doc/note Requires creation of or changes to an official release note label Aug 8, 2016
@hickeng
Copy link
Member

hickeng commented Sep 19, 2016

This can occur even if the ESX is not managed by VC - you can have residual config on the ESX in various scenarios.

@stuclem
Copy link
Contributor

stuclem commented Nov 7, 2016

Already in the release notes, so removing the kind/note tag.

@emlin emlin removed the impact/doc/note Requires creation of or changes to an official release note label Nov 7, 2016
@corrieb
Copy link
Contributor

corrieb commented Jul 19, 2017

@emlin. I don't believe this is still an issue. Let's close if not.

@emlin
Copy link
Contributor Author

emlin commented Jul 19, 2017

@corrieb I didn't test it atm, but as comment above, this can occur even if there is left over in ESXi which ever is managed by VC.

@andrewtchin did you ever touch this?
If not, we'd leave it open

@andrewtchin
Copy link
Contributor

I have not tested this

AngieCris pushed a commit to AngieCris/vic that referenced this issue Oct 9, 2017
@zjs zjs added resolution/invalid The issue is intended behavior or otherwise invalid resolution/incomplete Insufficint information is available to address this issue and removed resolution/invalid The issue is intended behavior or otherwise invalid labels Mar 5, 2019
@zjs zjs closed this as completed Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/install kind/defect Behavior that is inconsistent with what's intended priority/p2 resolution/incomplete Insufficint information is available to address this issue
Projects
None yet
Development

No branches or pull requests

9 participants