Foreman Discovery Image 5.0

Support
1

Hello,
Because of new hardware, I’m currently testing the current Foreman Discovery Image 5.0. I unpacked the ISO onto a stick (Rufus). Then I have booted the image on a Dell notebook. Everything works as expected. I select DHCP, enter the URL to my Foreman server. Then the window for the facts appears. Afterwards, when I click on Confirm, the error message appears that the fact upload failed (The page you were looking for doesn’t exist).

image

If I perform exactly the same steps with the Discovery Image version 4.0.3, the fact upload works and the installation starts. I have also tested the 5.0 image on different hardware and virtually. Always the same error. Have you seen the error before? I have also tested against different Foreman Server versions. No change…

Best regards,
Thomas

2

Foreman production.log shows:

2025-01-30T08:11:50 [I|app|92163760] Started POST “/discovery/create” for 10.5.177.143 at 2025-01-30 08:11:50 +0100
2025-01-30T08:11:50 [I|app|92163760] Katello event daemon started process=1838
2025-01-30T08:11:50 [I|app|92163760] Subscribed to katello.candlepin.candlepin_events
2025-01-30T08:11:50 [I|kat|92163760] Polling Katello Event Queue
2025-01-30T08:11:50 [F|app|92163760]
92163760 | ActionController::RoutingError (No route matches [POST] “/discovery/create”):
92163760 |
92163760 | lib/foreman/middleware/logging_context_request.rb:11:in call' 92163760 | katello (4.14.0) lib/katello/prevent_json_parsing.rb:12:in call’

3

I bumped into this because since 5.0 i also get FAILURE - fact upload failed.

I think the important Part is in the foreman-ssl_access_ssl.log. There it says “POST /discovery/create HTTP/1.1” 404 1564 “-” “Ruby”
While in production.log it says “Started POST “/discovery/create” for … at 2025-04-16 09:52:13 +0200
90475d09 | ActionController::RoutingError (No route matches [POST] “/discovery/create”):
90475d09 |
90475d09 | lib/foreman/middleware/logging_context_request.rb:11:in `call’”
like @tomzellner mentioned.

Before 5.0 it worked like a charme for Years.

Im currently use the Discovery Plugin Version 25.1.0 with proxy.type=foreman, foreman Version 3.14 and i installed it via the .deb Package. I Updated from Foreman 3.13 and Discovery Plugin Version 25.0.0 to test if this fixes the situation but unfortunately not.

I would also be interested to know if there is a git for the development of the discovery image, like there is for the Foreman discovery plugin.

4

I took another look at it today. In old forum posts, I found a note that the path /discovery/create is used for proxy.type=proxy. I couldn’t figure it out exactly, but for proxy.type=foreman it should be a different path.
Up to Image 5.0, we also used proxy.type=foreman and everything worked fine.
As a test, I installed the ruby-smart-proxy-discovery package, restarted the Smart Proxy, and added port 8443 to the URL in the boot parameter proxy.url=. This allowed me to use the new Discovery Image 5.1. I didn’t even need to change proxy.type=foreman.