Bug 1254158 - Missing contents count, sync status and product name under "Affected_repository" section under content-view filter page
Summary: Missing contents count, sync status and product name under "Affected_reposito...
Keywords:
Status: CLOSED DUPLICATE of bug 1277634
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 09:58 UTC by Sachin Ghai
Modified: 2016-04-25 16:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-25 16:28:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
content-view filter page --> under Affected Repo, doesn't show the repo details correctly (51.78 KB, image/png)
2015-08-17 09:58 UTC, Sachin Ghai
no flags Details

Description Sachin Ghai 2015-08-17 09:58:43 UTC
Created attachment 1063768 [details]
content-view filter page --> under Affected Repo, doesn't show the repo details correctly

Description of problem:
Missing contents count, sync status and product name under "Affected_repository" section under content-view filter page

Version-Release number of selected component (if applicable):
sat6.1 GA release

How reproducible:
always

Steps to Reproduce:
1. add a custom repo
2. add a content-view and add that repo to CV
3. create a 'Package' filter and choose 'Affected Repositories' and select "This filter applies only to a subset of repositories in the content view."

Actual results:

Missing contents count, sync status and product name under "Affected_repository" section under content-view filter page

Expected results:
UI should show the package count under contents and should show product name as well as sync status.

Additional info:

Comment 2 Brad Buckingham 2016-04-25 16:28:21 UTC

*** This bug has been marked as a duplicate of bug 1277634 ***


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