Bug 1779638

Summary: Unable to filter/search http-proxies using Organization/Location for Satellite UI.
Product: Red Hat Satellite Reporter: Jameer Pathan <jpathan>
Component: RepositoriesAssignee: Ian Ballou <iballou>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: egolov, iballou, zhunting
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-2.1.0-0, tfm-rubygem-katello-3.16.0-0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:33 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:
Bug Depends On:    
Bug Blocks: 1774324    

Description Jameer Pathan 2019-12-04 12:21:20 UTC
Description of problem:
Unable to filter http-proxies using Organization/Location on Satellite UI.

Version-Release number of selected component (if applicable):
- Satellite 6.7.0 snap 1

How reproducible:
- Always

Steps to Reproduce:
1. Go to Infrastructure > HTTP Proxies
2. Create two or more HTTP Proxies having different organization assigned to them.
3. Use filter to search HTTP Proxies based on Organization/Location. OR
4. Switch to any other Organization.

Actual results:
- All the HTTP Proxies get listed for every Organization.

Expected results:
- HTTP Proxies should be listed based on Organization/Location assigned to them.

Additional info:

[root@hpe-ml350egen8-01 ~]# hammer http-proxy list --organization-id 3
---|-------------------------------
ID | NAME                          
---|-------------------------------
1  | proxy1
3  | proxy3                        
---|-------------------------------

[root@hpe-ml350egen8-01 ~]# hammer http-proxy list --organization-id 1
---|-------------------------------
ID | NAME                          
---|-------------------------------
1  | proxy1
2  | kjk                           
3  | proxy3                        
---|-------------------------------

Comment 3 Brad Buckingham 2019-12-19 22:06:15 UTC
Created redmine issue https://projects.theforeman.org/issues/28552 from this bug

Comment 4 Brad Buckingham 2020-01-17 18:30:31 UTC
Both the foreman and katello PRs have been merged; therefore, moving to POST.

Comment 7 Jameer Pathan 2020-02-10 11:30:44 UTC
FailedQA

Failed on:
- Satellite 6.7.0 snap 11

Test steps:
1. Go to Infrastructure > HTTP Proxies
2. Create two or more HTTP Proxies having different organization assigned to them.
3. Switch to Any Organization and Any Location
4. From search bar, try searching/filtering Http proxy based on location/organization.

Observation:
- Search based on Organization/Location from search tab of Http proxy 
page doesn't work.
- Now switching to different Organization/Locations shows Http proxies assigned to them.
So the part of this issue is fixed. Only filtering/searching http proxies from search bar
doesn't work as expected.

Comment 9 Ian Ballou 2020-02-24 22:58:33 UTC
My PR to Foreman to fix this has been merged.  Related redmine: https://projects.theforeman.org/issues/29070

Comment 10 Jameer Pathan 2020-06-05 14:08:54 UTC
Verified:

Verified with:
- Satellite 6.8.0 snap 3

Test steps:
1. Go to Infrastructure > HTTP Proxies
2. Create two or more HTTP Proxies having different organization assigned to them.
3. Switch to Any Organization and Any Location
4. From search bar, try searching/filtering Http proxy based on location/organization.

Observation:
- Search based on Organization/Location from search tab of Http proxy 
page worked as expected.

Comment 13 errata-xmlrpc 2020-10-27 12:59:33 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 (Important: Satellite 6.8 release), 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:4366