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.

Created attachment 1286409 [details]
Screenshot of Tasks page

Description of problem:
I've tried to create organization with existing name via API, corresponding task obviously failed, however under Monitor/Tasks it is listed with state 'planning' and result 'pending' (check attached screenshot). On 6.2 it was 'stopped' and 'error'.

Version-Release number of selected component (if applicable):
Satellite 6.3 Snap 1.0:
* katello-3.4.0-3.el7sat.noarch
* foreman-1.15.0-1.el7sat.noarch
* satellite-6.3.0-15.0.beta.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create organization
2. Try to create another organization with the same name
3. Check task's status at Monitor/Tasks

Actual results:
State 'planning' and result 'pending'

Expected results:
State 'stopped' and result 'error'

Additional info:

Although the upstream bug describes a bit different situation, it was caused by the same thing.

Moving to POST since the bug is fixed in upstream (and released in foreman-tasks-0.9.2)

Verified and validated by automation

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