VCH installation fails to find datastore if located within a vCenter folder #3590
Comments
|
What i did to make the command work was to run the command with 'folder_name/dvs_name' instead of only 'dvs_name' on the "--bridge-network" option |
wolruf
changed the title
|
You're right, folders work for portgroups. We tested again. mdestrez@desk:~/VIC/vic$ ./vic-machine-linux create --target |
|
I'm stuck on the same problem... seems they already know of this... #773 |
|
Thanks for finding it! I'm closing this issue, this is indeed the same issue. |
VIC version:
0.8.0GA
Deployment details:
vSphere 6.0U2 is used with vCenter 6.0U2 as well.
Storage is using NFS.
Steps to reproduce:
Have VM Network, VMKernel in a vCenter folder, see screenshot below.
Actual behavior:
Installation fails
Expected behavior:
Ability to specify datastore folder in the installation parameters
Logs:
root@template-wheezy64:~/vic# ./vic-machine-linux create --target pcc-10-255-1-53.ovh.com/pcc-10-255-1-53_datacenter2368 --image-store "pcc-005573" --user [email protected] --bridge-network container1 --compute-resource Cluster1 --no-tlsverify --timeout 1200s --management-network VMKernel --management-network-ip 172.16.24.101 --management-network-gateway 172.16.24.0/23:172.16.24.2/23
INFO[2017-01-11T12:54:43+01:00] ### Installing VCH ####
INFO[2017-01-11T12:54:43+01:00] vSphere password for [email protected]:
WARN[2017-01-11T12:54:52+01:00] Using administrative user for VCH operation - use --ops-user to improve security (see -x for advanced help)
INFO[2017-01-11T12:54:52+01:00] Loaded server certificate virtual-container-host/server-cert.pem
WARN[2017-01-11T12:54:52+01:00] Configuring without TLS verify - certificate-based authentication disabled
INFO[2017-01-11T12:54:52+01:00] Validating supplied configuration
INFO[2017-01-11T12:54:53+01:00] Configuring static IP for additional networks using port group "VMKernel"
INFO[2017-01-11T12:54:53+01:00] Suggesting valid networks for --public-network
INFO[2017-01-11T12:54:53+01:00] Suggested values for --public-network:
INFO[2017-01-11T12:54:53+01:00] "Local PortGroup"
INFO[2017-01-11T12:54:53+01:00] "none"
INFO[2017-01-11T12:54:53+01:00] Suggesting valid networks for --client-network
INFO[2017-01-11T12:54:53+01:00] Suggested values for --client-network:
INFO[2017-01-11T12:54:53+01:00] "Local PortGroup"
INFO[2017-01-11T12:54:53+01:00] "none"
INFO[2017-01-11T12:54:53+01:00] Suggesting valid networks for --management-network
INFO[2017-01-11T12:54:53+01:00] Suggested values for --management-network:
INFO[2017-01-11T12:54:53+01:00] "Local PortGroup"
INFO[2017-01-11T12:54:53+01:00] "none"
INFO[2017-01-11T12:54:53+01:00] Suggesting valid networks for --bridge-network
INFO[2017-01-11T12:54:53+01:00] No valid networks found
INFO[2017-01-11T12:54:53+01:00] Firewall status: DISABLED on "/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.50"
WARN[2017-01-11T12:54:53+01:00] Firewall configuration on "/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.50" may prevent connection on dst 2377/tcp outbound with allowed IPs: [172.16.24.11 172.16.24.10]
INFO[2017-01-11T12:54:53+01:00] Firewall status: DISABLED on "/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.51"
WARN[2017-01-11T12:54:53+01:00] Firewall configuration on "/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.51" may prevent connection on dst 2377/tcp outbound with allowed IPs: [172.16.24.11 172.16.24.10]
WARN[2017-01-11T12:54:53+01:00] Unable to fully verify firewall configuration due to DHCP use on management network
WARN[2017-01-11T12:54:53+01:00] VCH management interface IP assigned by DHCP must be permitted by allowed IP settings
WARN[2017-01-11T12:54:53+01:00] Firewall configuration may be incorrect if firewall is reenabled on hosts:
WARN[2017-01-11T12:54:53+01:00]
"/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.50"
WARN[2017-01-11T12:54:53+01:00]
"/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.51"
INFO[2017-01-11T12:54:53+01:00] Firewall must permit dst 2377/tcp outbound to the VCH management interface if firewall is reenabled
INFO[2017-01-11T12:54:53+01:00] License check OK on hosts:
INFO[2017-01-11T12:54:53+01:00] "/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.50"
INFO[2017-01-11T12:54:53+01:00] "/pcc-10-255-1-53_datacenter2368/host/Cluster1/172.16.24.51"
INFO[2017-01-11T12:54:53+01:00] DRS check OK on:
INFO[2017-01-11T12:54:53+01:00] "/pcc-10-255-1-53_datacenter2368/host/Cluster1/Resources"
ERRO[2017-01-11T12:54:53+01:00] --------------------
ERRO[2017-01-11T12:54:53+01:00] Error checking network for --public-network: network 'VM Network' not found
ERRO[2017-01-11T12:54:53+01:00] Error checking network for --client-network: network 'VM Network' not found
ERRO[2017-01-11T12:54:53+01:00] Error checking network for --management-network: network 'VMKernel' not found
ERRO[2017-01-11T12:54:53+01:00] An existing distributed port group must be specified for bridge network on vCenter: network 'container1' not found
ERRO[2017-01-11T12:54:53+01:00] Create cannot continue: configuration validation failed
ERRO[2017-01-11T12:54:53+01:00] --------------------
ERRO[2017-01-11T12:54:53+01:00] vic-machine-linux failed: validation of configuration failed
The text was updated successfully, but these errors were encountered: