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

Conversation

@ocket8888
Copy link
Contributor

This was causing display issues because the table was inheriting from the normal DS table, which assumes APIv5 DS object structure.


Which Traffic Control components are affected by this PR?

  • Traffic Portal

What is the best way to verify this PR?

Go to a server with an assigned, active DS, and make sure that in the deliveryservices table for that server said DS is displayed as ACTIVE and not INACTIVE.

If this is a bugfix, which Traffic Control versions contained the bug?

  • master

PR submission checklist

  • This PR doesn't need tests
  • This PR doesn't need documentation
  • This PR has a CHANGELOG.md entry
  • This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

@ocket8888 ocket8888 added Traffic Portal v1 related to Traffic Portal version 1 low impact affects only a small portion of a CDN, and cannot itself break one regression bug a bug in existing functionality introduced by a new version labels May 8, 2023
Copy link
Contributor

@rimashah25 rimashah25 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Tested it local and an ACTIVE DS does appear as ACTIVE when assigned to a server instead of INACTIVE.
TP Tests failure are not related to this PR.

@rimashah25 rimashah25 merged commit c6b211c into apache:master May 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

low impact affects only a small portion of a CDN, and cannot itself break one regression bug a bug in existing functionality introduced by a new version Traffic Portal v1 related to Traffic Portal version 1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants