Created attachment 1190932 [details]
full error message text
Description of problem:
Unpublished content views are included to the list of content views to be added as a composite content view components. There are also no client-side verification, so no errors on an attempt to add such an item are raised.
Version-Release number of selected component (if applicable):
fully reproducible (= 100%)
Steps to Reproduce:
1. Log in to Satellite WebUI
2. Create a non-composite content view and do NOT publish it
3. Create a composite content view
4. Select an unpublished content view from a list and try to add it
The error message in console appears (please see the attachment for the full text of the message)
* A client-side error popup/modal with an appropriate explanation
* No unpublished CV's in the CV list
Created attachment 1190934 [details]
and also a screencast
Created redmine issue http://projects.theforeman.org/issues/16346 from this bug
Upstream katello PR: https://github.com/Katello/katello/pull/6283
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16346 has been resolved.
The fix for this issue is that non-published content views will no longer be displayed as being available for association to composite content views. Following the same steps mentioned in the original issue, the non-published content view cannot be associated to a composite content view.
The automation test is failing for this bug on the latest snap 6.3 snap 4
Based upon comment 14, any objection to closing this bug?
The changes that Partha mentioned were to address bug 1177766. As a result, the behavior requested by this bug is no longer valid and has been replaced by that solution. Since the CV publishing now takes in to account if a CV has no versions, we should no longer see the previous side affects.
1. I created a content view X (without publishing it)
2. Created a composite content view Y
3. Added cv X to composite cv Y
4. Published composite content Y
composite content view was published successfully, even if content view X was not published
is this a valid scenario?
Based on feedback from Partha, with the introduction of 'latest' support, it should be a valid scenario. In the scenario from comment 16, no version is available for X; therefore, the default is 'latest' on the composite. Since there is no version of X when composite Y is published, it is simply omitted from the new version of Y.
Based on the new feature of 'latest', I believe this becomes 'notabug'.
Adding needinfo back based upon comment 15.
Thanks Brad for the explanations
Since this is a predicable scenario from now on (with the new functionality), I have no object to close it as NOTABUG, will fix the automation tests accordingly.
Closing this out as NOTABUG based on Comment 19.