lxc broken in trunk r2440

Bug #1294632 reported by Curtis Hovey on 2014-03-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Critical
Ian Booth

Bug Description

Local provider lxc boostrap broke with r2440.
    juju --show-log bootstrap -e local --constraints mem=2G
    2014-03-19 03:14:16 INFO juju.provider.local environprovider.go:147 checking state port
    2014-03-19 03:14:16 INFO juju.provider.local environprovider.go:147 checking API port
    2014-03-19 03:14:17 INFO juju.provider.local environprovider.go:40 opening environment "local"
    2014-03-19 03:14:17 WARNING juju.environs.config config.go:861 unknown config field "shared-storage-port"
    2014-03-19 03:14:17 WARNING juju.environs.config config.go:861 unknown config field "shared-storage-port"
    2014-03-19 03:14:17 WARNING juju.environs.config config.go:861 unknown config field "shared-storage-port"
    2014-03-19 03:14:17 INFO juju.environs.bootstrap synctools.go:32 checking that upload is possible
    2014-03-19 03:14:17 ERROR juju.cmd supercommand.go:296 Juju cannot bootstrap because no tools are available for your environment.
    You may want to use the 'tools-metadata-url' configuration setting to specify the tools location.

Since local provider *DID* work before r2440, it appears the "checking that upload is possible" is too strict. CI is running lxc on the jenkins machine in ec2

Related branches

Curtis Hovey (sinzui) on 2014-03-19
Changed in juju-core:
milestone: none → 1.17.6
Curtis Hovey (sinzui) wrote :

The AWS instance we run lxc does state it is amd64 precise

$ uname -a
Linux ip-172-31-46-223 3.2.0-58-virtual #88-Ubuntu SMP Tue Dec 3 17:58:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise

Tim Penhey (thumper) on 2014-03-19
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
Curtis Hovey (sinzui) wrote :

Juju CI creates the release tarball, then makes and64 packages for trusty, precise, and saucy. Tests install the package in the workspace (not in the standard location). The PATH is updated to include the new juju. The tests then run with the new juju. Upgrade tests use the stable juju, then update the PATH, to switch to the new juju.

We can check the jujud version by exporting the PATH
$ cd ~/jobs/local-deploy/workspace/extracted-bin/usr/lib/juju-1.17.6/bin
$ PATH=/var/lib/jenkins/jobs/local-deploy/workspace/extracted-bin ./jujud version
1.17.6-precise-amd64
^ that is the version we are testing.

Ian Booth (wallyworld) on 2014-03-19
Changed in juju-core:
status: Triaged → In Progress
Ian Booth (wallyworld) on 2014-03-19
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui) on 2014-03-20
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers