I can grab the right db_version when I back up to the commit before the Token Revocation work. Steps to reproduce:
1.) lbragstad@precise64:/opt/stack/keystone/bin$ git checkout 1ba6c53bade4679d940fa311800d29038cf26358
2.) lbragstad@precise64:/opt/stack/keystone/bin$ ./keystone-manage db_version
2014-03-08 15:29:14.757 WARNING keystone.openstack.common.db.sqlalchemy.session [-] This application has not enabled MySQL traditional mode, which means silent data corruption may occur. Please encourage the application developers to enable this mode.
43
I can grab the right db_version when I back up to the commit before the Token Revocation work. Steps to reproduce:
1.) lbragstad@ precise64: /opt/stack/ keystone/ bin$ git checkout 1ba6c53bade4679 d940fa311800d29 038cf26358 precise64: /opt/stack/ keystone/ bin$ ./keystone-manage db_version openstack. common. db.sqlalchemy. session [-] This application has not enabled MySQL traditional mode, which means silent data corruption may occur. Please encourage the application developers to enable this mode.
2.) lbragstad@
2014-03-08 15:29:14.757 WARNING keystone.
43
This might have something to do with it? https:/ /review. openstack. org/#/c/ 55908/82/ keystone/ cli.py
I think that is the only change on keystone/cli.py that has happened since Steven's fix went in?