Closed vhosakot closed 7 years ago
@vhosakot there's been a PR that was submitted that allows users to increase the disk size: https://github.com/att-comdev/halcyon-vagrant-kubernetes/blob/master/config.rb#L4
would that help?
@v1k0d3n Borne Mace (bmace) confirmed in the #openstack-kolla IRC channel that this issue is not seen.
Turns out my vagrant host has low disk space, and I'm surprised why vagrant does not complain with an error when the host has disk space less than the sum of the disk spaces of all the VMs booted by vagrant. For example, if vagrant boots four VMs each with 10 GB disk and the vagrant host does not have at least >=40 GB disk space, I'd expect vagrant to complain with an error like:
Not enough disk space on host to boot four VMs each with 10 GB disk.
Once I collect all the info, I might open a bug against vagrant to check the host's disk space before booting the VMs. I will also increase the disk space on my vagrant host.
This issue can be closed.
awesome. thanks @vhosakot!
I see the
docker-storage-setup.service
service failed on all the nodes. Looks like a disk space issue? Restartingdocker-storage-setup.service
on the nodes did not help.kube{2,3,4} show
There is not enough free space in volume group VolGroup00 to create data volume of size MIN_DATA_SIZE=2G
. I have not dug into or googled this error yet. Don't know if it affects k8s. I'll submit a PR if I find the solution. I'm using CentOS+libvirt.Restarting
docker-storage-setup.service
on the nodes did not help.