Bug 1710234
| Summary: | Automation publish of composite CV does not work when multiple content views are promoted | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Magnus Glantz <sudo> | ||||||||
| Component: | Repositories | Assignee: | Jonathon Turel <jturel> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | vijsingh | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 6.5.0 | CC: | egolov, jturel | ||||||||
| Target Milestone: | 6.6.0 | Keywords: | Triaged | ||||||||
| Target Release: | Unused | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | tfm-rubygem-katello-3.12.0.11-1 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-10-22 19:47:09 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: |
|
||||||||||
Created attachment 1568817 [details]
Sosreport
Created attachment 1568818 [details]
Screenshot of failed promotion of composite content view
After the automatic promotion has happened, I did a manual promotion of the composite content view, has all changes been promoted, there would not be any more packages in that promotion, as auto publish was set.
Hi Magnus, Few questions about the problem you're seeing: 1) does it really have to do with the serial nature of the publish of 'x' and 'y' content views and doing them within a few seconds? 2) in your screenshot version 1.0 has no content. were 'x' and 'y' associated to the composite view at that time? Just want to make sure I am looking in the right areas for a fix. One more question Magnus - in reference to your screenshot: in version 4.0 was the content actually unavailabl or is this a 'display issue' showing incorrect numbers? Created redmine issue https://projects.theforeman.org/issues/27194 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27194 has been resolved. ON_QA Verified @Satellite 6.6.0 snap 17.0 Steps/Observation: 1. Created two content views, x and y 2. Created a composite content view consisting of content view x and y and set auto publish 'yes'. 3. Published content views x and y, serially after each other, but with just a couple of seconds between. 4. Composite content view does publish twice and get changes in content view x and y. 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-2019:3172 |
Created attachment 1568816 [details] Foreman debug Description of problem: When multiple content views are published and they are a part of a composite content view with auto publish 'yes' set, the composite content view may not automatically promote all changes. Version-Release number of selected component (if applicable): Satellite 6.5.0 How reproducible: All the time Steps to Reproduce: 1. Create two content views, x and y 2. Create a composite content view consisting of content view x and y and set auto publish 'yes'. 3. Promote content views x and y, serially after each other, but with just a couple of seconds between. 4. Watch as the composite content view only does publish once and not twice, meaning that it will only get the changes in content view x and not y. Actual results: Composite content view only promotes changes in content view x and not y Expected results: Composite content view does two automatic publish and get's changes in both content view x and y. Additional info: