[TC-264] Traffic Monitor Proxy should not be part of default parameter

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.8.0
• Fix Version/s: 2.1.0
• Component/s: Traffic Ops
• Labels: documentation newbie
• Assignee: Dewayne Richardson
• Reporter: Steve Malenfant
• Created: 01/May/17 17:24
• Updated: 02/May/17 20:10
• Resolved: 01/May/17 19:37

Description

During Traffic Portal integration, the API could not reach Traffic Ops. Found out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter was defined as orphaned variable and was actually being used.

Few things :

1 - This parameter is set at install as an orphan.
2 - This parameter is used even if not assigned to the GLOBAL profile
3 - The code is silent about the proxy not being reachable
4 - The documentation doesn't mention that parameter and which component uses it.

I would suggest the following :

1 - Removed from default parameter install AND/OR 2)
2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not assigned to a profile should not be used.
3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used and show the failed proxy requests
4 - Mention that profile parameter in the documentation

Issue Links

• links to: GitHub Pull Request #534