Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The spice console in Satellite6 of a VM running in RHEV does not display any input until the page is reloaded. 
Also, I've noticed that if a spice console is left unattended for a few minutes, the page again need to be reloaded for the console to update.

Version-Release number of selected component (if applicable):
satellite 6.0.4
Browser is firefox-32.0.2-1.fc20 on Fedora 20.
RHEV 3.4.1-031

How reproducible:
Every time

Steps to Reproduce:
1. Create a host on a RHEV compute provider. Make sure you choose a spice console
2. Go to the console (
3.https://satellite6ga.lab.arn.redhat.com/hosts/galera21.lab.arn.redhat.com/console)
4. Type something
5. do note that what you type does not show up.
6. reload the page in your browser
7. Do note that what you typed has shown up.

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.

Per 6.3 planning, moving out non acked bugs to the backlog

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.