Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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 1714645 - NoMethodError: undefined method `[]' for nil:NilClass
Summary: NoMethodError: undefined method `[]' for nil:NilClass
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Reporting
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.6.0
Assignee: Ondřej Ezr
QA Contact: Lukáš Hellebrandt
Depends On:
TreeView+ depends on / blocked
Reported: 2019-05-28 14:03 UTC by Lukáš Hellebrandt
Modified: 2019-10-22 19:48 UTC (History)
5 users (show)

Fixed In Version: foreman-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-22 19:48:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
production.log (17.21 KB, text/plain)
2019-05-28 14:06 UTC, Lukáš Hellebrandt
no flags Details

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26942 0 Normal Closed NoMethodError on generating report template 2020-12-28 05:45:47 UTC

Description Lukáš Hellebrandt 2019-05-28 14:03:12 UTC
Description of problem:
When generating a report, sometimes, after getting to Download page, the error "Internal Server Error: the server was unable to finish the request. This may be caused by unavailability of some required service, incorrect API call or a server-side bug. There may be more information in the server's logs." is shown and the report is not generated.
There is "NoMethodError: undefined method `[]' for nil:NilClass" with traceback in production.log (attached).

This only happened to me once and I don't know how to trigger it. The only nonstandard thing in that case was "Generate at" set to past but I couldn't reproduce again this way.

Version-Release number of selected component (if applicable):
Reproduced on Sat 6.6 snap 4.

How reproducible:
Only happened once (in ~ 100 attempts)

Steps to Reproduce:
1. Monitoring -> Report Templates
2. Generate any template
3. Submit

Actual results:
Sometimes, it fails with an error and traceback

Expected results:
This should always work

Comment 3 Lukáš Hellebrandt 2019-05-28 14:06:23 UTC
Created attachment 1574345 [details]

Comment 5 Ondřej Ezr 2019-06-04 09:01:07 UTC
Created redmine issue from this bug

Comment 6 Bryan Kearney 2019-06-04 10:07:09 UTC
Upstream bug assigned to oezr

Comment 7 Bryan Kearney 2019-06-04 10:07:11 UTC
Upstream bug assigned to oezr

Comment 8 Bryan Kearney 2019-06-10 16:10:01 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue has been resolved.

Comment 10 Ondřej Ezr 2019-07-05 12:05:07 UTC
I have opened the PR, sorry for the delay :(

Comment 12 Lukáš Hellebrandt 2019-07-16 11:25:33 UTC
Verified sanity-only (since no reproducer) with Sat 6.6 snap 11, generating reports works.

Comment 13 Bryan Kearney 2019-10-22 19:48:27 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.