Problem:
After following the instructions to update foreman to the latest version I now get a blank white screen on login.
I started with version 3.4, with the goal of getting to 3.10. I am currently on 3.7 as I had hoped that further upgrades might address this issue. However it is still there.
foreman-installer in noop mode does not report anything, though I did not use that on install so I only run it in noop mode.
Should I just continue to update until I get to 3.10?
Expected outcome:
Have the foreman login screen appear correctly
Foreman and Proxy versions:
Currently 3.7
I wanted to add, I am now on 3.10 and I still get a blank screen. No errors on install.
Here is what is in the foreman production log
2024-04-08T17:55:41 [I|app|1b3ed3f8] Started GET “/webpack/foreman-vendor.bundle-v12.2.3-production-0a199a5e8633973901ec.css” for x.x.x.x at 2024-04-08 17:55:41 -0700
2024-04-08T17:55:41 [F|app|1b3ed3f8]
1b3ed3f8 | ActionController::RoutingError (No route matches [GET] “/webpack/foreman-vendor.bundle-v12.2.3-production-0a199a5e8633973901ec.css”):
1b3ed3f8 |
1b3ed3f8 | lib/foreman/middleware/logging_context_request.rb:11:in call' 2024-04-08T17:55:41 [F|app|90ca4d50] 90ca4d50 | ActionController::RoutingError (No route matches [GET] "/assets/application-6eccfed1ebb0fffe6f9c4bfb335bd6a69f46ee2bf1e26029ccbfb142baede317.css"): 90ca4d50 | 90ca4d50 | lib/foreman/silenced_logger.rb:37:in silence’
90ca4d50 | lib/foreman/middleware/logging_context_request.rb:11:in call' 2024-04-08T17:55:41 [I|app|7f555014] Started GET "/webpack/vendor.js" forx.x.x.x at 2024-04-08 17:55:41 -0700 2024-04-08T17:55:41 [F|app|7f555014] 7f555014 | ActionController::RoutingError (No route matches [GET] "/webpack/vendor.js"): 7f555014 | 7f555014 | lib/foreman/middleware/logging_context_request.rb:11:in call’
2024-04-08T17:55:41 [F|app|c34099a2]
c34099a2 | ActionController::RoutingError (No route matches [GET] “/assets/late_load-f5ec8513734c84f5ef664a82568b768eed082306d1ce67d088194647aa4bc1ff.js”):
c34099a2 |
c34099a2 | lib/foreman/silenced_logger.rb:37:in silence' c34099a2 | lib/foreman/middleware/logging_context_request.rb:11:in call’
2024-04-08T17:55:42 [F|app|32d98669]
32d98669 | ActionController::RoutingError (No route matches [GET] “/assets/locale/en/app-4581889e779d0de636fe8619ecdb813e98db0b22adad54a236cb5ed8b3c1d843.js”):
32d98669 |
32d98669 | lib/foreman/silenced_logger.rb:37:in silence' 32d98669 | lib/foreman/middleware/logging_context_request.rb:11:in call’
2024-04-08T17:55:42 [I|app|8e75dc69] Started GET “/webpack/foreman-vendor.bundle-v12.2.3-production-0a199a5e8633973901ec.js” for x.x.x.x at 2024-04-08 17:55:42 -0700
2024-04-08T17:55:42 [I|app|9b067e83] Started GET “/webpack/bundle.js” for 192.52.114.27 at 2024-04-08 17:55:42 -0700
2024-04-08T17:55:42 [F|app|8e75dc69]
8e75dc69 | ActionController::RoutingError (No route matches [GET] “/webpack/foreman-vendor.bundle-v12.2.3-production-0a199a5e8633973901ec.js”):
8e75dc69 |
8e75dc69 | lib/foreman/middleware/logging_context_request.rb:11:in call' 2024-04-08T17:55:42 [F|app|ce4ce2d8] ce4ce2d8 | ActionController::RoutingError (No route matches [GET] "/assets/application-afac6de839c78410a684871dcda6305e78bb77062b60b937d358fab6a74c7211.js"): ce4ce2d8 | ce4ce2d8 | lib/foreman/silenced_logger.rb:37:in silence’
ce4ce2d8 | lib/foreman/middleware/logging_context_request.rb:11:in call' 2024-04-08T17:55:42 [F|app|9b067e83] 9b067e83 | ActionController::RoutingError (No route matches [GET] "/webpack/bundle.js"): 9b067e83 | 9b067e83 | lib/foreman/middleware/logging_context_request.rb:11:in call’
The solution to the problem was running the foreman-installer, it completed without error and I can log into the web interface. I do not believe I had originally run the installer, but perhaps I did.
