Project

General

Profile

Actions

Bug #17608

closed

Hammer --resolve-dependencies flag not working

Added by Andrew Kofink about 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1392063
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
Actions

Also available in: Atom PDF