You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/08/13 16:46:47 UTC
[GitHub] mitchell852 edited a comment on issue #2657: TO API: unable to
write a null or blank value to IPv6
mitchell852 edited a comment on issue #2657: TO API: unable to write a null or blank value to IPv6
URL: https://github.com/apache/trafficcontrol/issues/2657#issuecomment-412585025
if my memory serves me correctly, ipv6 addresses must be unique per profile. for example
server 1 has profile A which has ipv6=2001:aaaa:bbbb:cccc::
server 2 has profile B which has ipv6=2001:aaaa:bbbb:cccc::
^^ this is fine but if
server 3 has profile B which has ipv6=2001:aaaa:bbbb:cccc:: <-- that won't work.
anyhow, my guess is that this constraint is kicking in on a null or blank value. i.e.
server 1 has profile A which has ipv6=null
server 2 has profile A which has ipv6=null <-- the system thinks that null is already taken so it's throwing the unique constraint error which it obviously should not
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services