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.

Bug 1694862

Summary:	username and hostname filters not restricting output
Product:	Red Hat Enterprise Linux 8	Reporter:	Scott Poore <spoore>
Component:	cockpit-session-recording	Assignee:	jstephen
Status:	CLOSED ERRATA	QA Contact:	Scott Poore <spoore>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	Flags:	pm-rhel: mirror+
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:58:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Scott Poore 2019-04-01 21:26:43 UTC

Description of problem:

I'm trying to use the hostname and username fields to filter output of session-recording sessions.

It does not appear to work.  It seems to attempt to search as I type but the list is the same as default with no search filters.

Version-Release number of selected component (if applicable):
cockpit-session-recording-1-29.el8.noarch


How reproducible:
Unknown

Steps to Reproduce:
1.  Setup cockpit-session-recording and tlog on a host
2.  Add users and configure sssd to record all users
3.  login as different users
4.  change the hostname 
5.  login as different users again
6.  connect to cockpit and go to session-recording
7.  attempt to enter a username or hostname string in the fields at the top

Actual results:
Unable to restrict list using these fields

Expected results:
Should limit search entries returned to only those matching username or hostname strings entered.

Additional info:

Comment 1 Kirill Gliebov 2019-04-03 07:57:02 UTC

It might happen due to fact that now there is a quite complicated loist options and matches for journal and it seems that journal is not able to handle those properly. 
I'll try to change them somehow.

Comment 3 jstephen 2019-07-19 14:08:18 UTC

Fixed upstream: 

https://github.com/Scribery/cockpit-session-recording/commit/142dd4fb6a7ac08cbb11c70983c4654be42de5dd

Comment 5 Scott Poore 2020-01-12 22:58:52 UTC

Verified.

Version ::

cockpit-session-recording-3-1.el8.noarch

Results ::

With no filter:

localuser1  2018-11-28 13:26:06 2018-11-28 13:26:33 00:26   mytesthost.example.test
localuser1  2018-11-28 13:28:14 2018-11-28 13:28:40 00:26   mytesthost.example.test
localuser1  2018-11-28 13:30:21 2018-11-28 13:31:01 00:40   mytesthost.example.test
tlitestlocaluser1   2019-12-06 09:31:24 2019-12-06 09:31:24 00:00   rhel8-4.example.com
tlitestlocaluser1   2019-12-06 09:31:31 2019-12-06 09:31:31 00:00   rhel8-4.example.com
tlitestlocaluser1   2019-12-06 09:31:35 2019-12-06 09:31:35 00:00   rhel8-4.example.com
tlitestlocaluser1   2019-12-06 09:35:07 2019-12-06 09:35:07 00:00   rhel8-4.example.com
root    2019-12-06 09:38:02 2019-12-06 09:38:02 00:00   test0-rhel8-4.example.com
root    2019-12-06 09:38:07 2019-12-06 09:38:07 00:00   test1-rhel8-4.example.com
tlitestlocaluser2   2019-12-06 09:39:59 2019-12-06 09:39:59 00:00   rhel8-4.example.com
tlitestlocaluser1   2020-01-09 15:20:45 2020-01-09 15:20:45 00:00   rhel8-4.example.com
tlitestlocaluser1   2020-01-09 15:20:53 2020-01-09 15:20:53 00:00   rhel8-4.example.com
tlitestlocaluser1   2020-01-09 15:20:57 2020-01-09 15:20:57 00:00   rhel8-4.example.com
tlitestlocaluser1   2020-01-09 15:21:00 2020-01-09 15:21:00 00:00   rhel8-4.example.com
tlitestlocaluser1   2020-01-09 15:24:28 2020-01-09 15:24:28 00:00   rhel8-4.example.com
root    2020-01-09 15:27:23 2020-01-09 15:27:23 00:00   test0-rhel8-4.example.com
root    2020-01-09 15:27:27 2020-01-09 15:27:27 00:00   test1-rhel8-4.example.com
root    2020-01-09 15:27:31 2020-01-09 15:27:31 00:00   test2-rhel8-4.example.com
tlitestlocaluser2   2020-01-09 15:29:20 2020-01-09 15:29:20 00:00   rhel8-4.example.com
tlitestlocaluser1   2020-01-09 16:14:57 2020-01-09 16:15:33 00:36   rhel8-4.example.com
contractor1 2020-01-09 16:19:04 2020-01-09 16:19:25 00:21   rhel8-4.example.com
contractor1 2020-01-09 16:55:02 2020-01-09 16:58:19 03:17   rhel8-4.example.com
contractor1 2020-01-09 17:19:05 2020-01-09 17:19:26 00:20   rhel8-4.example.com
contractor1 2020-01-09 17:30:02 2020-01-09 17:33:46 03:43   rhel8-4.example.com

With contractor1 for username filter:

contractor1 2020-01-09 16:19:04 2020-01-09 16:19:25 00:21   rhel8-4.example.com
contractor1 2020-01-09 16:55:02 2020-01-09 16:58:19 03:17   rhel8-4.example.com
contractor1 2020-01-09 17:19:05 2020-01-09 17:19:26 00:20   rhel8-4.example.com
contractor1 2020-01-09 17:30:02 2020-01-09 17:33:51 03:48   rhel8-4.example.com
contractor1 2020-01-09 17:48:19 2020-01-09 17:48:24 00:04   test0.example.test
contractor1 2020-01-09 17:49:42 2020-01-09 17:49:45 00:03   test2.example.test

With mytesthost.example.test for hostname filter:

localuser1  2018-11-28 13:26:06 2018-11-28 13:26:33 00:26   mytesthost.example.test
localuser1  2018-11-28 13:28:14 2018-11-28 13:28:40 00:26   mytesthost.example.test
localuser1  2018-11-28 13:30:21 2018-11-28 13:31:01 00:40   mytesthost.example.test

Comment 7 errata-xmlrpc 2020-04-28 15:58:45 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2020:1685