Public bug reported:
The keystone maintainer script endeavours to check whether the
sql_connection string is set in keystone.conf; however it searches for
the wrong string:
if ! grep -q sql_connection /etc/keystone/keystone.conf
then
su -s /bin/sh -c 'exec keystone-manage db_sync' keystone
fi
The connection configuration uses the key 'connection' and inline with
other packages, I think we should only be doing a db_sync if the
connection is the default sqllite one (see glance for reference).
This is quite important - 2013.2.2 adds an index to an existing table
and takes a long time, resulting in quite a long outage; also running
from multiple locations might be bad as well.
** Affects: keystone (Ubuntu)
Importance: High
Status: Triaged
** Affects: keystone (Ubuntu Trusty)
Importance: High
Status: Triaged
** Also affects: keystone (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: keystone (Ubuntu Trusty)
Status: New => Triaged
** Changed in: keystone (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290423
Title:
maintainer scripts always run db_sync during upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1290423/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
