Bug 1120600 - [RFE] Information about repositories and product status in content views
Summary: [RFE] Information about repositories and product status in content views
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Views
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-17 09:11 UTC by Sergio Ocon
Modified: 2017-04-17 18:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-17 18:33:14 UTC


Attachments (Terms of Use)

Description Sergio Ocon 2014-07-17 09:11:09 UTC
Description of problem:
Accessing the Content View gives an understanding of content associated to the content view, repositories, puppet modules and data. But it does not provide information about the changes between the version of the content view and the versions on the repos 

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


How reproducible:
Always

Steps to Reproduce:
1. Create a content view
2. Synchronize the product associated
3.

Actual results:
Content view remains the same

Expected results:
Content view should report:
- That there are new packages availables in the repo
- There are new versions on the repo
- CVE, etc new
- For security, an option to automatically create a new version when CVE are found should be added

Additional info:

Comment 1 RHEL Product and Program Management 2014-07-17 09:24:07 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Og Maciel 2017-04-17 18:33:14 UTC
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.


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