Project

General

Profile

Actions

Bug #35981

closed

Error "undefined method `monitoring_datetime_f' for #<ActionView::Base:0x000000000XXXX> when trying to switch to "legacy ui" view on host

Added by Chuck Farlie over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Whenever I try to switch the host view to "legacy ui" I get the error posted above. This started happening after I upgraded Foreman from 3.3 to 3.4. I was hoping it would resolve itself by upgrading to 3.5, but the issue persists. Any ideas?


Files

legacy_ui_error.txt legacy_ui_error.txt 18.8 KB foreman-rake errors:fetch_log request_id=52c78ab7 Chuck Farlie, 01/23/2023 06:08 PM
Actions #1

Updated by Ewoud Kohl van Wijngaarden over 2 years ago

That comes from the foreman_monitoring plugin (https://github.com/theforeman/foreman_monitoring/blob/a036cdb4d7d969db21bed2b421a131c7ba9495f9/app/views/hosts/_downtime_fields.html.erb#L2). Perhaps the host extensions aren't loaded. That could be a bug in Foreman or in foreman_monitoring.

Actions #2

Updated by Chuck Farlie over 2 years ago

Thanks for the feedback.

My Foreman "About" page has me listed as using the plugin
foreman_monitoring Foreman plugin for monitoring system integration. Timo Goebel 3.0.0

The following package is installed
rubygem-foreman_monitoring-3.0.0-1.fm3_5.el8.noarch

I conducted a health check and noticed this in the production log. Not sure if this is relevant.

2023-01-23T15:51:17 [W|app|] Failed to load Proxmox extension uninitialized constant ForemanFogProxmox | Did you mean? ForemanMonitoring
2023-01-23T15:51:18 [W|app|] Creating scope :execution_scope. Overwriting existing method Host::Managed.execution_scope.
2023-01-23T15:51:18 [W|app|] Failed to load Proxmox extension uninitialized constant ForemanFogProxmox | Did you mean? ForemanMonitoring

Actions #3

Updated by Ewoud Kohl van Wijngaarden about 2 years ago

  • Status changed from New to Rejected

It is indeed a bug in foreman_monitoring, also reported here: https://github.com/theforeman/foreman_monitoring/issues/90#issuecomment-1479977118

Actions

Also available in: Atom PDF