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 was archived by the owner on Nov 24, 2025. It is now read-only.
This Bug Report affects these Traffic Control components:
Traffic Ops
What did you do?
When creating servers on the same profile with the same service address in range /32 for IPv4 or /128 for IPv6 (i.e. 1.1.1.1/32) it works fine. However, other ranges fail as servers with the same service address are not allowed
To reproduce:
Run Traffic Ops
Create server with service address ending in /32
Create another with the same address it won't fail
This Bug Report affects these Traffic Control components:
What did you do?
When creating servers on the same profile with the same service address in range /32 for IPv4 or /128 for IPv6 (i.e. 1.1.1.1/32) it works fine. However, other ranges fail as servers with the same service address are not allowed
To reproduce:
This is because we are using
inetPostgres type to represent IPs and it omits the mask part if it's a single host: https://www.postgresql.org/docs/current/datatype-net-types.html#DATATYPE-INETSo upon validation the IP stored in DB does not match what's in the request and it gets created with no errors.
What did you expect to happen?
Fail with error indicating that servers on the same profile can't share the same service address for subnet /32.
What actually happened?
Servers were created fine.