Bug 1810774

Summary: Applying errata via Host Collection the errata are trying to be applied to all hosts associated with the host collection
Product: Red Hat Satellite Reporter: Rudnei Bertol Jr. <rbertolj>
Component: Errata ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: aruzicka, cdonnell, inecas, jjeffers, mmccune
Target Milestone: 6.8.0Keywords: PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1832586 1851164 (view as bug list) Environment:
Last Closed: 2020-10-27 13:00:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Rudnei Bertol Jr. 2020-03-05 21:17:06 UTC 
Description of problem:

Applying errata via Host Collection the errata are trying to be applied to all hosts associated with the host collection.

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

6.6

How reproducible:

Create a Host Collection, associate some hosts on this host collection, try to apply an errata that affect a few hosts from this Host Collection via WebUI going to:

   Host > Host Collection > Click on the Host Collection > Errata Installation > Select an errata that affect few hosts > Install Selected


Steps to Reproduce:
1. On the Satellite WebUI try to apply an errata on the hosts associated with a Host Collection

Actual results:

The Satellite will try to apply the errata on all hosts associated with the content view. i.e. If you have 1000 hosts but you would like to apply an errata that affect just 100 hosts, the Errata Job will access the 1000 hosts trying to apply the errata even this errata would not be available for those hosts.

Expected results:

The Satellite tries to apply the errata just on the hosts affected, not on all hosts associated with the Host Collection.

Additional info:
The Satellite is generating a task for all host associated with the Host Collection, it can cause a high load on qpidd in case trying to apply the errata via katello agent.
Comment 3 Craig Donnelly 2020-03-05 21:37:19 UTC 
I think it would be ideal when triggering an action like this against a host collection that the satellite could do an applicability check (if applicability is available for a given host) before just spamming out the ordered action (install/update/remove).
Comment 5 James Jeffers 2020-03-25 16:21:16 UTC 
The upstream correction was exactly as Adam suggested. An applicability check is done on each host before the install is attempted, resulting in a noop for that host.
Comment 13 errata-xmlrpc 2020-10-27 13:00:31 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 (Important: Satellite 6.8 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-2020:4366