You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
GET /api/3.0/servers?dsId={{id}} does not return ORG servers directly assigned to the DS if:
a topology is assigned to the DS and
one ore more ORG servers are directly assigned to the DS and
the ds requires server capabilities that the ORG server(s) does not have
In fact, I don't even think you are allowed to assign server capabilities to an ORG so you'd never be able to accomplish #3.
Note: this issue also seems to affect ORT/atstccfg as the applicable line for the ds in parent.config file is missing altogether when the only parent(s) are ORG servers that don't have the necessary server capability. ORG servers are exempt from server capability filtering and should ALWAYS show up for a ds in which they are directly assigned (server capability or not) but looks like this was addressed with PR #5383
Expected behavior:
If I recall correctly, server capabilities are not applicable to ORG servers, therefore, for a ds with a topology AND required server capabilities:
a. show all the servers in the topology in the same cdn as the ds
b. minus the ones w/o the ds's required server caps...except for ORG servers which server caps do not apply to (if assigned, show ORG servers regardless)
Minimal reproduction of the problem with instructions:
I'm submitting a ...
Traffic Control components affected ...
Current behavior:
GET /api/3.0/servers?dsId={{id}} does not return ORG servers directly assigned to the DS if:
In fact, I don't even think you are allowed to assign server capabilities to an ORG so you'd never be able to accomplish #3.
Note: this issue also seems to affect ORT/atstccfg as the applicable line for the ds in parent.config file is missing altogether when the only parent(s) are ORG servers that don't have the necessary server capability. ORG servers are exempt from server capability filtering and should ALWAYS show up for a ds in which they are directly assigned (server capability or not) but looks like this was addressed with PR #5383
Expected behavior:
If I recall correctly, server capabilities are not applicable to ORG servers, therefore, for a ds with a topology AND required server capabilities:
a. show all the servers in the topology in the same cdn as the ds
b. minus the ones w/o the ds's required server caps...except for ORG servers which server caps do not apply to (if assigned, show ORG servers regardless)
Minimal reproduction of the problem with instructions: