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.
Description of problem:
Immediate after a 6.2.8 -> 6.2.9 upgrade, when looking at "Task Status" widget on the Dashboard, there's a job of
scheduled pending 1
Clicking on the 1 hyperlink gives a "Tasks" page with
"Insights Email Notifications N/A" scheduled pending
However, clicking on that gives an error in both production.log and in the GUI. In the production.log we see
2017-05-22 09:48:44 a0612a4f [app] [I] Started GET "/foreman_tasks/tasks/427c3d17-7ecd-43de-8d87-859f119becd3" for 131.111.150.66 at 2017-05-22 09:48:44 +0100
2017-05-22 09:48:44 a0612a4f [app] [I] Processing by ForemanTasks::TasksController#show as */*
2017-05-22 09:48:44 a0612a4f [app] [I] Parameters: {"id"=>"427c3d17-7ecd-43de-8d87-859f119becd3"}
2017-05-22 09:48:44 a0612a4f [app] [I] Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.14.11/app/views/foreman_tasks/tasks/_details.html.erb (56.3ms)
2017-05-22 09:48:44 a0612a4f [app] [I] Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.14.11/app/views/foreman_tasks/tasks/show.html.erb (57.4ms)
2017-05-22 09:48:44 a0612a4f [app] [W] Action failed
| NoMethodError: undefined method `join' for "N/A":String
[... Ruby stack trace ...]
2017-05-22 09:48:44 a0612a4f [app] [I] Rendered common/500.html.erb (1.6ms)
2017-05-22 09:48:44 a0612a4f [app] [I] Completed 500 Internal Server Error in 72ms (Views: 2.0ms | ActiveRecord: 4.1ms)
Version-Release number of selected component (if applicable):
RHEL7 and Satellite 6.2.9 both fully yum updated as of 2017-05-22 09:00 BST.
How reproducible:
Every time you click on that task.
Steps to Reproduce:
1. Upgrade to 6.2.9
2. Log in, go to Dashboard
3. Click on the "1" of the scheduled, pending job in the Task Status widget
4. Click on "Insights Email Notifications N/A" in the Tasks widget
Actual results:
500 error in production.log and error in GUI. The job doesn't seem to be going away, either. I can't see when it's scheduled to run.
Expected results:
Be able to view the job. Or just have it actually run and go away.
Additional info:
I'm assuming it's something to do with the "N/A" in the name of the job?
Description of problem: Immediate after a 6.2.8 -> 6.2.9 upgrade, when looking at "Task Status" widget on the Dashboard, there's a job of scheduled pending 1 Clicking on the 1 hyperlink gives a "Tasks" page with "Insights Email Notifications N/A" scheduled pending However, clicking on that gives an error in both production.log and in the GUI. In the production.log we see 2017-05-22 09:48:44 a0612a4f [app] [I] Started GET "/foreman_tasks/tasks/427c3d17-7ecd-43de-8d87-859f119becd3" for 131.111.150.66 at 2017-05-22 09:48:44 +0100 2017-05-22 09:48:44 a0612a4f [app] [I] Processing by ForemanTasks::TasksController#show as */* 2017-05-22 09:48:44 a0612a4f [app] [I] Parameters: {"id"=>"427c3d17-7ecd-43de-8d87-859f119becd3"} 2017-05-22 09:48:44 a0612a4f [app] [I] Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.14.11/app/views/foreman_tasks/tasks/_details.html.erb (56.3ms) 2017-05-22 09:48:44 a0612a4f [app] [I] Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.14.11/app/views/foreman_tasks/tasks/show.html.erb (57.4ms) 2017-05-22 09:48:44 a0612a4f [app] [W] Action failed | NoMethodError: undefined method `join' for "N/A":String [... Ruby stack trace ...] 2017-05-22 09:48:44 a0612a4f [app] [I] Rendered common/500.html.erb (1.6ms) 2017-05-22 09:48:44 a0612a4f [app] [I] Completed 500 Internal Server Error in 72ms (Views: 2.0ms | ActiveRecord: 4.1ms) Version-Release number of selected component (if applicable): RHEL7 and Satellite 6.2.9 both fully yum updated as of 2017-05-22 09:00 BST. How reproducible: Every time you click on that task. Steps to Reproduce: 1. Upgrade to 6.2.9 2. Log in, go to Dashboard 3. Click on the "1" of the scheduled, pending job in the Task Status widget 4. Click on "Insights Email Notifications N/A" in the Tasks widget Actual results: 500 error in production.log and error in GUI. The job doesn't seem to be going away, either. I can't see when it's scheduled to run. Expected results: Be able to view the job. Or just have it actually run and go away. Additional info: I'm assuming it's something to do with the "N/A" in the name of the job?