Unable to enable foreman-discovery-plugin due to timeout on metadata check

Support
, ,
1

Problem: I’m unable to run the command foreman-installer --enable-foreman-plugin-discovery because the system sits behind a corporate proxy, so the metadata check times out after two minutes when trying to download the fdi.

Expected outcome: System would use the already configured http_proxy and https_proxy variables, or the variables set for the same in the Foreman GUI.

Foreman and Proxy versions: Foreman 3.14.0, Foreman Smart Proxy 3.14.0

Foreman and Proxy plugin versions: foreman-tasks 10.0.2, foreman_discovery 25.1.1, foreman_remote_execution 15.0.2, katello 4.16.1

Distribution and version: Rocky 9.5 (Blue Onyx)

Other relevant data: I’m able to reach the web pages, and am able to manually run a wget command on the packages that the system is trying to download; that works. I have the packages put manually in places, but I’m not able to run the discovery enable after placing the files in /var/lib/tftpboot/boot, even with the checksum included and having manually validated the files with the checksum. When I try to change the download source with the commands documented in older versions, I’m receiving a failure due to the command not being valid, and receive the same message when I try to put inline syntax for an http/https proxy address. I’d be happy with something that skips the download portion of the plugin enable command if not an actual fix.

1 Like
2

Hi @pokeadmin ,

Were you looking at the docs here? Foreman :: Plugin Manuals

If so, we have more updated documentation here: 6.2. Installing the Discovery service. The old docs are what seems to pop up on search engines.

--foreman-proxy-plugin-discovery-source-url=https://downloads.theforeman.org/discovery/releases/x.y/

The above could potentially be changed to a web server that you host inside your proxy.

Let us know if that command is not working with the errors that pop up.

1 Like
3

This took care of things, thank you! I was using the old Plugin Manuals documentation and it didn’t like the syntax; hosting things on our repo server behind the proxy and setting it as the source worked like a charm.

1 Like