oslo.db should >= 1.4.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
High
|
stanzgy |
Bug Description
designate: 6b75da0#master (2015-01-14 23:39:30 +0000)
My devstack designate-manage command broken that lacks subcommand powerdns, pool-manager-cache and database.
Tried reinstall designate but not worked.
$ sudo designate-manage
usage: designate [-h] [--config-dir DIR] [--config-file PATH] [--debug]
designate: error: too few arguments
After a debug with ipdb, I found this is due to commit c6a7cbb which moves oslo.db out of "oslo" namespace but not updates the version of oslo.db.
My devstack has already installed the 1.3.0 oslo.db which matches the requirements.txt will not get upgraded during reinstalling designate.
When I manually installed lastest 1.4.1 oslo.db, designate-manage works good.
ipdb result:
...
> /usr/local/
156 LOG.debug('found extension %r', ep)
--> 157 try:
158 ext = self._load_
ipdb> ep
EntryPoint.
...
> /usr/local/
161 invoke_kwds,
--> 162 verify_
163 )
ipdb>
ImportError: 'No module named oslo_db.
requirement.txt
oslo.db>=1.3.0 # Apache-2.0
oslo.db release notes:
1.4.0:
...
Move files out of the namespace package
description: | updated |
summary: |
- designate-manage commands broken + oslo.db should >= 1.4.0 |
Changed in designate: | |
status: | Fix Committed → Fix Released |
Changed in designate: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/147407
Review: https:/