Description of problem: When trying to add a new content-view that is not yet published to the composite view, clicking on the "Add Content Views" button does not do anything. This seems expected since the child content view should contain atleast one published version which should be selected while adding it to the composite content view. But some users requests there should be an error message displayed something similar to "Publish the Content View and ensure a version is selected while adding to the composite view" which will be helpful. Version-Release number of selected component (if applicable): Red Hat Satellite 6.2.11 How reproducible: Every time Steps to Reproduce: 1. Create a new empty content view , do not publish 2. Try adding this content view to the composite view Actual results: The "Add Content Views" button does not give an error message. Expected results: The "Add Content Views" button should give an error message.
Note: With the behavior observed in 6.2, while there is no error to the user, the browswer console does show the following: bastion-07af021….js:2 TypeError: Cannot read property 'id' of undefined at bastion_katello-376bfe5….js:3 at Array.forEach (<anonymous>) at Object.i [as forEach] (bastion-07af021….js:1) at c.e.addContentViews (bastion_katello-376bfe5….js:3) at bastion-07af021….js:4 at bastion-07af021….js:4 at c.$eval (bastion-07af021….js:3) at c.$apply (bastion-07af021….js:3) at HTMLButtonElement.<anonymous> (bastion-07af021….js:4) at HTMLButtonElement.dispatch (application-b90592c….js:26) This issue has been resolved in Satellite 6.3 with the introduction of a feature that will allow selection of 'Latest' when associating component content views with a composite. Based on this, I am going to move this bugzilla forward to QE for verification in 6.3 internal builds.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336