smalenfant opened a new issue, #8111:
URL: https://github.com/apache/trafficcontrol/issues/8111
## This Bug Report affects these Traffic Control components:
- Traffic Monitor
- Traffic Ops
- Traffic Router
## What did you do?
I had 3 tm.url defined as paramters as I was preparing a Traffic Ops
migration. The target one was mapped to the GLOBAL profile. Although looks like
the first one encountered in the DB is used as I couldn't see my change in the
CR-Config.
I've been scratching my head quite a bit on that. After I deleted all the
other tm.url in the DB, my CR-Config finally get assigned to the proper Traffic
Ops.
I couldn't find any documentation on what ${toHostname} is actually mapped
to. It seems like this is tied to the `tm.url` (twelve monkey). Which is
`tm_host` in the cr-config stats section and probably renamed from
${tmHostname}.
I could finally get my Traffic Router to move from different Traffic Ops. I
also believe TR restart are required for this.
https://traffic-control-cdn.readthedocs.io/en/latest/overview/profiles_and_parameters.html#the-global-profile
## What did you expect to happen?
tm.url defined and attached to the GLOBAL profile be used.
## What actually happened?
First encountered tm.url was used.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
