yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02528
[Bug 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
** Changed in: keystone
Status: Fix Committed => Fix Released
** Changed in: keystone
Milestone: None => havana-1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1167421
Title:
Upgrading from folsom to grizzly results in all tenants/users being
disabled
Status in Ubuntu Cloud Archive:
New
Status in OpenStack Identity (Keystone):
Fix Released
Status in Keystone grizzly series:
Fix Released
Status in “keystone” package in Ubuntu:
Confirmed
Bug description:
Hi there,
I tested a Folsom to Grizzly upgrade using stock packages on Ubuntu
12.04 and noticed that upon completion of the upgrade that there was a
new 'enabled' column in `user`/ `project` tables and that all records
within these tables had enabled set to 0. This resulted in
authentication failure on users which were working prior to the
upgrade. Once I ran the following, users could authenticate again:
# mysql keystone -e "update user set enabled=1"
# mysql keystone -e "update project set enabled=1"
For anyone else reading this, I knew all my users/tenants were enabled
so didn't have to worry about the above statements, however in some
environments there are likely to be disabled users/tenants which you'd
need to take note of. You can determine this by looking at the text
in the `extra` column within these two tables.
-Matt
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1167421/+subscriptions