Bug #29264
openHost task show nothing
Added by Elias Pereira over 4 years ago. Updated over 4 years ago.
Description
Hello,
foreman: 2.1 dev
foreman-proxy: 2.1 dev
After the job success terminated, host task shows nothing on output.
Attached image.
Files
host_task.png | View host_task.png | 6.54 KB | Elias Pereira, 03/04/2020 04:12 PM | ||
host_link.png | View host_link.png | 8.87 KB | Elias Pereira, 03/05/2020 01:05 PM | ||
foreman-debug-bojyu.tar.xz | foreman-debug-bojyu.tar.xz | 4.94 MB | Elias Pereira, 03/05/2020 01:30 PM |
Updated by Adam Ruzicka over 4 years ago
What do you mean by "hsot task shows nothing on output"? If I click "host task" in there, it takes me to the task details
Updated by Elias Pereira over 4 years ago
- File host_link.png host_link.png added
Adam Ruzicka wrote:
What do you mean by "hsot task shows nothing on output"? If I click "host task" in there, it takes me to the task details
Ok. I made more tests.
- If I click in the host link (attached host_link.png), I access the command output;
- If I click in Task Details, no output at all. Nothing is shown. I thought it could be the browser's cache, but I tried it on other recently installed ones and there is also no task detail.
production.log when I click on Task Detail
2020-03-05T10:09:17 [I|app|debe3] Started GET "/foreman_tasks/tasks/75391e13-ba61-4161-ad11-f8fab0436085" for 10.60.0.7 at 2020-03-05 10:09:17 -0300 2020-03-05T10:09:17 [I|app|debe3] Processing by ForemanTasks::TasksController#show as HTML 2020-03-05T10:09:17 [I|app|debe3] Parameters: {"id"=>"75391e13-ba61-4161-ad11-f8fab0436085"} 2020-03-05T10:09:17 [I|app|debe3] Rendering vendor/ruby/2.5.0/gems/foreman-tasks-1.0.1/app/views/foreman_tasks/tasks/show.html.erb within layouts/application 2020-03-05T10:09:17 [I|app|debe3] Rendered vendor/ruby/2.5.0/gems/foreman-tasks-1.0.1/app/views/foreman_tasks/tasks/show.html.erb within layouts/application (1.8ms) 2020-03-05T10:09:17 [I|app|debe3] Rendered layouts/_application_content.html.erb (0.3ms) 2020-03-05T10:09:17 [I|app|debe3] Rendering layouts/base.html.erb 2020-03-05T10:09:17 [I|app|debe3] Rendered layouts/base.html.erb (18.9ms) 2020-03-05T10:09:17 [I|app|debe3] Completed 200 OK in 33ms (Views: 21.4ms | ActiveRecord: 3.0ms) 2020-03-05T10:09:18 [I|app|dc3e6] Started GET "/notification_recipients" for 10.60.0.7 at 2020-03-05 10:09:18 -0300 2020-03-05T10:09:18 [I|app|dc3e6] Processing by NotificationRecipientsController#index as JSON 2020-03-05T10:09:18 [I|app|dc3e6] Completed 200 OK in 8ms (Views: 0.1ms | ActiveRecord: 1.3ms)
- After success of task, when I click in host link, happens this error:
Oops, we're sorry but something went wrong can't convert String into an exact number
production.log
2020-03-05T10:09:17 [I|app|debe3] Started GET "/foreman_tasks/tasks/75391e13-ba61-4161-ad11-f8fab0436085" for 10.60.0.7 at 2020-03-05 10:09:17 -0300 2020-03-05T10:09:17 [I|app|debe3] Processing by ForemanTasks::TasksController#show as HTML 2020-03-05T10:09:17 [I|app|debe3] Parameters: {"id"=>"75391e13-ba61-4161-ad11-f8fab0436085"} 2020-03-05T10:09:17 [I|app|debe3] Rendering vendor/ruby/2.5.0/gems/foreman-tasks-1.0.1/app/views/foreman_tasks/tasks/show.html.erb within layouts/application 2020-03-05T10:09:17 [I|app|debe3] Rendered vendor/ruby/2.5.0/gems/foreman-tasks-1.0.1/app/views/foreman_tasks/tasks/show.html.erb within layouts/application (1.8ms) 2020-03-05T10:09:17 [I|app|debe3] Rendered layouts/_application_content.html.erb (0.3ms) 2020-03-05T10:09:17 [I|app|debe3] Rendering layouts/base.html.erb 2020-03-05T10:09:17 [I|app|debe3] Rendered layouts/base.html.erb (18.9ms) 2020-03-05T10:09:17 [I|app|debe3] Completed 200 OK in 33ms (Views: 21.4ms | ActiveRecord: 3.0ms) 2020-03-05T10:09:18 [I|app|dc3e6] Started GET "/notification_recipients" for 10.60.0.7 at 2020-03-05 10:09:18 -0300 2020-03-05T10:09:18 [I|app|dc3e6] Processing by NotificationRecipientsController#index as JSON 2020-03-05T10:09:18 [I|app|dc3e6] Completed 200 OK in 8ms (Views: 0.1ms | ActiveRecord: 1.3ms)
And there is another detail. It is taking too long to complete the task. About 5 minutes.
Updated by Elias Pereira over 4 years ago
Updated by Dirk Götz over 4 years ago
I can see the same problem on a customer setup which is running on Ubuntu 18.04 while my personal setup is fine which runs on CentOS 7.
I assume Adam is using CentOS, too. And from the foreman-debug I can see Elias is using Debian.
So can this be something caused by packaging?