Bug 1431107
| Summary: | it is hard (or there is no way at all) to cancel pending tasks from old remote execution job | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jan Hutař <jhutar> |
| Component: | Remote Execution | Assignee: | Adam Ruzicka <aruzicka> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2.8 | CC: | aruzicka, bbuckingham, egolov, inecas, jcallaha, ktordeur, lhellebr, peter.vreman, psuriset, will_darton |
| Target Milestone: | Unspecified | Keywords: | Triaged, UserExperience |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | scale_lab | ||
| Fixed In Version: | tfm-rubygem-foreman_remote_execution-1.3.4 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-21 16:43:38 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1122832 | ||
|
Description
Jan Hutař
2017-03-10 12:12:27 UTC
Created redmine issue http://projects.theforeman.org/issues/19937 from this bug Upstream bug assigned to aruzicka Upstream bug assigned to aruzicka Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19937 has been resolved. *** Bug 1422466 has been marked as a duplicate of this bug. *** I would expect the subcommands Cancel and Abort in 'hammer job-invocation' but they are not there, tested with snap 29:
# hammer job-invocation --help
Usage:
hammer job-invocation [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND subcommand
[ARG] ... subcommand arguments
Subcommands:
create Create a job invocation
info Show job invocation
list List job invocations
output View the output for a host
Options:
-h, --help print help
# hammer --version
hammer (0.11.0.1)
* hammer_cli_csv (unknown version)
* hammer_cli_foreman (0.11.0.5)
* hammer_cli_foreman_admin (0.0.7)
* hammer_cli_foreman_bootdisk (0.1.3.3)
* hammer_cli_foreman_discovery (1.0.0)
* hammer_cli_foreman_docker (unknown version)
* hammer_cli_foreman_openscap (unknown version)
* hammer_cli_foreman_remote_execution (unknown version)
* hammer_cli_foreman_tasks (unknown version)
* hammer_cli_foreman_virt_who_configure (unknown version)
* hammer_cli_katello (0.11.3.4)
This bug wasn't about being or not being able to do hammer job-invocation cancel --id $id. That is covered in another BZ[1]. This BZ was about how under certain conditions a REX job could get stuck in pending and clicking the cancel button would do nothing. The fix for this BZ addresses this situation and makes the cancel button work even in that case. I'm moving this to ON_QA once more. Please take a look at it again. [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1465521 In that case, I am verifying that the Cancel button actually cancels the pending jobs. Note that is something different than what is proposed in OP. Used Sat6.3 snap 29. Used reproducer from OP. Cancelling the job takes some time (~minute) but works. 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 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 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
|