Bug 1258014 - oslo_config != oslo.config
oslo_config != oslo.config
Status: CLOSED EOL
Product: RDO
Classification: Community
Component: python-oslo-config (Show other bugs)
Kilo
x86_64 Linux
unspecified Severity high
: ---
: Kilo
Assigned To: hguemar
Shai Revivo
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-28 12:12 EDT by Kevin Fox
Modified: 2016-05-19 11:57 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
RDO kilo 2015.1.1 on SL7.1
Last Closed: 2016-05-19 11:57:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patches to make things work. (2.21 KB, application/x-gzip)
2015-08-28 12:12 EDT, Kevin Fox
no flags Details

  None (edit)
Description Kevin Fox 2015-08-28 12:12:54 EDT
Created attachment 1068070 [details]
patches to make things work.

Description of problem:

Had upgraded from juno -> kilo and things were very broken. Had done another cluster from juno -> kilo rdo 2015.1.0 and didn't see this issue.

Multiple services, multiple processes each were broken. Notably Cinder, Horizon, Ceilometer and Trove.

Long story short, it turns out some of the packages are mixing importing oslo.config and oslo_config, either directly or via oslo.messaging importing oslo_messinag that imports oslo_config.

Since oslo_config and oslo.config are different namespaces config entries get registered in the wrong place, then break when the process goes and looks up the values in the other namespace.

I've attached the set of patches I had to apply to get the cloud starting again.

Version-Release number of selected component (if applicable):
2015.1.1

How reproducible:
100%

Steps to Reproduce:
1. Install the packages

Actual results:
Stuff wont start

Expected results:
Stuff starts
Comment 2 Chandan Kumar 2016-05-19 11:57:36 EDT
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.

Note You need to log in before you can comment on or make changes to this bug.