Do not validate next hop IP address for External Routes

Bug #1566004 reported by Sumit Naiksatam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Group Based Policy UI
Confirmed
Medium
ank

Bug Description

When creating an external segment, optional Extra Routes can be added. When adding an Extra Route, a destination needs to be provided but the next hop can be empty. Currently we validate this in the form. We can skip this validation, and if a junk value is provided (which is not an empty string), the backend will validate and throw an error.

Changed in group-based-policy-ui:
milestone: none → next
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.