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

Automate Throwing invalid FQDN error while adding Infra Server #4891

Closed
kalroy opened this issue Mar 31, 2021 · 0 comments
Closed

Automate Throwing invalid FQDN error while adding Infra Server #4891

kalroy opened this issue Mar 31, 2021 · 0 comments
Assignees
Labels

Comments

@kalroy
Copy link
Collaborator

kalroy commented Mar 31, 2021

Describe the bug

Customer is attempting to add a Chef Infra Server to Chef Automate via the UI. The FQDN is coming back as Invalid, as the last bit of the FQDN is ".internal", which goes over the limit of up to 5 characters in length per the regex on that validator: ^(http://www.|https://www.|http://|https://)?[a-zA-Z0-9_]+([-.]{1}[a-zA-Z0-9]+).[a-zA-Z]{2,5}(:[0-9]{1,5})?(/.)?$

chef/customer-bugs#340

To Reproduce

Steps to reproduce the behavior:

  • Go to Automate UI > Infrastructure > Chef Servers and click Add Chef Server.
  • Enter in chef.internal tin FQDN field; anything else valid in other two fields
  • Observer the error "FQDN is Invalid" when submitted

Expected behavior

Automate should not throw "FQDN is invalid" error

Screenshots

Aha! Link: https://chef.aha.io/epics/SH-E-361

@kalroy kalroy added the bug 🐛 Something isn't working label Mar 31, 2021
@AnkurMundhra AnkurMundhra added Epic and removed bug 🐛 Something isn't working labels May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants