db_sync throws CRITICAL KeyError: <VerNum(1)>
Bug #1314340 reported by
Justin Shepherd
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Morgan Fainberg |
Bug Description
On Ubuntu14.04
# cd /opt
# git clone https:/
# cd keystone
# virtualenv .venv
# tools/with_venv.sh pip install -r requirements.txt
Successfully installed pbr WebOb eventlet greenlet netaddr PasteDeploy Paste Routes six SQLAlchemy sqlalchemy-migrate passlib lxml iso8601 python-
# tools/with_venv.sh bin/keystone-manage db_version
0
# tools/with_venv.sh bin/keystone-manage db_sync
2014-04-29 18:24:15.251 30096 CRITICAL keystone [-] KeyError: <VerNum(1)>
description: | updated |
Changed in keystone: | |
importance: | Undecided → Medium |
assignee: | nobody → Morgan Fainberg (mdrnstm) |
milestone: | none → juno-1 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
# git show a5cc9dd630d7de2 5fdf67f2ab
commit 7a041d726339cea
Merge: e170988 7e4aab3
Author: Jenkins <email address hidden>
Date: Tue Apr 29 16:46:20 2014 +0000
Merge "Ignore broken endpoints in get_v3_catalog"