Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1438601 - Handle issues with loading execution_plan [NEEDINFO]
Handle issues with loading execution_plan
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Tasks Plugin (Show other bugs)
6.2.0
Unspecified Unspecified
high Severity high (vote)
: 6.2.10
: Unused
Assigned To: Ivan Necas
Lukas Pramuk
: PrioBumpField, PrioBumpPM, Triaged
: 1400688 1406168 1438928 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-03 18:05 EDT by Ivan Necas
Modified: 2017-09-14 04:47 EDT (History)
11 users (show)

See Also:
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 13:23:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mmccune: needinfo? (dcaplan)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 19147 None None None 2017-04-03 18:05 EDT
Red Hat Product Errata RHBA-2017:1553 normal SHIPPED_LIVE Satellite 6.2.10 Async Bug Release 2017-06-20 17:19:07 EDT

  None (edit)
Description Ivan Necas 2017-04-03 18:05:06 EDT
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 18:05:11 EDT
Created from redmine issue http://projects.theforeman.org/issues/19147
Comment 2 Ivan Necas 2017-04-03 18:05:17 EDT
Upstream bug assigned to inecas@redhat.com
Comment 4 Ivan Necas 2017-04-03 18:07:01 EDT
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 06:02:46 EDT
*** Bug 1438928 has been marked as a duplicate of this bug. ***
Comment 8 Ivan Necas 2017-05-10 09:21:56 EDT
*** Bug 1406168 has been marked as a duplicate of this bug. ***
Comment 9 Lukas Pramuk 2017-06-09 10:39:13 EDT
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 13:23:47 EDT
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 04:47:01 EDT
*** Bug 1400688 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.