Bug #7117
open
No clear error when viewing VM console when hypervisor hostname doesn't resolve
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1130159
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):
satellite 6.0.3
How reproducible:
Every time
Steps to Reproduce:
1. try to view the console of a host on libvirt configured with spice
Updated by Dominic Cleal over 9 years ago
- Category set to VM management
- Status changed from New to Feedback
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.
Updated by Dominic Cleal over 9 years ago
- Subject changed from can't connect to spice console of virtual machine to No clear error when viewing VM console when hypervisor hostname doesn't resolve
- Status changed from Feedback to New
Found the issue on the BZ, as per http://theforeman.org/manuals/latest/index.html#7.Troubleshooting, the hypervisor hostname didn't resolve and so websockify couldn't connect.