Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1438601

Summary: Handle issues with loading execution_plan
Product: Red Hat Satellite Reporter: Ivan Necas <inecas>
Component: Tasks PluginAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: aruzicka, bbuckingham, cduryee, dcaplan, hprakash, inecas, jcallaha, jhutar, mmccune, pwaghmar, zhunting
Target Milestone: UnspecifiedKeywords: PrioBumpField, PrioBumpPM, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman-tasks-0.7.14.14-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1446714 (view as bug list) Environment:
Last Closed: 2017-06-20 17:23:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ivan Necas 2017-04-03 22:05:06 UTC
There are various reasons that can cause the execution plan for a task not being available. We should still try
to not fail completely at those situations and try to show at least the data we have available in foreman_tasks_tasks table.

How to reproduce:

Follow http://projects.theforeman.org/issues/19146 for reproducer steps and go to the tasks details pages after doing so.

Expected results: the tasks page is still showing at least some data, not failing completely.

Current results: the tasks page is broken, returning 500 status code

Comment 1 Ivan Necas 2017-04-03 22:05:11 UTC
Created from redmine issue http://projects.theforeman.org/issues/19147

Comment 2 Ivan Necas 2017-04-03 22:05:17 UTC
Upstream bug assigned to inecas

Comment 4 Ivan Necas 2017-04-03 22:07:01 UTC
An example of such an error might be:

Oops, we're sorry but something went wrong Value (NilClass) '' is not any of: Dynflow::ExecutionPlan::Steps::Abstract.

Comment 5 Ivan Necas 2017-04-05 10:02:46 UTC
*** Bug 1438928 has been marked as a duplicate of this bug. ***

Comment 8 Ivan Necas 2017-05-10 13:21:56 UTC
*** Bug 1406168 has been marked as a duplicate of this bug. ***

Comment 9 Lukas Pramuk 2017-06-09 14:39:13 UTC
VERIFIED.

@satellite-6.2.10-3.0.el7sat.noarch
tfm-rubygem-foreman-tasks-0.7.14.14-1.el7sat.noarch

using manual reproducer described in comment#0:

5. Navigate to /foreman_tasks/tasks

REPRO:

(x) Oops, we're sorry but something went wrong Value (NilClass) '' is not any of: Dynflow::ExecutionPlan::Steps::Abstract.

vs.

FIX:

Actions::Katello::Repository::CapsuleGenerateAndSync N/A
Actions::Katello::Repository::Sync N/A
Actions::Katello::Repository::Sync N/A

>>> Tasks page/detail renders and tasks are listed even if there are invalid tasks

Comment 11 errata-xmlrpc 2017-06-20 17:23:47 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/RHBA-2017:1553

Comment 14 Ivan Necas 2017-09-14 08:47:01 UTC
*** Bug 1400688 has been marked as a duplicate of this bug. ***

Comment 15 Red Hat Bugzilla 2023-09-14 03:55:56 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days