← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1621605] Re: placement api doesn't have tests to confirm unicode entry

 

Reviewed:  https://review.openstack.org/365688
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=2e45b95a8f9e0c1b4c7c985f01b4928bd8818a07
Submitter: Jenkins
Branch:    master

commit 2e45b95a8f9e0c1b4c7c985f01b4928bd8818a07
Author: Chris Dent <cdent@xxxxxxxxxxxxx>
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
    Change-Id: I3d906c3296aa28b595fcc23c448c1744972c319d


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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/1621605

Title:
  placement api doesn't have tests to confirm unicode entry

Status in OpenStack Compute (nova):
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1621605/+subscriptions


References