yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1117384] Re: Cinder does not fill in Display Name on creation

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Fri, 15 Mar 2013 13:41:24 -0000
Reply-to: Bug 1117384 <1117384@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
** Changed in: cinder
       Status: Fix Committed => Fix Released

** Changed in: cinder
    Milestone: None => grizzly-rc1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1117384

Title:
  Cinder does not fill in Display Name on creation

Status in Cinder:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Invalid
Status in Openstack Ubuntu Testing:
  New

Bug description:
  When creating a block storage device, Cinder should fill in the
  volume's display name prior to trying to create the volume. Currently:

  cinder create --display-name Test 1
  +----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Property |                                                                                                                                        Value                                                                                                                                        |
  +----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  |    id    |                                                                                                                         3a5d96b3-d134-485a-bc09-30a9d869d9e6                                                                                                                        |
  |  links   | [{u'href': u'http://10.150.0.55:8776/v2/951f2ba7f0c44ae6a38ea7a9db3897b2/volumes/3a5d96b3-d134-485a-bc09-30a9d869d9e6', u'rel': u'self'}, {u'href': u'http://10.150.0.55:8776/951f2ba7f0c44ae6a38ea7a9db3897b2/volumes/3a5d96b3-d134-485a-bc09-30a9d869d9e6', u'rel': u'bookmark'}] |
  |   name   |                                                                                                                                         Test                                                                                                                                        |
  +----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

  cinder list
  +--------------------------------------+----------+--------------+------+-------------+----------+-------------+
  |                  ID                  |  Status  | Display Name | Size | Volume Type | Bootable | Attached to |
  +--------------------------------------+----------+--------------+------+-------------+----------+-------------+
  | 3a5d96b3-d134-485a-bc09-30a9d869d9e6 | creating |              |  1   |     None    |          |             |
  +--------------------------------------+----------+--------------+------+-------------+----------+-------------+

  
  This causes Horizon to throw an error when browsing to the Volumes page. I'm sure this is a bug on both sides (aka Horizon shouldn't require a name to display a volume). I noticed this when I was having issues with my Cinder storage service, so the Cinder scheduler couldn't create a volume:
  2013-02-06 10:35:25 WARNING cinder.scheduler.manager [req-eb7d7f46-c5ce-490c-b8ff-aab64a2ede02 15f9ce750c9f4c20b86c9e3e095c27ce 951f2ba7f0c44ae6a38ea7a9db3897b2] Failed to schedule_create_volume: No valid host was found. Is the appropriate service running?

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