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.

Traffic Portal v1 - Quick Search does not work for second/layered profiles #7052

@tcfdev

Description

@tcfdev

This Bug Report affects these Traffic Control components:

  • Traffic Portal

Current behavior:

Open the server table in Traffic Portal. At the top of the page is the "Quick search" input field. The quick search does not filter / show servers if the input is the second/layered profile.

Expected behavior:

If a server were to have "PRIMARY_PROFILE" assigned as the first profile, it will be filtered and show correctly, as expected. Additionally if you were to create and add a "SECONDARY_PROFILE" to the same server(s) the Quick search would display said server(s).

Steps to reproduce:

Create a server (or use existing). Assign a profile ("PRIMARY_PROFILE" for example). This should be the first and only profile assigned to the server. You can verify that Quick search on the Configure->Servers page works for said profile.

Then create and/or add another profile (say "SECONDARY_PROFILE"). Then add this profile to the same server such that it has both PRIMARY and SECONDARY profiles assigned. Go to the Configure->Servers page and attempt to Quick Search on "SECONDARY_PROFILE" and the list will be empty

Metadata

Metadata

Assignees

Labels

Traffic Portal v1related to Traffic Portal version 1bugsomething isn't working as intendedlow difficultythe estimated level of effort to resolve this issue is lowlow impactaffects only a small portion of a CDN, and cannot itself break one

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions