Name validation too strict in the UI
Bug #1632631 reported by
Luca Miccini
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiri Tomasek |
Bug Description
Naming a node throws an error, regardless if the node in manually defined or imported via instackenv.json. Screenshot attached. It works if the name is in uppercase.
Ironic spec http://
Importing the nodes definition via CLI works as expected regardless of the upper/lower-case.
tags: | added: ui |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → ocata-1 |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
assignee: | nobody → Jiri Tomasek (jtomasek) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/385418
Review: https:/