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:
Job invocation installs all the installable errata if incorrect `Job Template` is used.
Version-Release number of selected component (if applicable):
Satellite 7.0.0-13.0 RHEL7,RHEL8
How reproducible:
Always
Steps to Reproduce:
1. Sync repos with errata, create lce,cv(promote it),ak
2. Register host and install some packages so that errata is created. (I used 5 errata)
3. Monitor > Jobs > Run Job > Job Category = Katello > Job template = Install errata by search query - Katello SSH Default > Search Query = <registered host> > Errata search query = errataID_1,errataID_2,errataID_3 > Submit
4. You should get a success. Goto Preview templates of the job ran and toggle the job ran.
Actual results:
Under "#Action"(from step 4), you can see `yum -y update-minimal`. That means all the errata have been installed. But only 3 errata were supposed to be installed.
Expected results:
It should have been `yum -y update-minimal --advisory=errataID_1 --advisory=errataID_2 --advisory=errataID_3` so that only the mentioned errata is installed.
Additional info:
Yes, When using `Install errata by search query - Katello SSH Default` to install errata, you're supposed to use it as `id ^ (errataID...)` but incase the customer does not notice it, this step will install all the installable errata for that host(s). Which they might not want.
Adding a searchquery format checker or just let job should fail?
What are the expectations? Agreed that in this case the job shouldn't do anything, but should it be marked as a success or as failure?
> Adding a searchquery format checker
I'm afraid we can't really do that in a sensible way.
Marking it as a failure would be correct here(and easier for you too). If the customer wants to use comma separated errataID, they should use `Install errata - Katello SSH Default` template.
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.11 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-2022:5498