-
Bug
-
Resolution: Done
-
Normal
-
6.16.0
-
3
-
False
-
Moderate
-
Artemis Sprint 161, Artemis Sprint 162
-
sat-artemis
-
None
-
None
-
None
-
Automated
When a composite content view is both set to auto-publish and contains a content view set to 'Always update to latest version', it will update twice when an incremental update is applied on the child content view and the --propagate-all-composites flag is set.
How to reproduce:
- Create and publish a content view with missing errata.
- Add that content view to a composite content view and set the CV to 'Always update to latest version'. Set the CCV to auto-publish.
- Run an incremental update on the CV with the --propagate-all-composites flag set:
hammer content-view version incremental-update --content-view-version-id <cvv-id> --errata-ids <erratum-id> --propagate-all-composites true - Look at the new versions of the CCV. There will be a new minor version tracking the incremental update (X.1) and a new major version created in response to the new CV minor version (X+1).
Expected output
CCVs should not auto-publish on child CV minor version updates when the --propagate-all-composites flag is set
- is cloned by
-
SAT-42709 Composite content views can update twice due to a single incremental update of a child content view
-
- Release Pending - Upstream
-