Bug 1871202 - List of users logged into guest OS is not reset on logout
Summary: List of users logged into guest OS is not reset on logout
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.40.17
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.4.3
: 4.40.28
Assignee: Tomáš Golembiovský
QA Contact: Qin Yuan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-21 15:08 UTC by Tomáš Golembiovský
Modified: 2020-11-11 06:48 UTC (History)
2 users (show)

Fixed In Version: vdsm-4.40.28
Clone Of:
Environment:
Last Closed: 2020-11-11 06:42:15 UTC
oVirt Team: Virt
Embargoed:
ahadas: ovirt-4.4?
ahadas: planning_ack?
ahadas: devel_ack+
ahadas: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110220 0 master MERGED qga: reset users list when all users log off the guest 2021-01-20 16:25:11 UTC

Description Tomáš Golembiovský 2020-08-21 15:08:36 UTC 
When all users logged into guest OS log out the list is not emptied and the last logged in users stays displayed.
Comment 1 Qin Yuan 2020-09-10 07:05:10 UTC 
Verified with:
vdsm-4.40.28-1.el8ev.x86_64
ovirt-engine-4.4.3.1-0.7.el8ev.noarch

Steps:
1. create and run a VM(using latest-rhel-guest-image-8.2-infra template)
2. log into guest OS via `ssh root@guestip`
3. create users: test1, test2, test3
4. log into guest OS via `ssh test1@guestip`, `ssh test2@guestip`, `ssh test3@guestip`
5. check logged in user list
6. log out all users by sequence root, test1, test3, test2
7. check logged in user list

Results:
1. After all users logged in,the logged in user list is root,test1,test2,test3
2. After all users logged out, the logged in user list is empty, which is the desired result.
Comment 2 Sandro Bonazzola 2020-11-11 06:42:15 UTC 
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.
Note You need to log in before you can comment on or make changes to this bug.