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

Portal: Cannot use "0" as a TTL value for Static DNS entries #3400

Closed
smalenfant opened this issue Mar 12, 2019 · 1 comment · Fixed by #4955
Closed

Portal: Cannot use "0" as a TTL value for Static DNS entries #3400

smalenfant opened this issue Mar 12, 2019 · 1 comment · Fixed by #4955
Labels
help wanted regression bug a bug in existing functionality introduced by a new version Traffic Ops related to Traffic Ops

Comments

@smalenfant
Copy link
Contributor

This was possible with Traffic Ops although "0" now reports 'ttl' cannot be blank. TTL of 0 is valid number.

@smalenfant smalenfant added the Traffic Portal v1 related to Traffic Portal version 1 label Mar 12, 2019
@rawlinp rawlinp added bug something isn't working as intended Traffic Ops related to Traffic Ops regression bug a bug in existing functionality introduced by a new version and removed Traffic Portal v1 related to Traffic Portal version 1 labels Mar 12, 2019
@rawlinp
Copy link
Contributor

rawlinp commented Mar 12, 2019

This seems to be an API validation issue in traffic_ops_golang, rather than form validation in TP. TP allows 0 in the form, but the API returns an error. @smalenfant do you think this should be a backport candidate for 3.0.1?

@mitchell852 mitchell852 removed the bug something isn't working as intended label Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted regression bug a bug in existing functionality introduced by a new version Traffic Ops related to Traffic Ops
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants