LXC local provider fails to provision precise instances from a trusty host

[Liam Young]

SRU Rationale for juju-quickstart only:
[Impact]

juju-quickstart could not deploy the juju-gui charm for trusty.

[Test Case]

On a trusty host, using an LXC environment run juju-quickstart and ensure that the GUI charm is deployed.

[Regression Potential]

The supported series is expanded from just precise to include trusty. The trusty charm deployments have been used via the PPA for quite a while. The regression potential is small.

[Original Bug Report]

I'm using the LXC local provider on Trusty with,

juju-core: 1.18.0-0ubuntu1
juju-local: 1.18.0-0ubuntu1
juju-mongodb: 2.4.9-0ubuntu3

I can create trusty units without a problem but precise units gets stuck in pending. I have used this script http://blog.naydenov.net/2014/03/remove-juju-local-environment-cleanly/ to wipe my environment before attempting the test.

[Chris Johnston (cjohnston)]

I am also able to create trusty units, however precise fails.

[Curtis Hovey (sinzui)]

Juju uses the default-series to determine the series you want, otherwise it needs to guess. You can update the environments.yaml with
    default-series: precise
to tell juju the series to use for the boostrap node and the default series to deploy charms to when the series is not specified in the charm url.

[Chris Johnston (cjohnston)]

Curtis, I did have default-series: precise set when doing this.

[Chris Johnston (cjohnston)]

The relevant portion of my environments.yaml:

  local:
    type: local
    default-series: precise
    lxc-clone: true
    lxc-clone-aufs: true
    admin-secret: mine

[Curtis Hovey (sinzui)]

This is probably a dupe of bug 1302820

[Ian Booth (wallyworld)]

I can confirm that using default-series: precise solves the problem.
However, there's a possibly related issue in that if you don't have a default series set, and first try a precise charm, it gets stuck in pending. Then, deploying a trusty charm after that also stays in pending. Whereas deploying a trusty charm first works.

[John A Meinel (jameinel)]

2014-04-23 12:36:43 ERROR juju runner.go:220 worker: exited "environ-provisioner": failed to process updated machines: cannot start machine 1: no matching tools available

Is something I see in my log file when I try to deploy a Precise machine.

[Chris Johnston (cjohnston)]

As I said above, default-series did not resolve the problem for me.

[John A Meinel (jameinel)]

Steps to reproduce:

juju bootstrap -e local --debug
juju deploy precise/ubuntu
juju deploy trusty/ubuntu ubuntu-t

The former gets stuck and is erroring with "no tools found", the latter seems stuck waiting for the former to get provisioned.

If I, instead, do:
juju bootstrap -e local --debug --upload-tools --series precise,trusty
juju deploy precise/ubuntu
juju deploy trusty/ubuntu ubuntu-t

Then everything works as expected.

[Matthew Hooker (mjhdrmg)]

I'm still getting the issue with freshly installed and fully updated 14.04, what can I check to establish what is causing this?

installed trusty/juju-gui, trusty/mysql
fails installing precise/joomla

ERROR juju runner.go:220 worker: exited "environ-provisioner": failed to process updated machines: cannot start machine 3: no matching tools available

[Robie Basak (racb)]

juju-quickstart needs fixing in Utopic before I can SRU Trusty, but 1.3.2 packaged for Utopic currently fails, so I have not uploaded. I have filed bug 1317939 to track this.

[Chris Johnston (cjohnston)]

I'm running 1.18.3 and I'm still seeing this..

Installed: 1.18.3-0ubuntu1~14.04.1~juju1

[Erik B. Andersen (erik-b-andersen+azendale)]

For people still having trouble with this, you may want to look at http://askubuntu.com/questions/486542/upload-all-release-versions-of-tools-with-jujus-local-lxc-provider to see if it helps.

[Robie Basak (racb)]

Fixed in juju-quickstart 1.4.0-0ubuntu1 in Utopic. Trusty SRU pending.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris J Arges (arges)]

Hello Liam, or anyone else affected,

Accepted juju-quickstart into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju-quickstart/1.3.1-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Jay R. Wren (evarlast)]

Tested with
juju-quickstart 1.3.1-0ubuntu1.1 (from proposed)
# juju version
1.18.4-trusty-amd64

quickstart defaults to default-series trusty, this works.

Tested a second time with default-series precise, this also works, but deploys on trusty.

I do not know how to test this, can someone give more specific instructions on how to force precise ?

[Robie Basak (racb)]

Following a brief discussion on IRC, I think this is good enough.

15:55 <rbasak> Looking again, the key bug was in Juju. juju-quickstart had a task, and you moved to Trusty from Precise, which also eliminated the bug.

15:56 <rbasak> As long as proposed juju works with proposed juju-quickstart, we should be verification-done.

[Jay R. Wren (evarlast)]

Forced use of precise with:

juju-quickstart --gui-charm-url cs:~juju-gui/precise/juju-gui-169

Everything worked.

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju-quickstart - 1.3.1-0ubuntu1.1

---------------
juju-quickstart (1.3.1-0ubuntu1.1) trusty; urgency=medium

  * Cherry-pick bugfixes from 1.3.2:
    - Make control bucket optional (LP: #1309678).
    - Support Trusty environments (LP: #1306537).
    - Check unicode support (LP: #1311321).
 -- Robie Basak <email address hidden> Wed, 02 Jul 2014 16:47:16 +0000

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for juju-quickstart has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.