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.

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

parent_is_proxy missing from Strategies.yaml #7638

Open
cybertunnel opened this issue Jul 11, 2023 · 0 comments · May be fixed by #7639
Open

parent_is_proxy missing from Strategies.yaml #7638

cybertunnel opened this issue Jul 11, 2023 · 0 comments · May be fixed by #7639
Labels
bug something isn't working as intended cache-config Cache config generation low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one

Comments

@cybertunnel
Copy link
Contributor

This Bug Report affects these Traffic Control components:

  • Traffic Control Cache Config (t3c, formerly ORT)

What did you do?

  1. run t3c-apply like you normally do
  2. check strategies.yaml for parent_is_proxy

What did you expect to happen?

You expect parent_is_proxy to be set

What actually happened?

parent_is_proxy is missing from the strategies.yaml file.

@cybertunnel cybertunnel added the bug something isn't working as intended label Jul 11, 2023
cybertunnel added a commit to cybertunnel/trafficcontrol that referenced this issue Jul 11, 2023
@ocket8888 ocket8888 added low impact affects only a small portion of a CDN, and cannot itself break one cache-config Cache config generation low difficulty the estimated level of effort to resolve this issue is low labels Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended cache-config Cache config generation low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants