You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: