TO prevents assigning ORG servers to topology-based delivery services #6392
Assignees
Labels
bug
something isn't working as intended
high impact
impacts the basic function, deployment, or operation of a CDN
low difficulty
the estimated level of effort to resolve this issue is low
Traffic Ops
related to Traffic Ops
Comments
|
FYI I labelled this as medium impact since it has a workaround but could be very tedious if you had to use the workaround for any more than just a few delivery services. |
|
it seems it has another "impact". we're seeing a bug where same message: when trying to "offline" a server in a cache group that is used by a topology used by an MSO ds thus preventing us to offline a server that needs to be offlined. enough to bump it to "high impact" @rawlinp ? then again, this appears to have a work-around too... |
|
Yeah, I agree, we should be able to offline servers for MSO topology-based DSes as well. Since that is a much more common use case, I think that warrants high impact. |
rawlinp
added a commit
to rawlinp/trafficcontrol
that referenced
this issue
Dec 6, 2021
In order to prevent accidental ouages, TO currently has validation which prevents things like deleting the last server that is assigned to an active delivery service. However, this validation ignored the fact that delivery services can now be assigned to a topology instead of using DSS assignments. This prevents a number of actually valid things, such as safely setting caches to ADMIN_DOWN, assigning MSO servers to topology-based DSes, and removing legacy DSS EDGE assignments from topology-based DSes. This fixes that validation in order to take topology-based DSes into account. Closes: apache#6392
4 tasks
zrhoffman
pushed a commit
that referenced
this issue
Dec 6, 2021
…6408) * Take topology-based DSes into account when checking DSS assignments In order to prevent accidental ouages, TO currently has validation which prevents things like deleting the last server that is assigned to an active delivery service. However, this validation ignored the fact that delivery services can now be assigned to a topology instead of using DSS assignments. This prevents a number of actually valid things, such as safely setting caches to ADMIN_DOWN, assigning MSO servers to topology-based DSes, and removing legacy DSS EDGE assignments from topology-based DSes. This fixes that validation in order to take topology-based DSes into account. Closes: #6392 * Fix GROUP BY * Add TO API test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This Bug Report affects these Traffic Control components:
Current behavior:
If you attempt to assign ORG servers to a topology-based delivery service (if you are setting it up for MSO, for instance), and it has pre-existing DS-server EDGE assignments, TO returns the following error:
Expected behavior:
TO should allow you to assign ORG servers to a topology-based DS that has no DS-server EDGE assignments.
Steps to reproduce:
In TP, go to a topology-based delivery service that doesn't have any pre-existing EDGE server assignments, then More > Manage Servers > More > Assign ORG Servers > select an ORG server to assign > Submit
The text was updated successfully, but these errors were encountered: