Bug 1652630 - By default repositories are getting filtered as 'RPM'
Summary: By default repositories are getting filtered as 'RPM'
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: vijsingh
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-22 13:35 UTC by vijsingh
Modified: 2018-11-30 15:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-30 15:32:35 UTC
Target Upstream Version:

Attachments (Terms of Use)
UI Screenshot1 (54.10 KB, image/png)
2018-11-22 13:37 UTC, vijsingh
no flags Details
UI Screenshot1 of 6.4 for ref (57.86 KB, image/png)
2018-11-22 13:38 UTC, vijsingh
no flags Details

Description vijsingh 2018-11-22 13:35:55 UTC
Description of problem:

By default repositories are getting filtered as 'RPM'.

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

Red Hat Satellite 6.5 snap 4

How reproducible:


Steps to Reproduce:

1. On Red Hat Satellite GUI: go to 

   Content > 'Red Hat Repositories' > See right side on Top filter selection as "RPM"

2. Attached screen shots for reference.

Actual results:

By default repositories are getting filtered as 'RPM'

Expected results:

By default repositories should not get filter.

Additional info:

On Red Hat Satellite 6.4 by default there is not any filter type selected

Comment 1 vijsingh 2018-11-22 13:37:20 UTC
Created attachment 1507966 [details]
UI Screenshot1

Comment 2 vijsingh 2018-11-22 13:38:38 UTC
Created attachment 1507967 [details]
UI Screenshot1 of 6.4 for ref

Comment 5 Brad Buckingham 2018-11-30 15:32:35 UTC
The behavior described is working as expected for Satellite 6.5.  During Satellite 6.4, we received feedback that we should provide a default filter on the list.  The default chosen was 'RPM' as it was consistent with the behavior from Satellite 6.3.

For now, I am going to close this bugzilla.  If needed, we research the exact bugzilla that led to the change; however, I was unable to locate from a quick search.

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