I am not sure if this is a bug, we could replace the dot(s) in the host name
with a different char, for example a "_" but then the user will lose the option
to define a hostname as a FQDN.
And according to the rfc952:
' A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
sign (-), and period (.). Note that periods are only allowed when
they serve to delimit components of "domain style names"'
So if the user uses a period it should know that it is allowed only to delimit
a domain name and it has to be a valid one.
I am going to mark it as invalid, please let me know if you are not happy about
this decision.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1581977
Title:
Invalid input for dns_name when spawning instance with .number at the
end
Status in OpenStack Compute (nova):
Invalid
Bug description:
When attempting to deploy an instance with a name which ends in dot
<number> (e.g. .123, as in an all-numeric TLD) or simply a name that,
after conversion to dns_name, ends as .<number>, nova conductor fails
with the following error:
2016-05-15 13:15:04.824 ERROR nova.scheduler.utils [req-4ce865cd-e75b-
4de8-889a-ed7fc7fece18 admin demo] [instance:
c4333432-f0f8-4413-82e8-7f12cdf3b5c8] Error from last host:
silpixa00394065 (node silpixa00394065): [u'Traceback (most recent call
last):\n', u' File "/opt/stack/nova/nova/compute/manager.py", line
1926, in _do_build_and_run_instance\n filter_properties)\n', u'
File "/opt/stack/nova/nova/compute/manager.py", line 2116, in
_build_and_run_instance\n instance_uuid=instance.uuid,
reason=six.text_type(e))\n', u"RescheduledException: Build of instance
c4333432-f0f8-4413-82e8-7f12cdf3b5c8 was re-scheduled: Invalid input
for dns_name. Reason: 'networking-ovn-ubuntu-16.04' not a valid PQDN
or FQDN. Reason: TLD '04' must not be all numeric.\nNeutron server
returns request_ids: ['req-7317c3e3-2875-4073-8076-40e944845b69']\n"]
This throws one instance of the infamous Horizon message: Error: No
valid host was found. There are not enough hosts available.
This issue was observed using stable/mitaka via DevStack (nova commit
fb3f1706c68ea5b58f05ea810c6339f2449959de).
In the above example, the instance name is "networking-ovn (Ubuntu
16.04)", which resulted in an attempted dns_name="networking-ovn-
ubuntu-16.04", where the 04 was interpreted as a TLD and,
consequently, an invalid TLD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1581977/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
