Bug 1394332

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

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:

--- Additional comment from RHEL Product and Program Management on 2016-08-09 14:28:41 EDT ---

Since this issue was entered in Red Hat Bugzilla, the pm_ack has been
set to + automatically for the next planned release

--- Additional comment from Ivan Necas on 2016-08-15 11:27:50 EDT ---

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

--- Additional comment from Bryan Kearney on 2016-08-15 12:17:09 EDT ---

Upstream bug assigned to inecas

--- Additional comment from Bryan Kearney on 2016-09-01 08:19:15 EDT ---

Upstream bug assigned to aruzicka

--- Additional comment from Bryan Kearney on 2016-09-01 08:19:18 EDT ---

Upstream bug assigned to aruzicka

--- Additional comment from  on 2016-09-18 01:36:54 EDT ---

Hello Team,

In one of my customer case:01700466 Cu has encountered the reported issue.

However in this case task which is in question is a Content View Publish task in Planned state.

Is the reported issue related to planned task or the state of the task. Can this be considered in this Bugzilla.


Regards,
Ameya Nerurakar.

--- Additional comment from  on 2016-09-19 02:37:51 EDT ---

Hello Team,

Customer has escalated this case and requesting for a work around on this issue.

Account Name: Unacle B.V.

++++++
Please give me a workaround.
And please make it happen a lot faster than the previous mails.
+++++

Can any one please help with the same.


Regards,
Ameya Nerurkar

--- Additional comment from Bryan Kearney on 2016-09-30 16:36:48 EDT ---

Ivan, any idea of a work around for the CU?

--- Additional comment from Ivan Necas on 2016-10-05 08:56:00 EDT ---

As per comments and state of the customer case, the needed info was already provided and it helped the customer to fix the issue. For record, the real cause of the trouble was this BZ https://bugzilla.redhat.com/show_bug.cgi?id=1379820,
which also provides workaround information in case somebody else hits this issue as well

--- Additional comment from Bryan Kearney on 2016-11-01 08:12:23 EDT ---

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16113 has been resolved.