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:
One can not cancel the Foreman Templates export and import from UI for now. 

Version-Release number of selected component (if applicable):
Satellite 6.3 snap 3

How reproducible:
Always

Steps to Reproduce:
1. From UI, Hosts -> Templates -> Sync Templates , Export or import the templates.
2. Attempt to cancel the export / import operation from UI.

Actual results:
No option to cancel the export / import operation from UI.

Expected results:
Add ability to cancel the export / import operation from UI.

There's no way of canceling foregroung operations, e.g. importing vms from compute resource. Given this is not possible today through API/CLI either, this would be an RFE. It was raised that API/CLI supports ctrl+c to interrupt the operation. However ctrl+c in API/CLI is basically an equivalent of closing the browswer tab. It does not cancel the request on the server and the operation will continue executing, the response is just not displayed to anyone. Cancelling would be doable once we make import/export a background task. I'm closing for now, we can reopen if that gets implemented.