Error when you try to rename Hostname: deque(['hostname']): u'node-1dsfvlkdfl;vkdfl;vkdl;fvkd;' does not match...

[Anastasia Palkina]

Steps to reproduce:
1. Create new environment with default settings
2. Add some nodes
3. Click on cogwheel on one of nodes
4. Click on hostname and try to rename it with ";" symbol or with Cyrillic or just enter very long name
5. Error appears (see screens)

Expected result: clear human readable explanation of hostname restrictions.

ISO #172, 9.0

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Dmitry Pyzhov (dpyzhov)]

I agree that error message is not very clear. However it contains all needed information. Setting medium priority and moving to 10.0 release.

[Dmitry Pyzhov (dpyzhov)]

Also hostname can contain only limited number of characters:
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 (.)
https://tools.ietf.org/html/rfc952

I'll update bug description

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/326248

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/326248
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=17b4878e601f56a89a956b5be978189dc737ae43
Submitter: Jenkins
Branch: master

commit 17b4878e601f56a89a956b5be978189dc737ae43
Author: Georgy Kibardin <email address hidden>
Date: Tue Jun 7 09:29:09 2016 +0300

    Human friendly message for invalid hostname

    Unfortuanately json schema validators don't allow specifying more human
    friendly message as an alternative to complex regex patterns. So, the
    only way is to perform hostname validation "manually".

    Change-Id: Iee1717a3034fe4e33569fbeff6553b5bc949605e
    Closes-Bug: #1567875