Plugins » Katello

Currently, an incremental update of a content view version will succeed when a package is specified and valid. If that package already exists in the base content view version, we have no logic stopping the update. This should be corrected to throw an error. This can occur for rpm packages, deb packages, and errata.

Reproducer steps using appstream and pip:¶

1. Sync RHEL 9 Appstream and BaseOS.
2. Run `hammer package list --search "name = python3-pip"` and record the package id.
3. Create a new lifecycle environment and record the id.
4. Create a content view containing Appstream and BaseOS and publish it to the new lifecycle environment.
5. Get the rid of the content view version using `hammer content-view version list`.
6. Run `hammer content-view version incremental-update --content-view-version-id <cvv-id> --package-ids <pip-id> --lifecycle-environment-ids <le-id> --organization-id <org-id>`. This will succeed and "Added content:" should show nothing.
7. `hammer content-view version info --id <new_id>` will show no new content.