Project

General

Profile

Actions

Bug #4602

open

misleading error regarding host name when creating a host

Added by Alissa Bonas about 10 years ago. Updated almost 10 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Host creation
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When trying to create a new host, try to input a name , something like "host1".
Click 'submit'.
The system automatically adds a period (.) after "host1", so the name becomes "host1.",
and it displays this error: "must not include periods and is invalid"

1. If the system adds the period by itself, it should not fail as a wrong input.
2. It's not clear from user's point of view how to fix it if the system adds the period by itself. (and why this character is added anyway)
If a domain is needed, it should be clear from a message/tooltip that fqdn is expected as part of host name.
3. What means "and is invalid" - what else is wrong?

Please clarify the error message/make this flow more user friendly.
thank you


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #4680: Regression: Hosts with no domain cannot be created when Unattended=falseClosedGreg Sutcliffe03/17/2014Actions
Is duplicate of Foreman - Bug #5834: Hosts: "." in the name is invalid - user is told this but the UI adds one anyway.ClosedJoseph Magen05/20/2014Actions
Actions #1

Updated by Dominic Cleal about 10 years ago

  • Category set to Host creation

Do you have unattended in config/settings.yaml set to true or false?

Actions #2

Updated by Alissa Bonas about 10 years ago

it's set to true:
:unattended: true

Actions #3

Updated by Oscar Ferrer about 10 years ago

The same happens to me in one customer. By I have :unattended: set to false.

Actions #4

Updated by Oscar Ferrer about 10 years ago

Sorry. I meant 'But I have :unattended: set to false'

Actions #5

Updated by Greg Sutcliffe about 10 years ago

  • Related to Bug #4680: Regression: Hosts with no domain cannot be created when Unattended=false added
Actions #6

Updated by Greg Sutcliffe about 10 years ago

Oscar, I've created http://projects.theforeman.org/issues/4680 for your issue as it's not quite the same as this one.

Actions #7

Updated by Oscar Ferrer about 10 years ago

Big Thanks. This solves both issues for me.

Actions #8

Updated by Dominic Cleal almost 10 years ago

  • Is duplicate of Bug #5834: Hosts: "." in the name is invalid - user is told this but the UI adds one anyway. added
Actions #9

Updated by Dominic Cleal almost 10 years ago

The misleading error message has been fixed in #5834, so it no longer adds a period and then complains about it being there. However I think your point about "is invalid" is erm, valid, so will leave this open. The requirement for an FQDN and/or domain should be clearer, particularly as the domain is on another tab.

Actions

Also available in: Atom PDF