Juju Charms Collection

cassandra fails on 'leader-elected' hook because it doesn't know about lxd

Bug #1577955 reported by Mike McCracken
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charms Collection
New
Undecided
Unassigned

Bug Description

A deploy of cs:trusty/cassandra-15 is failing with the following in the debug log:
(these failures repeat regularly)

this is on a LXD controller, on xenial, with juju 2.0 beta 6.

this is part of deploying this bundle:
http://paste.ubuntu.com/16209402/

Here's a better-formatted way to see it:
http://paste.ubuntu.com/16209115/

See original description
Mike McCracken (mikemc)
description: updated
Revision history for this message
Mike McCracken (mikemc) wrote :

I'm trying to reproduce this again now.

description: updated
description: updated
Revision history for this message
Mike McCracken (mikemc) wrote :

This is because there's code that checks if the charm is deployed to an LXC container, and we were deploying into LXD.

http://bazaar.launchpad.net/~charmers/charms/trusty/cassandra/trunk/view/head:/hooks/helpers.py#L214

summary: - cassandra fails on 'leader-elected' hook
+ cassandra fails on 'leader-elected' hook because it doesn't know about
+ lxd
description: updated
Revision history for this message
Tycho Andersen (tycho-s) wrote :

Checking /proc/1/cgroup won't work on xenial with LXC or LXD, because both will make use of cgroup namespaces, and so /proc/1/cgroup should say / for all containers in xenial.

On xenial, you can use systemd-detect-virt, and on older releases you can do running-in-container.

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.