Bug 1636901

Summary: [UI] - User <UNKNOWN> got disconnected from VM 'VM name' on start VM
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: medium    
Version: 4.2.6.2CC: aoconnor, bugs, lsvaty, mburman, rbarry
Target Milestone: ovirt-4.4.1Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rhv-4.4.0-36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-08 08:26:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
engine log none

Description Michael Burman 2018-10-08 08:37:59 UTC 
Description of problem:
[UI] - User <UNKNOWN> got disconnected from VM 'VM name' 

<UNKNOWN> instead of user's name and what is weird that this messages appears in the event log UI on VM start and not on VM shutdown or dissconnection from the console. 

I think that except the <UNKNOWN> it is also a bug that those messages shown when starting the VM .

Version-Release number of selected component (if applicable):
4.2.7.2_SNAPSHOT-120.gb074dc8.0.scratch.master.el7ev

How reproducible:
100%

Steps to Reproduce:
1. Start a VM

Actual results:
User <UNKNOWN> got disconnected from VM 'VM name'

Expected results:
- Not sure this message should appear on VM start as this is missleading
- User's name instead <UNKNOWN> in the message body.
Comment 1 Michael Burman 2018-10-08 08:39:48 UTC 
Created attachment 1491544 [details]
screenshot
Comment 2 Michael Burman 2018-10-08 08:42:17 UTC 
Created attachment 1491545 [details]
engine log
Comment 3 Red Hat Bugzilla Rules Engine 2018-10-08 12:37:43 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 4 Ryan Barry 2019-01-21 13:34:20 UTC 
Re-targeting, because these bugs either do not have blocker+, or do not have a patch posted
Comment 5 Red Hat Bugzilla Rules Engine 2019-02-12 11:22:00 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 6 Aileen O'Connor 2019-02-12 11:24:19 UTC 
Is this still reproducible on a current 4.3 build.
Comment 7 Michael Burman 2019-02-12 11:44:58 UTC 
(In reply to aoconnor from comment #6)
> Is this still reproducible on a current 4.3 build.

Of course it is. reproduced each time on start VM on all latest 4.3 versions
Comment 9 Michal Skrivanek 2020-03-18 15:44:28 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 10 Michal Skrivanek 2020-03-18 15:49:30 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 12 Michal Skrivanek 2020-03-19 13:59:37 UTC 
it's likely console related.

not very high priority, but worth fixing, it's indeed confusing and a bit annoying...
Comment 13 RHEL Program Management 2020-03-19 13:59:44 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 14 Lukas Svaty 2020-04-01 09:33:39 UTC 
moving to 4.4.0 due to regression keyword
Comment 15 Ryan Barry 2020-04-01 11:15:38 UTC 
This is not a regression in 4.4. Moving back.
Comment 17 Michael Burman 2020-05-26 11:20:33 UTC 
Verified on - rhvm-4.4.1-0.1.el8ev.noarch
Comment 18 Sandro Bonazzola 2020-07-08 08:26:45 UTC 
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.