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:
The option to 'rerun' on hosts shall rerun the current jobtemplate again on the host without going to create a full new invocation of the complete job.
There are 2 issues with this:
- It selects again all hosts, even that the URL has hosts_id=[X] in it
- It allows editing of the template etc.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Execute a job on 5 hosts
2. Goto Hosts tab
3. Select rerun on 1 hosts
Actual results:
New job invocation is started with the full query and allow to edit
Expected results:
The same job is executed at the host again without going through the whole process again.
Additional info:
I don't think we change the behavior as there is an value in the original workflow as well. Would providing an option behind a dropdown to 'Rerun immediately' be sufficient enough for this request?
Hoi Ivan.
Sorry, the current behavior is a bug. It does reflect what is written on the action button and what then passed on the URL.
See the attached screenshots where i select rerun on a host.
Then in the next screen i see in the URL the host_ids, but in the query below this value is not used.
As a user i expect that the host_ids is used and overrides (disables) the query field to execute it only on those hosts selected by host_ids.
Verified.
Satellite-6.3 Snap 9
Package versions:
satellite-6.3.0-16.0.beta.el7sat.noarch
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_15.el7sat.noarch
1) Run a job on 100 hosts
2) Wait for it to finish
3) Go to Hosts
4) Select rerun on one of the hosts
5) New job invocation's search query is set to target only the one host
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, 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-2018:0336