This bug was fixed in the package cinder - 1:2013.1.1-0ubuntu1

---------------
cinder (1:2013.1.1-0ubuntu1) raring-proposed; urgency=low

  * Resynchronize with stable/grizzly (a4856c4e) (LP: #1179626):
    - [995a310] Can't specify custom backend-name for HP/3par driver
      LP: 1175222
    - [319f712] SolidFire driver can't be used with extra-specs as in the past
      LP: 1167141
    - [817eac8] 3par driver not synchronize causing duplicate hostname error
      LP: 1172503
    - [2e3c1cd] backup-delete removes backup from database LP: 1169943
    - [2f72682] nexenta driver doesn't report volume stats LP: 1166607
    - [6221a0e] ThinLVM driver fails due to get_stats LP: 1166572
    - [93247d2] Deleted snapshots still counting against quota  LP: 1173365
    - [6008be0] Multibackend config issue in cinder-volume LP: 1169928
    - [b8de829] glusterfs driver doesn't report volume stats LP: 1164038
    - [59f11c9] reschedule_or_reraise in cinder.volume.manager eats exception on
      base LVM driver LP: 1159027
    - [9318ffc] cinder-manage backup list is broken since we switched to uuids
      for backups LP: 1164922
    - [ba41b68] Logging configured incorrectly in cinder-all LP: 1161038
    - [2113fe1] sql_connection not marked secret LP: 1160680
    - [e1c153c] Error re-scheduling volume creation LP: 1164857
    - [5521cae] Remove unused tools/rfc.sh
    - [fed7c92] backup tests fail due to format errors in messages  LP: 1166600
 -- Adam Gandelman <[email protected]>   Tue, 14 May 2013 07:49:04 -0700

** Changed in: quantum (Ubuntu Raring)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179626

Title:
  Meta bug for tracking Openstack 2013.1.1 Stable Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1179626/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to