Juju Charms Collection
keystone package

keystone db accessed before ready

Bug #1413753 reported by Narinder Gupta
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
keystone (Juju Charms Collection)
Fix Released
High
Edward Hope-Morley
Juju Charms Collection 15.04

Bug Description

juju deploy keystone is failing at config-change
ubuntu@upstream-maas-vm:~$ juju status keystone
environment: maas
machines:
  "1":
    agent-state: started
    agent-version: 1.20.14
    dns-name: instructive-voice.maas
    instance-id: /MAAS/api/1.0/nodes/node-8baf40d6-8628-11e4-89a8-5254008e6f5b/
    series: trusty
    hardware: arch=armhf cpu-cores=4 mem=6656M
services:
  keystone:
    charm: cs:trusty/keystone-9
    exposed: false
    relations:
      cluster:
      - keystone
    units:
      keystone/0:
        agent-state: error
        agent-state-info: 'hook failed: "config-changed"'
        agent-version: 1.20.14
        machine: "1"
        public-address: instructive-voice.maas
networks:
  maas-eth1:
    provider-id: maas-eth1
    cidr: 10.10.2.0/24
ubuntu@upstream-maas-vm:~$

/var/log/juju/unit-keystone-0.log

http://paste.ubuntu.com/9824662/

juju resolved keystone/0 bring the agents into start mode and after that it works.

Tags: openstack cts
Revision history for this message
Ryan (ryan09) wrote :

I'm seeing the same issue deploying to pre-installed 14.10.1 hosts using a "manual" juju environment.

After running "juju resolved keystone/0" the service shows started in juju status, however running juju add-relation keystone mysql fails and sets the agent-state of keystone to error, with an agent-state-info of 'hook failed: "shared-db-relation-changed" for mysql:shared-db'.

Revision history for this message
Narinder Gupta (narindergupta) wrote :

This error is causing me not able to demo Nuage charms for MWC.

Revision history for this message
Ryan Beisner (1chb1n) wrote :

Retargeted bug to the keystone charm.

Changed in openstack-charm-testing:
status: New → Invalid
Revision history for this message
Ryan Beisner (1chb1n) wrote :

As a quick check, a simplified bundle deploys ok on amd64. See attached.

Revision history for this message
Edward Hope-Morley (hopem) wrote :

FYI I think this is fixed in /next by the following:

revno: 121 [merge]
committer: Edward Hope-Morley <email address hidden>
branch nick: keystone.next
timestamp: Tue 2015-02-17 09:22:46 +0000
message:
  [hopem,r=gnuoy]

  Fixes db migration (keystone-manage db-sync) races but preventing
  database access/usage until the database is ready and has been
  initialised.

Ryan Beisner (1chb1n)
no longer affects: openstack-charm-testing
Revision history for this message
Edward Hope-Morley (hopem) wrote :

Just found a bug in the aforementioned fix that allows db sync to run before db ready. Will post fix imminently.

Changed in keystone (Juju Charms Collection):
status: New → In Progress
assignee: nobody → Edward Hope-Morley (hopem)
milestone: none → 15.04
summary: - keystone charm deployment failed
+ keystone db accessed before ready
Changed in keystone (Juju Charms Collection):
importance: Undecided → High
tags: added: cts openstack
Billy Olsen (billy-olsen)
Changed in keystone (Juju Charms Collection):
status: In Progress → Fix Committed
James Page (james-page)
Changed in keystone (Juju Charms Collection):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.