Bug 1300365 - [Admin Portal] User <UNKNOWN> got disconnected from VM $vmname.
Summary: [Admin Portal] User <UNKNOWN> got disconnected from VM $vmname.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.2.5
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: ovirt-3.6.6
: ---
Assignee: jniederm
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-20 15:02 UTC by Jiri Belka
Modified: 2016-04-05 14:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-05 14:10:50 UTC
oVirt Team: Virt
michal.skrivanek: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jiri Belka 2016-01-20 15:02:32 UTC 
Description of problem:

Some events with UNKNOWN again...

Jan 20, 2016 3:50:37 PM
User <UNKNOWN> got disconnected from VM jb-w2k12r2.
	
Jan 20, 2016 3:45:16 PM
User <UNKNOWN> is connected to VM jb-w2k12r2.

2016-01-20 15:45:16,991 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-47) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Use
r <UNKNOWN> is connected to VM jb-w2k12r2.


2016-01-20 15:50:37,836 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-99) [] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Use
r <UNKNOWN> got disconnected from VM jb-w2k12r2.

Version-Release number of selected component (if applicable):
rhevm-backend-3.6.2.5-0.1.el6.noarch

How reproducible:
seems it appears only sometimes

Steps to Reproduce:
1. open console
2.
3.

Actual results:
sometimes user of opened console is not translated and it is displayed as <UNKNOWN>

Expected results:
real user should be part of the event msg

Additional info:
Comment 2 jniederm 2016-04-05 14:10:50 UTC 
I can't reproduce it. Feel free to reopen if it appears again.
Note You need to log in before you can comment on or make changes to this bug.