Ubuntu
juju-core package

[needs-packaging] 1.22.8 is not packaged in trusty

  1. Trusty (14.04)
  2. Bug #1483885
Bug #1483885 reported by Curtis Hovey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core (Ubuntu)
Invalid
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned

Bug Description

Juju 1.22.8 is currently proposed to be the next supported Juju release. The juju team want this version also proposed for trusty. This release has an upgrade and an proxy fix asked for by enterprise customers.

[SRU Information]

juju-core has a stable release exception in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions, including for major version updates.

[trusty Fix]

[sinzui] Prepare source package, and diffs: DONE
[rbasak] Review package and upload of new upstream release with packaging review.

[Pre-QA tasks]

[rbasak] Upload to the development release (trusty-proposed): DONE

[QA Status]

Since there are multiple verifications required, they are listed here as a work item whiteboard status type thing rather than try and track them in a single tag. Please do not mark verification-done or remove block-proposed until all following items have passed. If any of these items fail, this bug should be marked verification-failed immediately.

[sinzui] Upstream QA test against trusty: DONE
[sinzui] Upstream release process complete: DONE

Manual tests required:

[sinzui] Test juju-quickstart against trusty-proposed: DONE
[sinzui] Test juju-deployer against trusty-proposed: DONE
[sinzui] Test client manual bootstrap and add-machine: DONE
[sinzui] Test client and cloud server upgrade from main/updates: TODO

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

We do not want this version is wily because bug 1481556 tracks our request to put 1.24.x into wily, which offers systemd support.

The code change is small. Note that the html test files were removed from the release tarfile. The tests are not needed, and in older versions of juju, they were purged because they were ambiguously licensed. We decided we want consistent rules for creating tarfiles.

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

The only change to the debian dir was an update to the changelog.

description: updated
Revision history for this message
Robie Basak (racb) wrote :

As this isn't going into Wily, no need to block proposed migration in Wily. Bug 1481556 will take care of this for the 1.24 series that is going in to Wily.

tags: removed: block-proposed
Revision history for this message
Robie Basak (racb) wrote :

Uploaded to Trusty, with minor changes. Curtis: please pull in my changes from https://git.launchpad.net/~ubuntu-server/ubuntu/+source/juju-core/+git/packaging/log/?h=basak/trusty

Now awaiting SRU team review.

Changed in juju-core (Ubuntu):
status: New → In Progress
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Curtis, or anyone else affected,

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

Changed in juju-core (Ubuntu):
status: In Progress → Invalid
Changed in juju-core (Ubuntu Trusty):
status: New → Fix Committed
Revision history for this message
Curtis Hovey (sinzui) wrote :

I certify that juju 1.22.8 is suitable for local charm development and testing on trusty. Users of trusty juju 1.22.8 can create new environments in private and public clouds. trusty juju 1.22.8 can maintain environments back to 1.18.1 (including 1.22.6 which trusty currently has). Upgrades of clients and environments from juju 1.22.6 to 1.22.8 work without need of configuration changes. trusty juju 1.22.8 can manually provision environments and add-machines.

description: updated
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-core - 1.22.8-0ubuntu1~14.04.1

---------------
juju-core (1.22.8-0ubuntu1~14.04.1) trusty; urgency=medium

  * New upstream bugfix release (LP: #1483885).
    - Juju uses proxy to access bootstrap node (Lp: #1478660).
    - Juju environment not usable after the upgrade (Lp: #1473517).

 -- <email address hidden> (Curtis C. Hovey) Tue, 11 Aug 2015 15:05:03 +0000

Changed in juju-core (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update 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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.