Agent stuck in "allocating" state

Bug #1517535 reported by Jacek Nykis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
High
Unassigned

Bug Description

I am working on a charm that uses storage in juju 1.25.

I have this in my metadata.yaml:
storage:
  whisper:
    type: filesystem
    location: /var/lib/graphite/whisper

But when I juju deploy this charm using:
juju deploy local:trusty/graphite --storage whisper=loop,200M g2

Agents get stuck in allocating state

environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.25.0.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
    state-server-member-status: has-vote
  "1":
    agent-state: started
    agent-version: 1.25.0.1
    dns-name: 10.0.3.216
    instance-id: jacek-local-machine-1
    series: trusty
    hardware: arch=amd64
services:
  g2:
    charm: local:trusty/graphite-0
    exposed: false
    service-status:
      current: unknown
      message: Waiting for agent initialization to finish
      since: 18 Nov 2015 15:42:59Z
    units:
      g2/0:
        workload-status:
          current: unknown
          message: Waiting for agent initialization to finish
          since: 18 Nov 2015 15:42:59Z
        agent-status:
          current: allocating
          since: 18 Nov 2015 15:42:59Z
          version: 1.25.0.1
        agent-state: pending
        agent-version: 1.25.0.1
        machine: "1"
        public-address: 10.0.3.216

 Machine 1 was provisioned fine, I can juju ssh to it and agents seem to be running:
root 21322 1 0 15:45 ? 00:00:00 /var/lib/juju/tools/machine-1/jujud machine --data-dir /var/lib/juju --machine-id 1 --debug
root 21372 1 0 15:45 ? 00:00:00 /var/lib/juju/tools/unit-g2-0/jujud unit --data-dir /var/lib/juju --unit-name g2/0 --debug

juju 1.25.0-trusty-amd64

Revision history for this message
Cheryl Jennings (cherylj) wrote :

Can you attach the unit log for g2/0?

Changed in juju-core:
status: New → Incomplete
Revision history for this message
Jacek Nykis (jacekn) wrote :

Log file attached.

Changed in juju-core:
status: Incomplete → New
Revision history for this message
Cheryl Jennings (cherylj) wrote :

Unfortunately there wasn't much in the unit log, except that it looks like it's waiting for an API connection. If you still have the env, can you also upload machine-1.log and machine-0.log? (if you're using HA, please also include the machine logs from the other state servers)

Revision history for this message
Jacek Nykis (jacekn) wrote :

Machine 0 and 1 logs in attachment. I don't use juju HA, this is simple test environment using local provider.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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