Closed Chopper3 closed 7 years ago
This error is because the vic services initialization failed, most likely it's portlayer service failed. Can you reach the ip 10.101.33.50? If yes, you can check logs from https://10.101.33.50:2378. If you have the installation success, it will show this address.
btw, we ever saw one deployment issue for the bridge network range configuration. I saw your parameter is --bridge-network-range '192.168.100.0/24', the range is too small for bridge network. You will need to make it at least /16 or bigger. If you find error message in portlayer service, which said bridge network configuration issue, this might be the reason.
Thanks for coming back to me, I redeployed this VCH using /16 on the bridge-network, I can ping it but can't get anything from 2378 sorry.
if that's the case, run vic-machine debug --enable-ssh, to enable ssh connection. Then you're able to ssh to the vm. The log files are in /var/log/vic
@Chopper3 you need something bigger than /16. Each of the bridge networks that VIC allows for are /16, so you need something larger than that to accommodate more than one bridge network. The --bridge-network-range
specifies the full pool for the bridge networks. So for instance it is 172.16.0.0/12
by default, which, if I am not mistaken, will allow for 16 /16 bridge networks.
Sorry to be dim, looked around and can't see a working way to use that --enable-ssh, tried the '--enable-ssh=password, didn't work, used a space, used parentheses - it's not listed in the -x list - oh and I'll try with a /12 too
actually both --enable-ssh and --rootpw both say 'flag provided but not defined' - have they been removed?
@Chopper3 have you tried not using those options for vic-machine debug? Just use the minimum options required, and vic-machine debug should turn on ssh with the default password.
just redeployed just using --debug 1 - still not ssh, and root/password doesn't work at the VM console
Sorry I meant use the vic-machine-linux debug
command with the bare minimum options.
Which options would you suggest I drop - it's not far off being at the bare minimum anyway is it?
I believe in your case just
./vic-machine-linux debug --target 'rm101vcenter.room101.com' --user vicadmin@vsphere.local --password notactualpassword --compute-resource '/Room101/host/Main-Cluster/Resources/vSphere Integrated Containers/VCHs' --thumbprint D1:D5:00:99:80:28:51:7D:BB:A2:03:8D:7A:5E:7D:83:1E:B9:45:51 --name 'rm101vch4050'
should suffice.
Nope that won't find my port-groups - if you have multiple clusters in a vCentre you have to spell them out via path - I've spent the last week getting that bit working - I could drop the insecure-repo but everything else is needed - as I say this isn't a home lab anymore, it's a realistic vCenter.
The vic-machine-linux debug
should not care about the port groups that you specified with create. The only options are:
NAME:
vic-machine-linux debug - Debug VCH
USAGE:
vic-machine-linux debug [command options] [arguments...]
OPTIONS:
--target value, -t value REQUIRED. ESXi or vCenter connection URL, specifying a datacenter if multiple exist e.g. root:password@VC-FQDN/datacenter (default: <nil>)
--user value, -u value ESX or vCenter user
--password value, -p value ESX or vCenter password (default: <nil>)
--thumbprint value ESX or vCenter host certificate thumbprint
--id value The ID of the Virtual Container Host, e.g. vm-220
--name value, -n value The name of the Virtual Container Host (default: "virtual-container-host")
--compute-resource value, -r value Compute resource path, e.g. myCluster/Resources/myRP. Default to <default cluster>/Resources
--enable-ssh, --ssh Enable SSH server within appliance VM
--authorized-key value, --key value File with public key to place as /root/.ssh/authorized_keys
--rootpw value, --pw value Password to set for root user (non-persistent over reboots)
--timeout value Time to wait for operation to complete (default: 3m0s)```
Ok, was being dim, didn't realise you ran it against an existing VCH, so did this;
root@rm101vicc [ ~/vic ]# ./vic-machine-linux debug --target 'rm101vcenter.room101.com' --user vicadmin@vsphere.local --password not-actual-password --compute-resource '/Room101/host/Main-Cluster/Resources/vSphere Integrated Containers/VCHs' --thumbprint D1:D5:00:99:80:28:51:7D:BB:A2:03:8D:7A:5E:7D:83:1E:B9:45:51 --name 'rm101vch4050' --enable-ssh --password not-actual-password INFO[2016-11-21T18:45:53Z] ### Configuring VCH for debug #### INFO[2016-11-21T18:45:53Z] INFO[2016-11-21T18:45:53Z] VCH ID: VirtualMachine:vm-1827 INFO[2016-11-21T18:46:04Z] INFO[2016-11-21T18:46:04Z] Installer version: v0.7.0-6507-6c4627d INFO[2016-11-21T18:46:04Z] VCH version: v0.7.0-6507-6c4627d WARN[2016-11-21T18:46:04Z] Unable to identify address acceptable to host certificate INFO[2016-11-21T18:46:04Z] INFO[2016-11-21T18:46:04Z] SSH to appliance: INFO[2016-11-21T18:46:04Z] ssh root@10.101.33.50 INFO[2016-11-21T18:46:04Z] INFO[2016-11-21T18:46:04Z] vic-admin portal: INFO[2016-11-21T18:46:04Z] https://10.101.33.50:2378 INFO[2016-11-21T18:46:04Z] INFO[2016-11-21T18:46:04Z] Published ports can be reached at: INFO[2016-11-21T18:46:04Z] 10.101.33.50 INFO[2016-11-21T18:46:04Z] INFO[2016-11-21T18:46:04Z] Docker environment variables: INFO[2016-11-21T18:46:04Z] DOCKER_HOST=10.101.33.50:2376 INFO[2016-11-21T18:46:04Z] INFO[2016-11-21T18:46:04Z] Connect to docker: INFO[2016-11-21T18:46:04Z] docker -H 10.101.33.50:2376 --tls info INFO[2016-11-21T18:46:04Z] Completed successfully
Which is great, except the 'create' still fails with the same message, though I can now ssh in (my own password wasn't honoured though but I could login with the default one, so logs are below.
Oh and I can't get anything out of port 2378 still, also if I run just 'docker -H 10.101.33.50:2376 --tls info' on the photon VM I'm running 'vic-machine-linux create/debug' on I get 'Cannot connect to the Docker daemon. Is the docker daemon running on this host?', so I don't know how this debug command managed it.
the last line of the log file: time="2016-11-21T18:56:20Z" level=fatal msg="could not initialize port layer: bridge mask is not compatible with bridge pool mask"
is this the result with /12?
damn no, will try again sorry
Damn it - that's it - you can't have a small subnet! a /12 did it - thank you all very much indeed - it might be worth adding that this network MUST be a /12 into the documentation - cheers.
thanks for verify it. #3227 is to track the document issue
v 0.7.0
I'm an infrastructure guy at a large UK telco - we're very interested in VIC so I've been following its development and test deploying most major releases. 0.7.0 seems to do everything I need of it in my home lab (simple 1 x vCenter, 2 x host environment with no firewalls or proxies), so I decided to test deploying into one of our lab environments (1 x vCenter, 20 x HPE hosts all on 6.0u2). After a fair bit of faffing about with the cluster/port-group/storage pathing (see CormacH's recent blog post) I can now build VCHs - but they don't 'finish'.
Here's the output of a 'create' using --debug;
Then lots of these last two lines for nearly ten minutes then this lot;
Maybe you might spot something in this?