Description of problem:
after creating a host configured with a spice console on a libvirt computer provider, if I try to view the console from the satellite 6, I only get a red banner with the text " Error: Unexpected protocol mismatch"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. try to view the console of a host on libvirt configured with spice
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/7117 from this bug
Edit the libvirt domain XML, if you have something similar to this:
<graphics type='spice' autoport='yes'/>
Then change it to:
<graphics type='spice' autoport='yes' listen='0.0.0.0'/>
Otherwise Foreman won't be able to connect to the console on your libvirt hypervisor. The default is to listen to 127.0.0.1 only.
That is how my XML looks, the machine was created from the Sat6 compute provider.
Domain XML attached
Created attachment 927896 [details]
Thanks, looks OK. Do you have any firewalls on the Sat6 server, or between your browser and it? Is SELinux enforcing?
Check that when you view the console page, "ps auxww | grep [w]ebsockify" shows up a process, please paste the output. Check the hostname in the last argument of the command line resolves (this is supplied by libvirt and may indicate a misconfiguration if incorrect).
No firewall on satellite host and AFAIK, no firewall between my browser and the satellite.
SELinux is Permissive and no AVC:s at the time I try to connect.
ps auxww | grep [w]ebsockify
foreman 5911 0.5 0.1 156176 12104 ? S 16:35 0:00 /usr/bin/python /usr/share/foreman/extras/noVNC/websockify.py --daemon --idle-timeout=120 --timeout=120 5910 localhost.localdomain:5901
Also, tcpdump on the satelite show there is traffic comming from my laptop to port 5010.
Is the libvirt compute resource on the same system that runs Satellite 6, or is it different?
If it's different, then it has an identity issue as the "localhost.localdomain" is what libvirt's giving as the hypervisor FQDN. I've seen this a lot before, but I don't know precisely which config drives it, so would double check the usual "hostname -f" resolution etc.
Uhm, yes, the compute provider (libvirt host)is different from the satellite. And yes, it did have hostname set to localhost )-: And fixing that solved the issue.
So would it be possible to somehow make the error message a bit more verbose? If not, feel free to close the bug. And thanks for the help (-:
Upstream bug component is Compute Resources
This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you belive doing so is an issue, please feel free to re-open and provide additional business information. Thank you.