This tripped me up as I tried doing some vanilla upgrades from folsom to grizzly using precise-proposed/folsom and precise-proposed/grizzly (which still has 1:2013.1-0ubuntu1.1~cloud0) and was unable to replicate the issue with some newly created dummy users/tenants.
Packages keystone_ 2013.1. 1-0ubuntu1_ all.deb and python- keystone_ 2013.1. 1-0ubuntu1_ all.deb worked for me when upgrading from folsom to grizzly.
On a side note, this issue reported should have only been an issue when you have data like this in the "extra" column in the keystone.user table:
{"password": null, "enabled": "true", "email": null, "tenantId": "2f216605a48148 f89d4390fc63e64 819"}
If your data was like this, it would have migrated correctly:
{"password": null, "enabled": true, "email": null, "tenantId": "2f216605a48148 f89d4390fc63e64 819"}
This tripped me up as I tried doing some vanilla upgrades from folsom to grizzly using precise- proposed/ folsom and precise- proposed/ grizzly (which still has 1:2013. 1-0ubuntu1. 1~cloud0) and was unable to replicate the issue with some newly created dummy users/tenants.
Thanks!
-Matt