pyjuju

New agent requirement for session file breaks all existing bootstrapped envs using juju-origin PPA

Bug #938463 reported by Clint Byrum
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Won't Fix
Undecided
Unassigned

Bug Description

If somebody has juju bootstrapped any time in the future from the PPA, and then tries to deploy/add-unit/etc. today, they wll get an error in the console of the new machines:

juju.errors.JujuError: No session file specified

This is because your old bootstrap node's provisioning agent is not specifying that option.

Perhaps we won't care about this, but filing the bug to document it.

Ideally juju would keep deploying the same version that it was bootstrapped with.

Revision history for this message
William Reade (fwereade) wrote :

Sorry, I think this is the second time I've managed to break every juju in existence :-/.

+100 on caching the original version of juju.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Its ok, the fallout is worth having the robustness added, really. I do think we need to have an "upgrade to a new client version" integration test which will simply bootstrap with the last known good version, and then run all integration tests with the newer client.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

This has gone unfixed long enough that no users are likely left running the old version on PPA.

Changed in juju:
status: New → Won't Fix
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.