Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 1631812 - Searching by user with ~ is not properly handled.
Summary: Searching by user with ~ is not properly handled.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Tasks Plugin
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.7.0
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks: 1468388
TreeView+ depends on / blocked
 
Reported: 2018-09-21 15:37 UTC by Perry Gagne
Modified: 2020-04-14 13:23 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman-tasks-0.17.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-14 13:23:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25017 0 Normal Closed Searching by user with ~ is not properly handled. 2020-08-17 10:42:36 UTC
Red Hat Bugzilla 1468388 0 medium CLOSED [RFE] Tasks: allow for searching of tasks by 'user' 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2020:1454 0 None None None 2020-04-14 13:23:37 UTC

Internal Links: 1468388

Description Perry Gagne 2018-09-21 15:37:01 UTC
Description of problem:

While testing bz 1468388 i noticed that the ~ operator is not handled properly 


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Create multiple users (eng-user1, eng-user2, bob, sam)
2. Perform some tasks with each of the users. 
3. Monitor -> Tasks. 
4. Search user ~ eng

Actual results: 
Empty search results 


Expected results: 
Tasks run by users with "eng" anywhere in their user name are returned. See docs [1] "... If no wildcard is specified, the string is treated as if surrounded by wildcards: %rhel7%"


Additional info:
The workaround here is to add wildcards to the search like:
user ~ eng-*

This could be an issue for customer who use usernames that contain other information they wish to search on, other then a literal username. For example all service accounts may be prefixed by "serv-servname-".

Comment 2 Adam Ruzicka 2018-09-24 08:44:15 UTC
Created redmine issue http://projects.theforeman.org/issues/25017 from this bug

Comment 3 Satellite Program 2018-09-24 10:03:39 UTC
Upstream bug assigned to aruzicka

Comment 4 Satellite Program 2018-09-24 10:03:42 UTC
Upstream bug assigned to aruzicka

Comment 6 Bryan Kearney 2019-09-10 12:03:19 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25017 has been resolved.

Comment 10 Perry Gagne 2019-12-03 16:56:25 UTC
FailedQA in Sat 6.7 snap 4 same reason as bz 1468388

Comment 12 Peter Ondrejka 2020-01-20 13:50:08 UTC
Verified on Sat 6.7 snap 9

Comment 15 errata-xmlrpc 2020-04-14 13:23:24 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/RHSA-2020:1454


Note You need to log in before you can comment on or make changes to this bug.