[SRU] Juju 2.0 for Xenial

Bug #1573176 reported by Nicholas Skaggs on 2016-04-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core (Ubuntu)

Bug Description

Juju 2.0 is not quite final, as per the risks and timeline outlined in the FFe for Xenial, bug 1545913. As such, we intend to release SRU post-xenial release. This updates juju to the lastest 2.0 milestone version.

[SRU Information]

juju-core has a stable release exception, including for major version updates, https://lists.ubuntu.com/archives/technical-board/2014-August/001992.html.

This beta brings further stability to lxd integration, fixes critical bugs, along with easing the transition for juju-1 users who upgrade.

[Changes in Beta5]
* Support for local charm repositories removed.
  * All local charms must now be deployed using the path to the charm
    instead of a local URL.
  * Bundles support specifying local charms using the path to the charm.

* Notable Bug Fixes:
  * GridFS namespace breaks charm and tools deduping across models bug 1569054
  * Unable to download local: charm due to hash mismatch in multi-model deployment bug 1541482
  * Destroyed models still show up in list-models bug 1534627

[Changes in Beta6]
* Juju loses agents, bug 1572237
* tols info mismatch on arch with lxd containers, bug 1572781

A full list of targetted bugs can be seen against each milestone:


Juju practices continuous integration and testing of the juju source tree. All voting tests must pass for ubuntu before release.

For beta5: http://reports.vapour.ws/releases/3908
For beta6: http://reports.vapour.ws/releases/3921

In addition, juju has adt test coverage for all supported archs, http://autopkgtest.ubuntu.com/packages/j/juju-core/.

summary: - [SRU] Juju 2.0 beta5 for Xenial
+ [SRU] Juju 2.0 for Xenial
description: updated
description: updated

Hello Nicholas, or anyone else affected,

Accepted juju-core into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/juju-core/2.0~beta6-0ubuntu1.16.04.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!

tags: added: verification-needed
Mike McCracken (mikemc) wrote :

I tested the package version 2.0~beta6-0ubuntu1.16.04.1 from xenial-proposed and can verify that bug 1572237 is fixed in that package.

As when testing that bug, I used juju and conjure-up to deploy openstack onto lxd containers. I saw no agent-lost errors.

tags: added: verification-done
removed: verification-needed
Adam Stokes (adam-stokes) wrote :

Also tested on a separate system utilizing conjure-up and juju beta6 and saw no agent lost errors for bug 1572237

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-core - 2.0~beta6-0ubuntu1.16.04.1

juju-core (2.0~beta6-0ubuntu1.16.04.1) xenial-proposed; urgency=medium

  * New upstream release 2.0-beta6 (LP: #1573176).
  * Includes fixes for upstream bugs:
    - juju loses agents during a lxd deploy.
    - 'failed to ensure LXD image' creating LXD container.

 -- Martin Packman <email address hidden> Tue, 26 Apr 2016 01:27:27 +0000

Changed in juju-core (Ubuntu):
status: New → Fix Released

The verification of the Stable Release Update for juju-core 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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers