1.x upgrades do not not use isolated home for default-jes
Bug #1531183 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-ci-tools |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
When performing an upgrade, the decision of whether to use an isolated home is based only on whether the source juju supports jes, not the target. Current jes-enabled builds do not dump a cache.yaml in this situation, but there is a risk that future versions will.
| summary: |
- upgrades do not not use isolated home for default-jes + 1.x upgrades do not not use isolated home for default-jes |
| Changed in juju-ci-tools: | |
| importance: | Medium → Wishlist |
Revision history for this message
| Aaron Bentley (abentley) wrote | #1 |
| Changed in juju-ci-tools: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
We no longer test 1.x JES and we don't test 1.x -> 2.x