Repository navigation
Request canceled client timeout #858
Description
When launching infrakit local vagrant provision vagrant-centos7-vm.json I get the following:
CRIT[02-08|13:59:51] error executing module=main cmd=infrakit err="Post http://h: net/http: request canceled (Client.Timeout exceeded while awaiting headers)" fn=main.main
Post http://h: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
It seems to be a cosmetic issue, but I don't know if infrakit is wanting to keep state on the VM. It looks like it failed, but if you look at the vagrant global-status you see:
$ vagrant global-status
id name provider state directory
5c2ab1d default virtualbox running /tmp/infrakit-473117891
So obviously it succeeded. Also the vagrant plugin seems happy.
INFO[0051] Vagrant STDOUT: default: Running: /tmp/vagrant-shell20180208-23141-vtiee6.sh
INFO[0051] Command completed, err=
Also I would think there would be a command like "infrakit local list" or "infrakit local vagrant list" to see running instances, instead we have to check through vagrant.
Activity
havok4u commentedon Feb 8, 2018
One thing to add. I believe even though the image is running, state is definitely not stored. Started up a new one via infrakit, then checked it via vagrant and then tried to delete it via infrakit and get the following:
CRIT[02-08|17:05:51] error executing module=main cmd=infrakit err="Instance does not exist" fn=main.main
Instance does not exist
The only way to see the id and remove is from vagrant.
nurfet-becirevic commentedon Feb 12, 2018
I noticed the timeout issue while provisioning an instance a few days ago too. Today another, similar one popped up when destroying instances.
EROR[02-12|22:02:50] Failed to destroy instance module=plugin/group id=bac2ff88-aa4a-4e66-ad99-38ee946b2884_6039b034-8775-4481-a235-675299f84aba err="Post http://h: net/http: request canceled (Client.Timeout exceeded while awaiting headers)" fn=github.com/docker/infrakit/pkg/plugin/group.(*scaledGroup).Destroy