Bug 1493494
| Summary: | [RFE] While adding a content-view to a composite view which is not published, clicking "Add Content Views" button does nothing, it should give an error. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | vivpatil |
| Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Ales Dujicek <adujicek> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.2.11 | CC: | adujicek, bbuckingham, bkearney, michael.hammer |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, 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-02-21 12:39:59 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: | |
| Embargoed: | |||
|
Description
vivpatil
2017-09-20 10:58:20 UTC
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 |