Bug #19692

Opening a libvirt VM console fails with fog-libvirt 0.4.0

Added by Michael Moll 8 months ago. Updated 5 months ago.

Status:Closed
Priority:Normal
Assigned To:Michael Moll
Category:Compute resources - libvirt
Target version:-
Difficulty: Bugzilla link:
Found in release:nightly Pull request:https://github.com/theforeman/foreman/pull/4784
Story points-
Velocity based estimate-
Release1.16.0Release relationshipAuto

Description

Works with 0.3.0, but with 0.4.0:

Failed to set console: Call to virDomainUpdateDeviceFlags failed: Operation not supported: cannot change keymap setting on vnc graphics

trace.log (12.5 KB) Santiago Ruiz, 07/04/2017 11:40 AM


Related issues

Related to Foreman - Refactor #19579: require fog-libvirt 0.4.0 Closed 05/17/2017
Related to Foreman - Bug #1644: Changing VNC keymap on a Libvirt VM (via virt-manager or ... Closed 05/19/2012

Associated revisions

Revision 9b960ab6
Added by Michael Moll 5 months ago

Fixes #1644,#19692 - update fog-libvirt to 0.4.1

History

#1 Updated by Michael Moll 8 months ago

#2 Updated by Michael Moll 8 months ago

  • Related to Bug #1644: Changing VNC keymap on a Libvirt VM (via virt-manager or virsh) causes web-based console to choke added

#3 Updated by Santiago Ruiz 7 months ago

This also affects version 1.15.1.

attached error log

#4 Updated by Carlos Villanueva 6 months ago

Santiago Ruiz wrote:

This also affects version 1.15.1.

attached error log

I can confirm that this issue is present on 1.15.2. I followed all the instructions on setting up NoVNC on Foreman 1.15.2. My Qemu/KVM server is running Centos 7 and I have SELINUX and IPTABLES disabled. My Foreman instance is running on Ubuntu 16.04. I can manage my KVM server from Foreman using the FQDN of the server and qemu+ssh, but whenever I launch the console I get:

Error: Failed to set console: Call to virDomainUpdateDeviceFlags failed: Operation not supported: cannot change keymap setting on vnc graphics

The instance I am trying to console into has en-us set as the keymap, there is no password, vnc is set up to listen on all interfaces and I have auto set up for the VNC port (5903).

If I manually set the VNC port to any port between 5910-5930 I get:

Error: Failed to set console: Call to virDomainUpdateDeviceFlags failed: Operation not supported: cannot change port settings on vnc graphics

In either case, I do not see websockify.py under processes, nor do I see anything significant in the production.log (with debug enabled). Every time I click on the console button, the only thing that pops up in the log is:

2017-07-17T11:03:25 f7a77f80 [app] [I] Current user: admin (administrator)
2017-07-17T11:03:25 f7a77f80 [app] [D] Setting current user thread-local variable to admin
2017-07-17T11:03:25 f7a77f80 [app] [I]   Rendered compute_resources_vms/show/_libvirt.html.erb (28.5ms)
2017-07-17T11:03:25 f7a77f80 [app] [I]   Rendered compute_resources_vms/show.html.erb within layouts/application (34.2ms)
2017-07-17T11:03:25 f7a77f80 [app] [I]   Rendered layouts/_application_content.html.erb (0.4ms)
2017-07-17T11:03:25 f7a77f80 [app] [I]   Rendered home/_user_dropdown.html.erb (3.7ms)
2017-07-17T11:03:25 f7a77f80 [app] [I] Read fragment views/tabs_and_title_records-3 (0.5ms)
2017-07-17T11:03:25 f7a77f80 [app] [I]   Rendered home/_topbar.html.erb (5.9ms)
2017-07-17T11:03:25 f7a77f80 [app] [I]   Rendered layouts/base.html.erb (8.8ms)
2017-07-17T11:03:25 f7a77f80 [app] [I] Completed 200 OK in 86ms (Views: 46.5ms | ActiveRecord: 2.0ms)
2017-07-17T11:03:25 686ab86a [app] [I] Started GET "/notification_recipients" for 198.51.100.51 at 2017-07-17 11:03:25 -0500

At this point, I think I've exhausted all possible options (to include updating the config settings in Firefox). I would really like to get this working if possible.

Cheers,
Carlos

#5 Updated by Santiago Ruiz 6 months ago

Also reported on the fog-libvirt project at:
https://github.com/fog/fog-libvirt/issues/42

#6 Updated by Michael Moll 6 months ago

  • Status changed from New to Assigned
  • Assigned To set to Michael Moll

#7 Updated by The Foreman Bot 5 months ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4784 added

#8 Updated by Michael Moll 5 months ago

  • Release set to 1.16.0

#9 Updated by Michael Moll 5 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF