-
Notifications
You must be signed in to change notification settings - Fork 314
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
Search Domains Are Not Supported #1993
Comments
@ibinshtok Could you please triage this? |
@MMaiero yes, I recreated this exception if "Search Domain" is a name that can't be resolved (i.e. google, instead of google.com or IP address). |
Please note that search domains were broken, see #923. Should we just disable or remove the field from the Web UI? |
Well the tests asks you to add set all other kinds of settings from your local settings. This is one of them. So maybe adding that field to the test explicitly makes sense.
I think fixing the issue would be the appropriate action. |
@ibinshtok are you confident in a proper fix to this issue and to #923? |
As agreed in the weekly call, let's start removing the |
Temporary covered by PR #2023. Let's keep this issue open in order to provide a proper fix in one of the next releases. |
This issue is stale because it has been open for 60 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
While testing NET-ETH0-003 on Fedora I ran into the follow error when applying the configuration:
Looking at the exception I do think that the search domain field validation is broken:
The entered information is actually part of hostname, not a hostname itself and thus cannot necessarily be looked up.
The text was updated successfully, but these errors were encountered: