Ive run into similar issues on a single machine with keystone, horizon, glance, and the like. The general consensus is to run each openstack service in a lxc container if you wish to deploy a cloud on a single node/machine
On Wed, Apr 23, 2014 at 3:34 PM, Quentin Hartman <[email protected]> wrote: > 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 <[email protected]> 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 > > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- [ Adam Stokes ] -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
