[Bug 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled

[Matt Thompson]

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":
"2f216605a48148f89d4390fc63e64819"}

If your data was like this, it would have migrated correctly:

{"password": null, "enabled": true, "email": null, "tenantId":
"2f216605a48148f89d4390fc63e64819"}

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

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1167421

Title:
  Upgrading from folsom to grizzly results in all tenants/users being
  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1167421/+subscriptions