Bug 1425159

Summary: Actions::Pulp::Repository::RegenerateApplicability should be able to be cancelled
Product: Red Hat Satellite Reporter: Andrew Kofink <akofink>
Component: RepositoriesAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Jan Hutař <jhutar>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.7CC: andrew.schofield, bbuckingham, cduryee, jcallaha, jhutar, jsherril, mvanderw, tomg
Target Milestone: 6.4.0Keywords: FieldEngineering, PrioBumpField, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:23:49 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:

Description Andrew Kofink 2017-02-20 16:54:37 UTC 
Description of problem:
The Actions::Pulp::Repository::RegenerateApplicability task cannot be cancelled via the Foreman Tasks UI or Dynflow.

Version-Release number of selected component (if applicable):
6.2.7

How reproducible:
Always

Steps to Reproduce:
1.Perform a Actions::Pulp::Repository::RegenerateApplicability task from Katello
2.Try to cancel the task

Actual results:
The cancel button is grayed out

Expected results:
The user can cancel the task

Additional info:
It might be helpful to cause this task to hang by stopping pulp workers so that it doesn't complete before you can test whether it can be cancelled or not.
Comment 5 Justin Sherrill 2017-07-26 16:56:28 UTC 
Created redmine issue http://projects.theforeman.org/issues/20422 from this bug
Comment 6 Satellite Program 2017-07-27 20:18:01 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20422 has been resolved.
Comment 10 Bryan Kearney 2018-10-16 19:23:49 UTC 
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:2927