Charms utilizing block storage fail on LXD

Bug #1603221 reported by Nicholas Skaggs on 2016-07-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Low
Unassigned

Bug Description

The issue showing the linked failures can be seen here: http://reports.vapour.ws/releases/issue/5788d733749a5678166b0791

As seen in http://reports.vapour.ws/releases/4136/job/functional-storage/attempt/55#highlight, the test passes in the AWS substrate, but fails inside of LXD by timing out waiting for the agent to come up.

A proper AWS run can be seen here:

http://juju-ci.vapour.ws:8080/job/functional-storage/54/console

Ian Booth (wallyworld) on 2016-07-14
Changed in juju-core:
milestone: none → 2.0-beta13
importance: Undecided → High
status: New → Triaged
description: updated
Curtis Hovey (sinzui) on 2016-07-15
tags: added: jujuqa lxd-provider storage
Changed in juju-core:
assignee: nobody → Katherine Cox-Buday (cox-katherine-e)
Curtis Hovey (sinzui) on 2016-07-22
Changed in juju-core:
milestone: 2.0-beta13 → 2.0-beta14
Anastasia (anastasia-macmood) wrote :

This bug also affects CI and prevents a "bless".

Changed in juju-core:
importance: High → Critical
Tim Penhey (thumper) wrote :

Last success was July 14, http://reports.vapour.ws/releases/4136

Nicholas Skaggs (nskaggs) wrote :

Actually, it seems there is no recorded success, since as soon as we transitioned the job to LXD, it looks like it began failing. The earlier successes were on AWS or joyent. If you would like to run the test against an old release of juju (aka, you feel beta3 may work and want data) and need help, let me know.

tags: added: blocker
Changed in juju-core:
status: Triaged → In Progress
tags: removed: blocker
Changed in juju-core:
assignee: Katherine Cox-Buday (cox-katherine-e) → nobody
Curtis Hovey (sinzui) on 2016-08-03
summary: - Charms utilizing storage fail on LXD
+ Charms utilizing block storage fail on LXD
Changed in juju-core:
importance: Critical → Medium
status: In Progress → Triaged
tags: added: feature
Changed in juju-core:
milestone: 2.0-beta14 → none
importance: Medium → Low
Curtis Hovey (sinzui) wrote :

lxd does not support block storage. just rootfs ramfs and loop. If CI wants to test storage on lxd, the test needs to be structured to test supported features.

Aaron Bentley (abentley) wrote :

The failure does not appear to be related to block storage. The command leading to the failure is is "juju --show-log deploy -m functional-storage:functional-storage /tmp/tmpkDUt55/trusty/dummy-storage-lp --series trusty --storage disks=loop,1G"

Ian Booth (wallyworld) wrote :

loop is block storage which is not yet supported by the new lxd provider

affects: juju-core → juju
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers