juju 1.23b4 vivid panic: runtime error: invalid memory address or nil pointer dereference

Bug #1443541 reported by Ryan Beisner on 2015-04-13
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
High
Eric Snow
1.23
High
Eric Snow

Bug Description

With juju 1.23b4 and Vivid deployments, some arbitrary units get stuck in an "allocating" state. Juju machine logs show "panic: runtime error: invalid memory address or nil pointer dereference."

juju stat (openstack deploy): http://paste.ubuntu.com/10816905/
juju stat (mysql deploy): http://paste.ubuntu.com/10817168/
panic: http://paste.ubuntu.com/10817269/

See attached logs.

jenkins@juju-osci-machine-3:~$ apt-cache policy juju
juju:
  Installed: (none)
  Candidate: 1.23-beta4-0ubuntu1~14.04.1~juju1
  Version table:
     1.23-beta4-0ubuntu1~14.04.1~juju1 0
        500 http://ppa.launchpad.net/juju/devel/ubuntu/ trusty/main amd64 Packages
     1.22.1-0ubuntu1~14.04.1~juju1 0
        500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
     1.20.11-0ubuntu0.14.04.1 0
        500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
     1.18.1-0ubuntu1 0
        500 http://nova.clouds.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

Attached all logs from http://10.245.162.77:8080/view/Dashboards/view/OpenStack%20Deploy/job/deploy_with_deployer/6025/artifact/logs/

Ryan Beisner (1chb1n) wrote :
Ryan Beisner (1chb1n) wrote :

To confirm that this issue is not specific to deploying OpenStack, I deployed this mysql bundle with Vivid and juju 1.23b4, which also resulted in juju panics.

http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/dev/mysql-scale.yaml

juju stat: http://paste.ubuntu.com/10817168/
mysql/1 machine log: http://paste.ubuntu.com/10817269/

Commands used to deploy:
juju-deployer -v -c mysql-scale.yaml -d trusty
  ..or..
juju-deployer -v -c mysql-scale.yaml -d kilo

As an added note, the same mysql bundle deploys cleanly with juju 1.23b4 on Trusty (http://paste.ubuntu.com/10817202/).

Additional version info:
00:01:38.953 Juju-core ver: Installed: 1.23-beta4-0ubuntu1~14.04.1~juju1
00:01:38.968 Juju-core ppa: 500 http://ppa.launchpad.net/juju/devel/ubuntu/ trusty/main amd64 Packages 500 http://ppa.launchpad.net/juju/stable/ubuntu/ trusty/main amd64 Packages
00:01:38.984 Amulet ver: Installed: 1.10.0-0ubuntu3~ubuntu14.04.1~ppa1
00:01:39.000 Juju-deployer ver: Installed: 0.4.3-0ubuntu1~ubuntu14.04.1~ppa1

description: updated
description: updated
Ryan Beisner (1chb1n) on 2015-04-13
description: updated
Ian Booth (wallyworld) on 2015-04-13
Changed in juju-core:
milestone: none → 1.23.0
status: New → Triaged
importance: Undecided → High
assignee: nobody → Eric Snow (ericsnowcurrently)
Changed in juju-core:
milestone: 1.23.0 → 1.24-alpha1
status: Triaged → In Progress
Eric Snow (ericsnowcurrently) wrote :

This addresses the panic: http://reviews.vapour.ws/r/1424/

However, the root cause is still unclear. It is possible, however, that it is related to lp:1443440.

Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2015-04-21
Changed in juju-core:
status: Fix Committed → Fix Released
tags: added: systemd upstart vivid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers