PSARC/2014/207 OpenStack Glance Update to Havana
PSARC/2014/208 OpenStack Cinder Update to Havana
PSARC/2014/209 OpenStack Keystone Update to Havana
PSARC/2014/210 OpenStack Nova Update to Havana
18416146 Neutron agents (L3 and DHCP) should cleanup resources when they are disabled
18562372 Failed to create a new project under Horizon
18645763 ZFSSA Cinder Driver support
18686327 evs agent silently ignores user-specified pool allocation ranges
18702697 fibre channel volumes should be supported in the cinder volume driver
18734289 nova won't terminate failed kz deployments
18738371 cinder-volume:setup should account for commented-out zfs_volume_base
18738374 cinder-volume:setup should check for existence of configuration file
18826190 nova-compute fails due to nova.utils.to_bytes
18855698 Update OpenStack to Havana 2013.2.3
18855710 Update python-cinderclient to 1.0.9
18855743 Update python-keystoneclient to 0.8.0
18855754 Update python-neutronclient to 2.3.4
18855764 Update python-novaclient to 2.17.0
18855793 Update python-swiftclient to 2.1.0
18856992 External networks can be deleted even when floating IP addresses are in use
18857784 bake in some more openstack configuration
18884923 Incorrect locale facets in python modules for openstack
18913890 the error in _get_view_and_lun may cause the failure of deleting volumes
18943044 Disable 'Security Groups' tab in Horizon dashboard
Although the following patch has been addressed in Icehouse 2014.1, it
still has not yet been released for Havana. It has been modified to
apply cleanly into our current Havana implementation
commit 3badd1ffbe8796d27b924f882ed05b8d3f4f0f11
Author: Dan Prince <[email protected]>
Date: Tue Dec 10 14:51:32 2013 -0500
Lazy log the fixed_key warnings
Cinder currently spews quite a bit of WARNINGs like this with
the default settings:
WARNING cinder.keymgr.conf_key_mgr [-] config option keymgr.fixed_key
has not been defined: some operations may fail unexpectedly
Many users may not be using features that require key manager...
so logging the WARNING message a bit more lazily seems reasonable.
Change-Id: I5ab72285c7d4bc2ec3196dd94fabf977b3a4ebaf
Closes-bug: 1252512
diff --git a/cinder/keymgr/conf_key_mgr.py b/cinder/keymgr/conf_key_mgr.py
index f000c44..ee4fbc3 100644
--- cinder-2013.2.3/cinder/keymgr/conf_key_mgr.py.~2~ 2014-05-29 11:02:58.846311952 -0700
+++ cinder-2013.2.3/cinder/keymgr/conf_key_mgr.py 2014-05-29 11:02:58.855843284 -0700
@@ -67,9 +67,6 @@
super(ConfKeyManager, self).__init__()
self.key_id = '00000000-0000-0000-0000-000000000000'
- if CONF.keymgr.fixed_key is None:
- LOG.warn(_('config option keymgr.fixed_key has not been defined: '
- 'some operations may fail unexpectedly'))
def _generate_key(self, **kwargs):
_hex = self._generate_hex_key(**kwargs)
@@ -78,6 +75,8 @@
def _generate_hex_key(self, **kwargs):
if CONF.keymgr.fixed_key is None:
+ LOG.warn(_('config option keymgr.fixed_key has not been defined: '
+ 'some operations may fail unexpectedly'))
raise ValueError(_('keymgr.fixed_key not defined'))
return CONF.keymgr.fixed_key