Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
I'm having pernament problems with win7x32 guest agent. I'm able to connect trough userportal only after clean boot. Any attempt to login/disconnection immidiatelly causes that I'm not able to login any more. Client waits for timeout and then exits
Version-Release number of selected component (if applicable):
ic134
How reproducible:
100% on my setup (client
Steps to Reproduce:
1. install ic134 tools to a clean installed win7x32 guest
2. login to guest after clean boot (should succeeed)
3. logout && close client (or just close client without logout)
4. login again
Actual results:
client exits as it gets no response from agent
Expected results:
agent should respond just fine
Additional info:
no problem with winxp or win7x64 guest (with agent from the same tools cd)
all rhev/spice services are started
Lubos,
please explain why do you claim SSO does not work,
when you reconnect what do you see? a dark spice screen? the win login page ?
We can't work with so little information.
Hello
there is only black screen (the same screen while spicec is waiting for vdagent response) after spice client starts up and it leads to connection timeout and exit (on windows) and seems like linux client is timeout tolerant and after some timeout connection is normally established.
As far as I remember there is already a patch to windows client (which is not still being shipped with any ic build) which has also vdagent timeout tolerance.
These are the installation logs which are redundant in this case. The agent's log is called "Install.rhev-agent-service.log" (I know... a stupid name).
From your description in comment #14 I'm quite sure that this is not an SSO bug. It sound like the SPICE bug which I've been told it was fixed.
This seems like a duplicate of 719140 which is fixed in ic135 (vdagent-win-0.1-7)
Lubos, can you please try installing the new tools (specifically spice-vdagent) and see if you can reproduce ?
Thanks,
Uri.