Poor proxy support at install script

[eloyd]

Then I recommend changing the wording to reflect that you do not provide support for the installation process but that you still provide support for the product, even if it was installed (and/or continues to be used) through a proxy.

[tmcdonald]

A fair suggestion, and certainly one I can bring up.

As for the original issue in the thread, any changes to the fullinstall script need to be decided upon by the developers which puts this somewhat out of my hands. The feature request was canceled and we discussed it, determining ultimately that it would not be implemented.

[gormank]

This is an old post, but still open so...
I recently installed NLS and XI with a (restrictive) proxy, with Satellite and all on an IPv6 network internally, and IPv4 to the internet. The fullinstall script typically wants to get to assets.nagios.com which is redirected to nagios.com so .nagios.com was whitelisted. I also had to get the right repos defined in Satellite, tell the proxy to prefer IPv4 (it likes v6 by default), and set up .wgetrc or bash variables to define the proxy, and what not to send to the proxy. By default the proxy gets internal (localhost and Satellite) http requests and will fail.

http_proxy=http://pxy001:3128/
https_proxy=http://pxy001:3128/
no_proxy="localhost, localdomain.com"

My proxy is set up so that anything not whitelisted gets denied.
On the NLS install I commented the ntpdate command since NTP was already configured and was using the port, causing a failure. The installer expects a less configured system, so that's on our Satellite OS install.
On the NXI install I touched installed.repos to make it not send yum off looking for things it can't get to.
I probably could have stopped NTP, and whitelisted more domains to resolve the two remaining issues, but was happy to get it to this point.

Its largely an issue of getting to understand the proxy process, setting up the proxy right, and understanding what not to proxy. If the install script was mine, it would probably different, but its not the underlying issue...

I'm using squid, installing the latest packag and on RHEL 7.3.

[dwhitfield]

@gormank, for clarity, you are not currently experiencing an issue, just providing helpful info for others, correct?

[gormank]

Sorry, yes, this is just info and a statement that the install can be made to work w/o changing the script...

[dwhitfield]

@vmesquita, are we ready to lock this up?

[vmesquita]

As long as it concerns me, you can lock the thread, I am not sure about the other people who posted.