Note that this is not a horizon bug, I get the same behaviour when
accessing the URL returned from "nova get-vnc-console" directly.
** Changed in: horizon
Status: New => Invalid
** Changed in: nova
Status: New => In Progress
** Changed in: nova
Assignee: (unassigned) => Dr. Jens Rosenboom (j-rosenboom-j)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1622684
Title:
Keycode error using novnc and Horizon console
Status in OpenStack Dashboard (Horizon):
Invalid
Status in OpenStack Compute (nova):
In Progress
Bug description:
When using Newton or Mitaka versons of OpenStack Horizon, I am unable
to talk to the vm in the Horizon console window. I am using noVNC and
I see the following in the console when ever pressing any key on the
keyboard:
atkbd serio0: Use 'setkeycodes 00 ' to make it known.
[ 41.750245] atkbd serio0: Unknown key released (translated set 2,
code 0x0 on isa0060/serio0).
[ 41.750591] atkbd serio0: Use 'setkeycodes 00 ' to make it known.
[ 41.815590] atkbd serio0: Unknown key pressed (translated set 2,
code 0x0 on isa0060/serio0).
[ 41.816087] atkbd serio0: Use 'setkeycodes 00 ' to make it known.
[ 41.945017] atkbd serio0: Unknown key released (translated set 2,
code 0x0 on isa0060/serio0).
[ 41.945848] atkbd serio0: Use 'setkeycodes 00 ' to make it known.
[ 42.393227] atkbd serio0: Unknown key pressed (translated set 2,
code 0x0 on isa0060/serio0).
This appears to be related to recent code changes in noVNC. If I
revert noVNC to the sha 4e0c36dda708628836dc6f5d68fc40d05c7716d9,
everything works. This sha commit date is August 26, 2016.
Phil
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1622684/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
