Troubleshooting

Solution

There are many ways to install virtualenv. For all installation options you can refere to their official documentation - Virtualenv installation.

For example, virtualenv can be installed using pip.

First install pip.

sudo apt install python3-pip

Then install virtualenv using pip3.

pip3 install virtualenv

Solution

Make sure that the libvirt service is running:

sudo systemctl status libvirtd

If the libvirt service is not running, start it:

sudo systemctl start libvirtd

Optional: Start the libvirt service automatically at boot time:

sudo systemctl enable libvirtd

Solution

If the libvirtd service is not running, start it:

sudo systemctl start libvirtd

Add the current user to the libvirt and kvm groups if needed:

# Add current user to groups
sudo usermod -aG libvirt,kvm `id -un`

# Verify groups are added
id -nG

# Reload user session
su - `id -un`

Solution

Make sure the security_driver in /etc/libvirt/qemu.conf is set to none instead of selinux. This line is commented out by default, so you should uncomment it if needed:

# /etc/libvirt/qemu.conf

...
security_driver = "none"
...

Do not forget to restart the libvirt service after making the changes:

sudo systemctl restart libvirtd

Solution

The resource you are trying to create already exists. Make sure you destroy the resource:

virsh destroy your-domain
virsh undefine your-domain

You can verify that the domain was successfully removed:

virsh dominfo --domain your-domain

If the domain was successfully removed, the output should look something like this:

error: failed to get domain 'your-domain'

Solution

Volumes created by Libvirt are still attached to the images, which prevents a new volume from being created with the same name. Therefore, these volumes must be removed:

virsh vol-delete cloud-init.iso --pool your_resource_pool

and / or

virsh vol-delete your-volume.qcow2 --pool your_resource_pool

Solution

Remove the existing libvirt storage pool.

virsh pool-destroy your-pool && virsh pool-undefine your-pool

Solution

Restart the libvirtd service:

sudo systemctl restart libvirtd

Solution

1. Make sure the pool is running.

   virsh pool-start --pool local-k8s-cluster-main-resource-pool
   

2. List volumes in the pool.

   virsh vol-list --pool local-k8s-cluster-main-resource-pool
   
   #  Name         Path
   # -------------------------------------------------------------------------------------
   #  base_volume  /var/lib/libvirt/pools/local-k8s-cluster-main-resource-pool/base_volume
   

3. Delete listed volumes from the pool.

   virsh vol-delete --pool local-k8s-cluster-main-resource-pool --vol base_volume
   

4. Destroy and undefine the pool.

   virsh pool-destroy --pool local-k8s-cluster-main-resource-pool
   virsh pool-undefine --pool local-k8s-cluster-main-resource-pool
   

Solution 1

For example, if an error is thrown when accessing port 80, check which processes are listening on port 80 on the load balancer VM:

netstat -lnput | grep 80

# Proto Recv-Q Send-Q Local Address           Foreign Address   State       PID/Program name
# tcp        0      0 192.168.113.200:80      0.0.0.0:*         LISTEN      1976/haproxy
# tcp        0      0 192.168.113.200:80      0.0.0.0:*         LISTEN      1897/haproxy

If you see more than one process, kill the unnecessary process:

kill 1976

Note: You can kill all HAProxy processes and only one will be automatically recreated.

Solution 2

Check the HAProxy configuration file (config/haproxy/haproxy.cfg) that it does not contain 2 frontends bound to the same port.