Red Hat Bugzilla – Bug 482126
Login User is not refreshed after VDSM crash/restart
Last modified: 2016-04-26 13:30:25 EDT
---- Reported by firstname.lastname@example.org 2008-07-06 20:13:35 EDT ----
if you have a server that is running VMs going into non responsive state and then return to function properly, the logged in user name is not refreshed again from the against and remain Unknown this means that any one can connect using spice to those desktops.
---- Additional Comments From email@example.com 2008-07-13 01:17:18 EDT ----
Please elaborate on the process.
Though Iwonder how could you log in with no ticket ??
Please specify the exact stages to reproduce , and especially how did you connect to the VM the second time (through the VDC ???)
---- Additional Comments From firstname.lastname@example.org 2008-07-16 12:40:16 EDT ----
This is in your domain,
In case a VDS turnes not responding and back to up, please make sure the info is refreshed.
In addition keep in mind that we(vdsm) is implementing the diconnect flag on set ticket which may solve the hijack issue (but will not solve the refresh issue)
---- Additional Comments From email@example.com 2008-10-07 01:25:34 EDT ----
1. if guest has no tools, we can't lock, so not sure what behavior should be, wrt to deciding this user should be able to logon/when.
2. if guest has tools, VDC should not allow to connect unless got a response from hyperchannel that the lock action succeeded.
i.e., locking guest and setting ticket should be "transactive"
--- Bug imported by firstname.lastname@example.org 2009-01-27 13:32 EDT ---
This bug was previously known as _bug_ 4438 at http://mantis.tlv.redhat.com/show_bug.cgi?id=4438
Actual time not defined. Setting to 0.0
This bz is listed as ON_QA but no NVR is populated in the Fixed in Version field. Please populate this field with the brew NVR that contains this fix. Thanks!
Also, this is in ON_QA without qa_ack set. Please request qa flag.
Still happens on sp183.
Steps to reproduce:
1.Connect to VDC Admin GUI.
2.You must have VM running and user logged in via SPICE.
In this case username in the GUI will look like Administrator@machine's name
3.Go to VDS and run service vdsmd stop (In the GUI you will see that host turns to non responsive,VMs state turns to Unknown and User turns to Unknown.
4.Now start vdsmd service (service vdsmd start).
5.Host will return to be Up,VM - Up. Logged-in User still Unknown.
I Checked this issue and seems that VDC get username = Unknown after vdsm restart
Please send refresh command via the vmchannel to each vm (guest agent)
It is relevant also after hibernation.
(In reply to comment #5)
> Please send refresh command via the vmchannel to each vm (guest agent)
> It is relevant also after hibernation.
I just did that. Note that we already send 'refresh' after waking from hibernation.
Created attachment 370318 [details]
refresh guest username on recovery
sm30. Fixed, verified.