Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Adding "--resolve-dependencies=no" to an incremental update has no effect. Dependencies are still published to the content view
Version-Release number of selected component (if applicable):
Satellite 6.2.3
tfm-rubygem-hammer_cli_katello-0.0.22.26-1.el7sat.noarch
How reproducible:
Deploy an incremental update using "--resolve-dependencies=no"
Steps to Reproduce:
1. Promote an errata that will pull in dependencies. Examples:
hammer content-view version incremental-update --organization=MyOrg --content-view-version-id=10 --errata-ids=RHBA-2016:2454 --resolve-dependencies=no #RHEL7
hammer content-view version incremental-update --organization=MyOrg --content-view-version-id=10 --errata-ids=RHSA-2016:1912 --resolve-dependencies=no #RHEL6
2. Compare command output to package list in the errata
3. Confirm by logging into a host using a view with the incremental update:
yum list glibc #RHBA-2016:2454
yum list libX11 #RHSA-2016:1912
Actual results:
Packages included via dependency and not the specified errata are displayed
New versions of packages visible to yum
Expected results:
Only packages in the errata are displayed
Yum shows previous versions of dependent packages
steps to test:
1. Create a custom repo with some erratas (I use https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/)
2. Create a cv and add the repo from 1 to it and not the errata that you'll use to incrementally update (I used RHEA-2012:0055)
3. Create a filter that excludes packages of "*"
4. Publish the cv
5. Run the incremental update without resolve-dependencies: hammer content-view version incremental-update --content-view-version-id <cvv-id> --errata-ids=RHEA-2012:0055 --resolve-dependencies=no
6. Run the incremental update with resolve-dependencies: hammer content-view version incremental-update --content-view-version-id <cvv-id> --errata-ids=RHEA-2012:0055 --resolve-dependencies=yes
Expected:
5. Should only have 3 packages due to no dep-solving
6. Should have 8 packages due to dep-solving
Actual:
5. Content View: own version 1.1
Added Content:
Errata:
RHEA-2012:0055
Packages:
penguin-0.9.1-1.noarch
shark-0.1-1.noarch
walrus-5.21-1.noarch
6. Content View: own version 1.2
Added Content:
Errata:
RHEA-2012:0055
Packages:
bear-4.1-1.noarch
dolphin-3.10.232-1.noarch
lion-0.4-1.noarch
penguin-0.9.1-1.noarch
shark-0.1-1.noarch
tiger-1.0-4.noarch
walrus-5.21-1.noarch
wolf-9.4-2.noarch
Marking verified on 6.10_04
Note: you can find the cvv by running "hammer content-view version list"
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.10 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-2021:4702