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 1188354 [details]
screenshot

Description of problem:
Opening task in 'planning' state return an error page with:
"plan_self has to be invoked before being able to reference the output"

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


How reproducible:
Always

Steps to Reproduce:
1. Start capsule synchronization
2. Go to 'Tasks' page
3. Click on the synchronization task while it's in 'planning' state.

Actual results:
error - "plan_self has to be invoked before being able to reference the output"

Expected results:
Task status

Additional info:

Created redmine issue http://projects.theforeman.org/issues/16113 from this bug

Upstream bug assigned to inecas

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/16113 has been resolved.

A deterministic way of reproduce it:

1. Run service foreman-tasks stop
2. Initiate your task
3. Check planned state working as expected
4. Run Run service foreman-tasks start

And now system is working for tasks on planned state on version 6.2.5.

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-2016:2940