Bug 1304891
| Summary: | Incremental update from UI on a child content view is not propagating automatically to composite content view | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> | ||||||||||||
| Component: | Errata Management | Assignee: | Justin Sherrill <jsherril> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 6.1.6 | CC: | abalakht, bbuckingham, bkearney, cwelton, mmccune, sreber | ||||||||||||
| Target Milestone: | Unspecified | Keywords: | PrioBumpQA, Regression, Triaged | ||||||||||||
| Target Release: | Unused | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| URL: | http://projects.theforeman.org/issues/14399 | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2016-07-27 11:28:17 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: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
sthirugn@redhat.com
2016-02-04 22:17:43 UTC
Correction: All the steps mentioned in `Steps to Reproduce` are done from Satellite 6 Web UI There are no errors in the logs, but the logic to update composites is totally missed. Created redmine issue http://projects.theforeman.org/issues/14399 from this bug Moving to POST since upstream bug http://projects.theforeman.org/issues/14399 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|efe6fac6b679ab697dabe1ba263fa0fd22383b49. WORKAROUND: Utilize the Hammer CLI to perform the incremental update. For example, the following will incrementally update the component view version (13) and propagate the update to the any composite views utilizing it: content-view version incremental-update --organization-id 1 --content-view-version-id 13 --errata-ids RHEA-2012:0002 --propagate-all-composites true Failed QA in Satellite 6.2 Beta Snap 18.2 After incremental update, the composite view is not automatically pulling in the new version. Perhaps we can offer a choice during the update process like I show in my attached screenshot. Created attachment 1176939 [details]
propagate update
I think there may be a misunderstanding how this works. The behavior automatically works against composite content views only when you've selected a system that is within a composite content view. In that case the component will be updated and that will be pushed to the composite. The feature you mention would be a feature request. See my attached screenshot for what the actual page looks like. Moving back to ON_QA Created attachment 1177341 [details]
screen showing what a composite incremental update looks like
Verified in Satellite 6.2 Beta Snap 19. Incremental update is working as expected per Justin's comment above. See attached screenshots for verification. Created attachment 1177377 [details]
verification 1
Created attachment 1177378 [details]
verification 2
Created attachment 1177379 [details]
verification 3
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/RHBA-2016:1501 |