Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Need to generate tm_host using tm.url instead of host header on crconfig generation #2224

Closed
dg4prez opened this issue May 3, 2018 · 0 comments · Fixed by #3069
Closed

Need to generate tm_host using tm.url instead of host header on crconfig generation #2224

dg4prez opened this issue May 3, 2018 · 0 comments · Fixed by #3069
Labels
bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Ops related to Traffic Ops Traffic Router related to Traffic Router

Comments

@dg4prez
Copy link
Contributor

dg4prez commented May 3, 2018

RIght now when a crconfig is generated the tm_host field is generated using the host header. This caused an outage when a crconfig file was generated via script using the management interface, resulting in the management interface FQDN's population to tm_host rather than the correct FQDN.

The correct behavior would be to generate tm_host using the contents of tm.url in global.
@dg4prez dg4prez added bug something isn't working as intended Traffic Router related to Traffic Router critical labels May 3, 2018
@mitchell852 mitchell852 added Traffic Ops related to Traffic Ops and removed Traffic Ops related to Traffic Ops Traffic Ops API (golang) labels Oct 17, 2018
@mitchell852 mitchell852 removed the intake label Nov 7, 2018
rob05c added a commit to rob05c/trafficcontrol that referenced this issue Nov 29, 2018
@rob05c
Fix TO CRConfig generation to use tm.url parameter
2d3c0d3 
Also adds a config param, so it can be set back without a new binary
deployment, if someone discovers it needs to be the host header for
some reason, default false.

Also changes the CRConfig stats.tmpath to be the real path, and adds
a config param to set it back if there's an issue, default false.

Fixes apache#2224
@rob05c rob05c mentioned this issue Nov 29, 2018
Merged
17 tasks
@mitchell852 mitchell852 added the high impact impacts the basic function, deployment, or operation of a CDN label Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug something isn't working as intended high impact impacts the basic function, deployment, or operation of a CDN Traffic Ops related to Traffic Ops Traffic Router related to Traffic Router
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix TO CRConfig generation to use tm.url parameter rob05c/trafficcontrol
2 participants
@mitchell852 @dg4prez