placement api doesn't have tests to confirm unicode entry
Bug #1621605 reported by
Chris Dent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Chris Dent |
Bug Description
There are lots of tests of the placement api but none of them use unicode data. The only place where unicode is valid is in resource provider name so we should have some gabbi tests of that.
Changed in nova: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/365688 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=2e45b95a8f9 e0c1b4c7c985f01 b4928bd8818a07
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2e45b95a8f9e0c1 b4c7c985f01b492 8bd8818a07
Author: Chris Dent <email address hidden>
Date: Mon Sep 5 14:09:42 2016 +0000
[placement] Add some tests ensuring unicode resource provider info
Add some gabbi tests which demonstrate that it is possible to create
and query a resource provider that has a name that is outside the
bounds of ascii. The tests using a 4byte wide utf-8 character are left
as xfails because not all installations of mysql will support it.
Also confirm that if a unicode characters (uri-encoded or not) in
the uuid part of a resource providers path will result in the
expected 404 and not explode.
Closes-Bug: #1621605 b595fcc23c448c1 744972c319d
Change-Id: I3d906c3296aa28