Bug 1585410 - some tasks in Monitor -> Tasks have "N/A" in a first column
Summary: some tasks in Monitor -> Tasks have "N/A" in a first column
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Tasks Plugin
Version: 6.4
Hardware: Unspecified
OS: Unspecified
low vote
Target Milestone: Released
Assignee: Ivan Necas
QA Contact: Jan Hutař
: 1589854 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2018-06-02 13:54 UTC by Jan Hutař
Modified: 2019-10-07 17:20 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman-tasks-0.13.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-14 12:37:23 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:1222 None None None 2019-05-14 12:37:30 UTC
Foreman Issue Tracker 23889 None None None 2018-06-13 10:47:16 UTC

Description Jan Hutař 2018-06-02 13:54:49 UTC
Description of problem:
some tasks in Monitor -> Tasks have "N/A" in a first column

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

How reproducible:

Steps to Reproduce:
1. Unknown, IMO I have seen some right after the installation

Actual results:
There are tasks with "N/A" in the "Action" column in Monitor -> Tasks

Expected results:
All tasks should have some descriptive name

Additional info:
Tasks with "N/A" I see now have this on the "Raw" tab (maybe there are others as well?):

    Id: d09b03df-7606-49de-b1ae-5ed518c5e0c1
    Label: SendExpireSoonNotifications
    Duration: about 5 hours
    Raw input:
    Raw output:
    External Id: 03b4c6b6-e2f2-4ff1-971e-0230619da8a7

Dynflow on a "Run" tab shows:

    2: Dynflow::ActiveJob::QueueAdapters::JobWrapper (success) [ 0.09s / 0.09s ]

Comment 2 Adam Ruzicka 2018-06-11 14:21:22 UTC
*** Bug 1589854 has been marked as a duplicate of this bug. ***

Comment 3 Ivan Necas 2018-06-13 10:47:14 UTC
Connecting redmine issue http://projects.theforeman.org/issues/23889 from this bug

Comment 10 errata-xmlrpc 2019-05-14 12:37:23 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.


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