OK, finally twigged that in order to reproduce this issue, the starting point version must be 9 as opposed to zero.
Whereas the instructions as stated will cause the version field in the migrate_version table to be set to zero, as the the following commit to allow a specific version be specified has not yet been applied to the stable diablo branch (and isn't directly applicable):
OK, finally twigged that in order to reproduce this issue, the starting point version must be 9 as opposed to zero.
Whereas the instructions as stated will cause the version field in the migrate_version table to be set to zero, as the the following commit to allow a specific version be specified has not yet been applied to the stable diablo branch (and isn't directly applicable):
https:/ /github. com/openstack/ glance/ commit/ da66de06
Otherwise the Essex upgrade from version 0 fails with:
http:// paste.openstack .org/show/ 12345/
I've backported the "Allow specifying the current version in 'glance-manage version_control'" commit to diablo stable:
https:/ /review. openstack. org/6077
and with that patch in place, the bug is reproducible if the target version is explicitly set to 9:
sudo ./tools/ with_venv. sh bin/glance-manage version_control 9 --config-file ./etc/glance- registry. conf
before switching to the Essex branch.