Cannot specify a version to 'glance-manage version_control'
Bug #966242 reported by
Mark McLoughlin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
Mark McLoughlin |
Bug Description
'glance-manage version_control' takes an existing unversioned database and associations it with a migration version.
However, you can't actually specify a migration version, so it defaults to zero. This only makes sense for a completely empty database.
See bug #966241 for why you might a unversioned DB in the first place.
Changed in glance: | |
assignee: | nobody → Mark McLoughlin (markmc) |
description: | updated |
tags: | added: essex-rc-potential |
Changed in glance: | |
importance: | Undecided → Medium |
Changed in glance: | |
milestone: | none → essex-rc2 |
tags: | removed: essex-rc-potential |
Changed in glance: | |
milestone: | essex-rc2 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/5862
Review: https:/