Bug 1370243

Summary: Composite Content View shows "Not Yet Published" for older content views
Product: Red Hat Satellite Reporter: Paul Armstrong <parmstro>
Component: Content ViewsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6.2.0CC: bbuckingham, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 17:46:10 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:
Attachments:
Description Flags
Screen shot with issue... none

Description Paul Armstrong 2016-08-25 17:15:01 UTC 
Description of problem:
When a existing composite content view references an older version of an included content view, the WebUI indicates that the included content view is "not yet published", which of course it has been, otherwise it wouldn't be included... 


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

How reproducible:
Always

Steps to Reproduce:
1. Create a composite content view
2. Publish a new version of one of the included views
3. Look at that the content views page for the composite

Actual results:

upgraded content view will show as not yet published.

Expected results:

page should indicate current view and that there is an updated view available.

Additional info:
Comment 1 Paul Armstrong 2016-08-25 18:46:43 UTC 
Created attachment 1194081 [details]
Screen shot with issue...
Comment 3 Brad Buckingham 2016-08-29 14:07:26 UTC 
Created redmine issue http://projects.theforeman.org/issues/16365 from this bug
Comment 4 Bryan Kearney 2018-09-04 17:46:10 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.