Merge lp://staging/~sinzui/juju-release-tools/survive-unsupported-series into lp://staging/juju-release-tools
| Status: | Merged |
|---|---|
| Merged at revision: | 106 |
| Proposed branch: | lp://staging/~sinzui/juju-release-tools/survive-unsupported-series |
| Merge into: | lp://staging/juju-release-tools |
| Diff against target: |
24 lines (+7/-0) 1 file modified
assemble-streams.bash (+7/-0) |
| To merge this branch: | bzr merge lp://staging/~sinzui/juju-release-tools/survive-unsupported-series |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Aaron Bentley (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
This branch adds a guard to prevent creating agents for series that the localhost doesn't support.
Juju will raise an error if the series is not registered with it or the localhost via
/usr/share/
Precise machines like juju-ci and Jerff haven't gotten the new distro-info-data package that includes vivid. We hacked the data on juju-ci's master. Jerff has an RT open to get the machine updated...OS image streams are affects much like juju agent streams. Jerff may get updated in a few hours.
In the meantime this branch adds rules to skip the agent if its series is not known. I tested this using the -t option to pass a directory of juju-core packages which included vivid. The vivid agent was made and included in the streams on my trusty host. I remove vivid from ubuntu.csv, then ran the script again to verify the vivid agent was skipped. There were errors.
If we do release without Jerff having vivid knowledge, I expect the vivid agent to be added shortly after the host is updated with vivid.
This works, but I found the supported_series handling a bit weird. See below.