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

TS cache config creates duplicate lines in ip_allow.yaml for mid servers #7763

Open
AbdelrahmanElawady opened this issue Aug 30, 2023 · 0 comments
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

@AbdelrahmanElawady
Copy link
Contributor

This Bug Report affects these Traffic Control components:

  • Traffic Control Cache Config (t3c, formerly ORT)

What did you do?

  • Run CDN in a Box
  • Display ip_allow.yaml for mid-01 or mid-02 cache servers with docker-compose exec mid-01 cat /opt/trafficserver/etc/trafficserver/ip_allow.yaml

What did you expect to happen?

Single entries for 127.0.0.1 and ::1

What actually happened?

ip_allow:
  - apply: in
    ip_addrs: ::1
    action: allow
    methods:
      - ALL
  - apply: in
    ip_addrs: 127.0.0.1
    action: allow
    methods:
      - ALL
  ...
  - apply: in
    ip_addrs: 127.0.0.1
    action: allow
    methods:
      - ALL
  ...
  - apply: in
    ip_addrs: ::1
    action: allow
    methods:
      - ALL
@AbdelrahmanElawady AbdelrahmanElawady added bug something isn't working as intended 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 Aug 30, 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

No branches or pull requests

1 participant