Project

General

Profile

Actions
Copy link

Bug #18746

closed

No route matches [GET] "/javascripts/compute_resources/xenserver/cache_refresh.js"

Added by Torben Hørup over 7 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Just upgraded to foreman_xen 0.5.0
and Now I get this in foreman.log

2017-03-01T12:54:55 f1a9d974 [app] [I] Started GET "/javascripts/compute_resources/xenserver/cache_refresh.js?_=1488369218341" for 192.168.20.2 at 2017-03-01 12:54:55 +0100
2017-03-01T12:54:55 f1a9d974 [app] [F]
ActionController::RoutingError (No route matches [GET] "/javascripts/compute_resources/xenserver/cache_refresh.js"):
 lib/middleware/tagged_logging.rb:18:in `call'
Actions
Copy link
 #1

Updated by Torben Hørup over 7 years ago

  • Status changed from New to Rejected
Actions
Copy link
 #2

Updated by Ben Erickson about 2 years ago

Did you find a way to fix this?

Actions
Copy link
 #3

Updated by Ben Erickson about 2 years ago

Did you find a way to fix this?

edit: I figured this out. Because I installed the plugin via gem, I had to do an asset precompile (which isn't necessary if you install via rpm/deb):
1. dnf install foreman-assets
2. chown -R foreman. /usr/local/share/gems/gems/foreman_xen-1.0.1/
3. foreman-rake plugin:assets:precompile[foreman_xen]
4. chown -R root. /usr/local/share/gems/gems/foreman_xen-1.0.1/
5. systemctl restart foreman

Actions
Copy link

Also available in: Atom PDF