common issues

This page contains information about common issues and possible solutions. #Creating snapshots

UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 1: ordinal not in range(128)

UTF-8 is currently not supported - make sure to replace umlauts.

libvirt.libvirtError: internal error: Could not find compute resource specified in '/Stankowic/Test cluster/st-esxi02.stankowic.loc'

Blanks are not supported in vSphere datacenter or cluster names. Avoid them!

#libvirt ##Connectivity

libvirt.libvirtError: internal error curl_easy_perform() returned an error: Couldn't connect to server (7) : couldn't connect to host

Make sure that your firewalls are configured properly.

libvirt.libvirtError: internal error HTTP response code 500 for call to 'SessionIsActive'. Fault: ServerFaultCode - Permission to perform this operation was denied.

You forgot to assign the validate sessions permissions to your vCenter user. Check the wiki

##vCenter support libvirt supports the following URI format along with VMware vCenter:

vpx://myvc/mydc/mysrv

Currently it is not supported to access vCenter without specifying a dedicated ESXi node. As a result you need to know on which ESXi host your systems managed by satprep are running. When using ESXi clusters with technologies like fully-automatic DRS or vMotion this is quite impossible.

There is a workaround for this.

#Preparing maintenance

ERROR:satprep_prepare_maintenance:ERROR: unable to schedule downtime for host 'myhost.localdomain.loc' - please run again with -d / --debug and check HTML output!

Make sure, that the hostnames in Spacewalk/Red Hat Satellite/SUSE Manager and Nagios/Icinga/Thruk/Shinken are the same (e.g. both FQDN). If it is not possible to keep them identical take a look at the advanced setup wiki page.