-
Notifications
You must be signed in to change notification settings - Fork 344
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
t3c parent.config fix for MSO non-topo mid cache group no parent cache groups #7471
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7471 +/- ##
============================================
- Coverage 29.28% 27.45% -1.83%
Complexity 98 98
============================================
Files 782 685 -97
Lines 81860 77786 -4074
Branches 784 90 -694
============================================
- Hits 23970 21358 -2612
+ Misses 55825 54416 -1409
+ Partials 2065 2012 -53
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 97 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a couple small things/questions but should be approved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, tests pass! The CiaB failure is unrelated.
Bug fix for #7137 (create topology on the fly for non topo delivery services)
Case:
delivery service with MSO but no topology.
mid cache group does not have primary and secondary parents assigned.
origins belong to any number of origin cache groups.
In this case the origin from only the fist encountered cache group was getting pulled into parent.config
Which Traffic Control components are affected by this PR?
t3c
, formerly ORT)What is the best way to verify this PR?
Create delivery service, MSO non topo. Ensure origins belong to different origin cache groups. ensure the mid cache group has neither primary nor secondary cache groups assigned. T3C run parent.config should
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist