Skip to content
This repository has been archived by the owner on Nov 13, 2018. It is now read-only.

Traffic Ops install profile parameter for Traffic Monitor location is incorrect #1016

Closed
rob05c opened this issue Feb 5, 2016 · 0 comments · Fixed by #1017
Closed

Traffic Ops install profile parameter for Traffic Monitor location is incorrect #1016

rob05c opened this issue Feb 5, 2016 · 0 comments · Fixed by #1017
Assignees
@rob05c
Labels
bug Traffic Ops
Milestone
1.4.0

Comments

@rob05c
Copy link
Member

rob05c commented Feb 5, 2016

The profile.traffic_monitor.traffic_ops profile, used to create a default profile with a clean Traffic Ops install, incorrectly has the location set to /opt/rascal/conf when it should be /opt/traffic_monitor/conf. This cause a clean install of Traffic Ops followed by Traffic Monitor to fail in the traffic_monitor_config.pl, because /opt/rascal/conf doesn't exist.

This was caused by the production location being /rascal/, which was then fetched by get_parameters to create the profile. The production parameter has been fixed, so we need to update the profile now.

The fix is trivial and safe.
@rob05c rob05c self-assigned this Feb 5, 2016
@rob05c rob05c added this to the 1.4.0 milestone Feb 5, 2016
@rob05c rob05c mentioned this issue Feb 5, 2016
Merged
@rob05c rob05c added the bug label Feb 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rob05c rob05c

Labels
bug Traffic Ops
Projects
None yet
Milestone
1.4.0
Development

Successfully merging a pull request may close this issue.

Fix Traffic Ops install profile param rob05c/traffic_control
1 participant
@rob05c