Incorrect error message when creating a DS with insufficient Tenancy #7321
Labels
bug
something isn't working as intended
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
Traffic Ops
related to Traffic Ops
This Bug Report affects these Traffic Control components:
Current behavior:
When creating a new Delivery Service, if
tenantId
is omitted (and probably also in the case that it's simply outside of the user's Tenant's access), Traffic Ops will respond with a 500 Internal Server Error after failing to check Tenancy.Expected behavior:
The issue is with the client's request, so the response should be a 400 Bad Request along with an error message telling me what I did wrong.
Steps to reproduce:
Assuming
8
is the ID ofANY_MAP
and no DS with the XMLID "test" already exists:topost -kpa 3.1 deliveryservices '{"xmlId": "test", "displayName": "test", "protocol": 0, "typeId": 8, "dscp": 0}'
The text was updated successfully, but these errors were encountered: