Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot update any regex in Traffic Ops/ Traffic Portal #5296

Closed
srijeet0406 opened this issue Nov 17, 2020 · 3 comments · Fixed by #5297
Closed

Cannot update any regex in Traffic Ops/ Traffic Portal #5296

srijeet0406 opened this issue Nov 17, 2020 · 3 comments · Fixed by #5297
Assignees
Labels
bug something isn't working as intended medium impact impacts a significant portion of a CDN, or has the potential to do so Traffic Ops related to Traffic Ops

Comments

@srijeet0406
Copy link
Contributor

I'm submitting a ...

  • bug report

Traffic Control components affected ...

  • CDN in a Box
  • Traffic Ops

Current behavior:

If you have a regex for a delivery service, you cannot update it.

Expected behavior:

All regexes should be updateable, with the exception of the following:
1.) If the regex in question has set number 0 and type HOST_REGEXP
2.) If there already is another regex with the same order.

Minimal reproduction of the problem with instructions:

Go to Traffic Portal.
In an existing or new delivery service, try changing the pattern of a regex thats associated with this DS.
You'll notice that it fails stating that there already is another regex with the same order.
This is incorrect, because "updating" something means that it has to be already available.

Anything else:

@srijeet0406 srijeet0406 added the bug something isn't working as intended label Nov 17, 2020
@mitchell852
Copy link
Member

so basically if you are trying to update:

my.regex.com, order=1

it's failing because it thinks something else is already in position 1? which is not true. nothing else is in postion 1 except for my.regex.com?

@mitchell852 mitchell852 added the Traffic Ops related to Traffic Ops label Nov 18, 2020
@srijeet0406
Copy link
Contributor Author

Yes, thats correct. So basically all updates are disallowed currently, which is obviously wrong.

@mitchell852
Copy link
Member

fyi as a workaround, the user can simply delete/create to update :)

@mitchell852 mitchell852 added the low impact affects only a small portion of a CDN, and cannot itself break one label Dec 1, 2020
@mitchell852 mitchell852 added medium impact impacts a significant portion of a CDN, or has the potential to do so and removed low impact affects only a small portion of a CDN, and cannot itself break one labels Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended medium impact impacts a significant portion of a CDN, or has the potential to do so Traffic Ops related to Traffic Ops
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants