Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

Creating a DSR: cannot update non-existent Delivery Service '' #7212

@zrhoffman

Description

@zrhoffman

This Bug Report affects these Traffic Control components:

  • Traffic Ops
  • Traffic Portal

Steps to reproduce:

  1. Enable Delivery Service Requests by setting .properties.dsRequests.enabled to true in traffic_portal/app/src/traffic_portal_properties.json
  2. Start CDN in a Box for Developers
    docker-compose up
  3. Go to https://localhost:444/#!/delivery-services/1?dsType=HTTP
  4. Set Display Name to new-display-name
  5. Press Update
  6. Choose Submit Request for Review and Deployment, enter My text as your comment, and press Submit

Expected behavior:

Traffic Ops successfully created a Delivery Service Request

Actual behavior

POSTing to /api/4.1/deliveryservice_requests responded with status code 400:

{
  "alerts": [
    {
      "text": "cannot update non-existent Delivery Service ''",
      "level": "error"
    }
  ]
}

Metadata

Metadata

Assignees

Labels

Traffic Opsrelated to Traffic OpsTraffic Portal v1related to Traffic Portal version 1medium impactimpacts a significant portion of a CDN, or has the potential to do soregression buga bug in existing functionality introduced by a new version

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions