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.
DescriptionJoniel Pasqualetto
2021-03-29 18:24:07 UTC
Description of problem:
1. Job execution fails (for any reason)
2. User wants to rerun job on failed hosts using hammer.
3. Rerun job cannot be posted due to error below:
~~~
# hammer job-invocation rerun --id 20057 --failed-only=true
Validation failed: Targeting: Hosts is invalid
~~~
If "rerun failed" is called using webUI it works fine.
Version-Release number of selected component (if applicable):
Satellite 6.7 (customer) and Satellite 6.8 (internal reproducer)
How reproducible:
** Host on Satellite must have some inconsistent configurations (easy way to reproduce it is assigning a medium_id to the host that is not linked to its operating system) **
1. Try running a job and force it to fail (type wrong password, for example). Note the job id from the URL (https://192.168.250.100/job_invocations/20060 => job id is 20060)
2. Ensure host has a wrong medium_id assigned:
- Create a random media on Satellite and get its id (let's say, medium_id = 12). Do not assign this media to the operating system of the host!
- Assign the medium_id to the host manually:
~~~
echo "update hosts set medium_id = '12' where id = '57';"|su - postgres -c "psql foreman"
~~~
3. Rerun the job using hammer and it will fail:
~~~
hammer job-invocation rerun --id 20060 --failed-only=true
~~~
On the webUI (https://192.168.250.100/job_invocations/20060) click option "Rerun failed" and job will start properly.
Actual results:
WebUI is able to rerun job. Hammer cannot rerun job due to extra verification.
Expected results:
WebUI and hammer should be able to rerun the job (or both should fail). I only expect consistency.
Additional info:
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