juju-core

local lxc deployments fail to create machines

Bug #1363143 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Andrew Wilkins
juju-core 1.21-alpha1

Bug Description

The local-deploy-precise-amd64 fails because juju is not creating containers/machines
    http://juju-ci.vapour.ws:8080/job/local-deploy-precise-amd64/1832/

The test last passed for commit 0c6ec682, as of commit f8ff4561 it fails. There is only one suspect commit
f8ff456 Merge pull request #608 from axw/cloudinit-download-tools-apiserver

precise uses lxc 1.0.0~alpha1-0ubuntu14.1~ubuntu12.04.1~juju1 which is know to not support --version

Revision history for this message
Curtis Hovey (sinzui) wrote :

I suspect lxc containers were created, but maybe the tools could not be downloaded to start machine 1 and 2's logs.

Andrew Wilkins (axwalk)
Changed in juju-core:
assignee: nobody → Andrew Wilkins (axwalk)
status: Triaged → In Progress
milestone: none → 1.21-alpha1
Revision history for this message
Andrew Wilkins (axwalk) wrote :

I'm going to back out a local-specific change I made to serialise the tools into cloud-config. Looks like it is causing cloud-init to hammer the CPU, probably in the YAML parser.

Revision history for this message
Andrew Wilkins (axwalk) wrote :

Tentatively setting to fixed, will watch CI for confirmation.

Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
importance: Critical → High
Curtis Hovey (sinzui)
Changed in juju-core:
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.