yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #68616
[Bug 1655964] Re: the error message when a invalid instance name is given on an instance creation have a generic error
Horizon is simply forwarding on nova's (arguably misleading) error
message to the user. The proper place to fix this is in nova rather
than horizon. It is not appropriate for horizon to try to reverse-
engineer nova's errors to try to figure out what the "real" problem is.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1655964
Title:
the error message when a invalid instance name is given on an instance
creation have a generic error
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
Hello guys,
Here is my problem, when you give your instance a name with an
exclusive numeric last part, it fails, example :
cow.moo => ok
cow.moo3 => ok
cow => ok
cow. => ok
cow.333 => KO
cow.333. => KO
it's ok, because it's a conceptual choice :
https://bugs.launchpad.net/nova/+bug/1581977
RESP BODY: {"NeutronError": {"message": "Invalid input for dns_name.
Reason: 'myinstance6.4' not a valid PQDN or FQDN. Reason: TLD '4' must
not be all numeric.", "type": "HTTPBadRequest", "detail": ""}}
but when a customer gives a invalid instance name the instance creation fails and the standard error message "no valid host was found" appears in Horizon, which has nothing to do with it.
Could it be more interesting to get a more obvious error, in the same
format we could have when we forget to chose an image ? something like
"this instance name is not valid".
I tried to modify "create_instance.py" and "update_instance.py" myself
by simply add a regexp in
name = forms.CharField(label=_("Instance Name"), max_length=255)
but it isn't seems to be satisfactory at all.
If you have a better idea it could be great !
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1655964/+subscriptions
References