keystone charm in Trusty

Quentin Hartman qhartman at gmail.com
Wed Apr 23 19:34:46 UTC 2014


Oops, just found this bug:
https://bugs.launchpad.net/charms/+source/mysql/+bug/1305582

Seems to be the behavior I'm seeing. I'll move discussion / whatnot over
there.

QH


On Wed, Apr 23, 2014 at 1:30 PM, Quentin Hartman <qhartman at gmail.com> wrote:

> Continuing with my MAAS/JuJu/Openstack adventures with Trusty, I've found
> what seems to be a problem in the keystone charm. When it gets to the point
> where it seems to be needing to do some Mysql schema work, it fails, with
> the following output in the unit-keystone-0.log:
>
> 2014-04-23 17:22:39 INFO juju-log shared-db:16: Rendering from template:
> keystone.conf
> 2014-04-23 17:22:39 INFO juju-log shared-db:16: Wrote template
> /etc/keystone/keystone.conf.
> 2014-04-23 17:22:39 INFO juju-log shared-db:16: Migrating the keystone
> database.
> 2014-04-23 17:22:39 INFO shared-db-relation-changed keystone stop/waiting
> 2014-04-23 17:22:40 INFO shared-db-relation-changed Traceback (most recent
> call last):
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/var/lib/juju/agents/unit-keystone-0/charm/hooks/shared-db-relation-changed",
> line 291, in <module>
> 2014-04-23 17:22:40 INFO shared-db-relation-changed     main()
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/var/lib/juju/agents/unit-keystone-0/charm/hooks/shared-db-relation-changed",
> line 285, in main
> 2014-04-23 17:22:40 INFO shared-db-relation-changed
> hooks.execute(sys.argv)
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/var/lib/juju/agents/unit-keystone-0/charm/hooks/charmhelpers/core/hookenv.py",
> line 381, in execute
> 2014-04-23 17:22:40 INFO shared-db-relation-changed
> self._hooks[hook_name]()
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/var/lib/juju/agents/unit-keystone-0/charm/hooks/charmhelpers/core/host.py",
> line 217, in wrapped_f
> 2014-04-23 17:22:40 INFO shared-db-relation-changed     f(*args)
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/var/lib/juju/agents/unit-keystone-0/charm/hooks/shared-db-relation-changed",
> line 139, in db_changed
> 2014-04-23 17:22:40 INFO shared-db-relation-changed     migrate_database()
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/var/lib/juju/agents/unit-keystone-0/charm/hooks/keystone_utils.py", line
> 262, in migrate_database
> 2014-04-23 17:22:40 INFO shared-db-relation-changed
> subprocess.check_output(cmd)
> 2014-04-23 17:22:40 INFO shared-db-relation-changed   File
> "/usr/lib/python2.7/subprocess.py", line 573, in check_output
> 2014-04-23 17:22:40 INFO shared-db-relation-changed     raise
> CalledProcessError(retcode, cmd, output=output)
> 2014-04-23 17:22:40 INFO shared-db-relation-changed
> subprocess.CalledProcessError: Command '['sudo', '-u', 'keystone',
> 'keystone-manage', 'db_sync']' returned non-zero exit status 1
> 2014-04-23 17:22:40 ERROR juju.worker.uniter uniter.go:486 hook failed:
> exit status 1
>
>
> I haven't dug into this at all yet, but I expect it is a result of the
> mysql permissions being incorrect to allow this machine to make schema
> changes. I'm running this test deployment with all services collapsed onto
> a single machine, in case that's relevant.
>
> I believe I've changed the mysql config to allow this to happen. What is
> the correct way to attempt to re-deploy a charm? Should I remove it and
> then simply deploy again?
>
> Thanks
>
> QH
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140423/29a33aa0/attachment.html>


More information about the Juju mailing list