Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

+++ This bug was initially created as a clone of Bug #1656691 +++

Description of problem:

unlike BZ #1656684, canceling a job initiated from cockpit-composer gui using "composer-cli compose cancel" results in a hung compose api server.  Newly queued job builds do not start. It remains in waiting state.


--- Additional comment from Brian Lane on 2018-12-07 11:21:52 PST ---

Thanks. Recovering from a crash/reboot is a known issue and #1647985 should fix that.

I'll try to make sense of the logs, but what I was trying to figure out is if you issued 2 cancels to the same build. Either from 2 cli sessions or from cli and gui sessions. It looks like something removed the results directory before the build was done, and it's possible that 2 different requests may do this since I don't have a check for a previously waiting cancel (working on adding that now).


Also, with the current code, cancel really only works before the build starts. I'm working on trying to cancel anaconda while it is running, but am not sure if that can be done without causing other problems. So the cancel will hang until the build is finished and then it will delete the results.

--- Additional comment from Brian Lane on 2018-12-13 08:12:42 PST ---

https://github.com/weldr/lorax/pull/547

Backport PR is here https://github.com/weldr/lorax/pull/615
The pylorax changes will go to rhel7-branch and rhel7-extras, the pylorax.api changes to rhel7-extras only.

Hi Vladimir,

Thanks for pointing me this out.

*** Bug 1659131 has been marked as a duplicate of this bug. ***

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/RHBA-2019:2161