RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1258014 - oslo_config != oslo.config
Summary: oslo_config != oslo.config
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: python-oslo-config
Version: Kilo
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: Kilo
Assignee: hguemar
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-28 16:12 UTC by Kevin Fox
Modified: 2016-05-19 15:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
RDO kilo 2015.1.1 on SL7.1
Last Closed: 2016-05-19 15:57:36 UTC
Embargoed:


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

Description Kevin Fox 2015-08-28 16:12:54 UTC
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 15:57:36 UTC
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.