You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2018. It is now read-only.
The edit delivery service UI allows multiple regexes with the same value in the order field. This causes unintended consequences downstream in Traffic Monitor, for example, when two HOST regexes are specified with order = 0. Modify Traffic Ops such that this UI allows only one regex per order value.
The text was updated successfully, but these errors were encountered:
The following query can be used to identify any delivery services configured with more than one regex with a given set number value:
select d.xml_id, dr.set_number, count(*) from deliveryservice d left join deliveryservice_regex dr on dr.deliveryservice = d.id join regex r on r.id = dr.regex where r.type=(select id from type where name='HOST_REGEXP') group by d.xml_id, dr.set_number having count(*) > 1;
Seems like it'd be ideal if the GUI didn't allow duplicate orders either, i.e. selected order numbers were removed via JS from other dropdowns. Or better yet, order was determined by dragging and dropping. But, not worth doing in 1.x.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The edit delivery service UI allows multiple regexes with the same value in the order field. This causes unintended consequences downstream in Traffic Monitor, for example, when two HOST regexes are specified with order = 0. Modify Traffic Ops such that this UI allows only one regex per order value.
The text was updated successfully, but these errors were encountered: