Upgrade --upload-tools fails if there's a series in streams Juju doesn't recognize
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Jesse Meek | ||
1.21 |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Every six months we run into the same problem - there's a new series announced, and it makes it into part of the ecosystem but not all.
I was doing upgrade testing today and got this error:
ERROR juju.worker runner.go:219 exited "upgrader": invalid series "wily"
This blocked my environment from upgrading. Why is that? I wasn't deploying tools for the series wily... and I wasn't upgrading a machine that used the series wily. So why does my environment care that somewhere someone specified a series it doesn't understand if it's not even using that series?
I think this is overly aggressive error checking when retrieving streams. We definitely should never stop someone's environment from upgrading because someone published something to streams that our juju doesn't recognize. If it doesn't recognize it, it shouldn't use it... but it shouldn't just stop everything from proceeding.
Comment #2 described two work arounds. Many people report that updating the distro-info-data package on the state-server (often machine-0) fixes the issue
sudo apt-get install distro-info-data
no longer affects: | juju-core/1.24 |
Changed in juju-core: | |
assignee: | nobody → Jesse Meek (waigani) |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
description: | updated |
summary: |
- Upgrade fails if there's a series in streams Juju doesn't recognize + Upgrade --upload-tools fails if there's a series in streams Juju doesn't + recognize |
tags: | added: canonical-is |
This issue overlaps with Tims assertion that the state-server's job is to store the agents, not judge them: bug 1403689