Bug 1974225 - Incremental CV update does not auto-publish CCV
Summary: Incremental CV update does not auto-publish CCV
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.9.0
Hardware: x86_64
OS: Linux
medium
medium with 1 vote
Target Milestone: 6.11.0
Assignee: Ian Ballou
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-21 07:10 UTC by Pavel Moravec
Modified: 2024-02-08 20:15 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:29:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34676 0 Normal New Incremental CV update does not auto-publish CCV 2022-03-24 21:02:04 UTC
Red Hat Knowledge Base (Solution) 6628131 0 None None None 2022-01-07 09:25:43 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:29:45 UTC

Description Pavel Moravec 2021-06-21 07:10:09 UTC
Description of problem:
Having a CCV with auto-publish enabled, doing an incremental update of a CV in the CCV does _not_ trigger an auto-publish of the CCV.

This happens regardless of the CCV has configured the CVs to "Always Use Latest" policy.

After the incremental update completion, the CCV does point to the latest (minor) version of the CV, "just" it didnt do the auto-publish.


Version-Release number of selected component (if applicable):
Sat 6.9


How reproducible:
100%


Steps to Reproduce:
1. Create and publish a CV with some filter (just to be able to add some content later on easily)
2. Create a CCV with auto-publish enabled. Add the CV with "Always Use Latest" policy, and publish this CCV.
3. Optionally publish or promote a new version of the CV to see the CCV will be automatically published.
4. Execute an incremental update of the CV.
5. Check if the CCV was auto-published to contain the incremental content.


Actual results:
3. does happen.
5. does not happen to the CCV


Expected results:
Also incremental update should auto-publish such CCV.


Additional info:

Comment 5 Ian Ballou 2022-03-24 21:02:03 UTC
Created redmine issue https://projects.theforeman.org/issues/34676 from this bug

Comment 6 Bryan Kearney 2022-03-25 00:03:52 UTC
Upstream bug assigned to iballou

Comment 7 Bryan Kearney 2022-03-25 00:03:54 UTC
Upstream bug assigned to iballou

Comment 8 Ian Ballou 2022-03-31 21:25:49 UTC
We're getting inc update + auto publish working with composite content views, but I wanted to make sure users know about the `--propagate-all-composites` flag for incremental update.  If you set that to true in hammer, incremental updates to a component CVV will propagate to all composites that have that component within it.  Auto publish is not necessary if you use that.

Comment 9 Ian Ballou 2022-03-31 22:39:40 UTC
Reading the request again, I realize that it's a bit different from propagate-all-composites.  Is the expectation for a new incremental (y-version) composite version to be created? Or a new x composite version?  If we're incrementally updating the composite (creating a y-version), only the incremental content will be added (this is what propagate-all-composites does).  If we're creating a new x version, then the content from other components within the composite CV will be pulled in as well.

The request seems to read more like a publish should simply be triggered on the composite content view after an incremental update, as long as the inc update produces a new "latest" content view version.  If we're inc updating version 1 out of 100, that won't become the latest.  This would trigger anew x version rather than an incremental y version.

Comment 10 Bryan Kearney 2022-04-07 20:03:50 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34676 has been resolved.

Comment 11 Ian Ballou 2022-04-08 20:36:59 UTC
In the interest of time, we continued with the PR regardless of the needinfo request. my PR makes the composite auto publish if the incremental update produces a version that is the newest one in the component.  I believe that is the intent of the original request.

Comment 12 Pavel Moravec 2022-04-11 06:04:12 UTC
Sorry for not answering the needinfo in time. Yes, that chosen implementation is what was requested, thank you.

Comment 13 Griffin Sullivan 2022-04-29 20:00:23 UTC
Verified in 6.11 snap 18.5 on RHEL 7

Component content view incremental update autopublishes composite content view when use latest is set.

Steps to Reproduce:
1. Create and publish a CV with some filter (just to be able to add some content later on easily)
2. Create a CCV with auto-publish enabled. Add the CV with "Always Use Latest" policy, and publish this CCV.
3. Optionally publish or promote a new version of the CV to see the CCV will be automatically published.
4. Execute an incremental update of the CV.
5. Check if the CCV was auto-published to contain the incremental content.

Expected Results:
Incremental update triggers composite content view to publish a new version.

Actual Results:
Incremental update triggers composite content view to publish a new version.

Here you can see my publish from step 3 (ID 7 and 8) and then the publish from the incremental update (ID 9 and 10).

# hammer content-view version list
---|-------------------------------|---------|--------------------------------------------|-----------------------
ID | NAME                          | VERSION | DESCRIPTION                                | LIFECYCLE ENVIRONMENTS
---|-------------------------------|---------|--------------------------------------------|-----------------------
10 | compview 3.0                  | 3.0     | Auto Publish - Triggered by 'inctestt 2.1' | Library               
9  | inctestt 2.1                  | 2.1     |                                            |                       
8  | compview 2.0                  | 2.0     | Auto Publish - Triggered by 'inctestt 2.0' |                       
7  | inctestt 2.0                  | 2.0     |                                            | Library

Comment 16 errata-xmlrpc 2022-07-05 14:29:32 UTC
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 (Moderate: Satellite 6.11 Release), 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-2022:5498


Note You need to log in before you can comment on or make changes to this bug.