Juju should use bundled jujud if not matching agents found in streams
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
Critical
|
Unassigned | ||
juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Nicholas Skaggs | ||
Xenial |
Fix Released
|
High
|
Nicholas Skaggs |
Bug Description
Since --upload-tools is now no longer needed, juju needs to fallback to using bundled jujud in the case where no matching agents are found in streams. For example,
6:38:07 INFO juju.environs.
..
16:38:07 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0-beta18 for amd64
...
16:38:08 INFO juju.environs.
..
16:38:08 ERROR cmd supercommand.go:458 failed to bootstrap model: no matching tools available
16:38:08 DEBUG cmd supercommand.go:459 (error details: [{github.
In this example, beta18 is a released version, and 15 agents are found. However, none of them match my crazy series. Juju should still use the bundled agent automatically. Note, passing --build-agent requires me to rebuild an agent in this case; not something I can/should need to do on a client machine.
[SRU Information]
[Impact]
The autopkgtest for future-
[Verification]
The autopkgtest future-
SKIP: Juju won't bootstrap unknown without published agent (LP:1629376)
[Regression Potential]
None. The package won't make it out of proposed, as the test will currently fail as-is.
[Other]
This should have no impact on end users of the package; the verification can be done by viewing the test results under http://
description: | updated |
tags: | added: ci regression |
tags: | added: packaging |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.0.0 |
Changed in juju: | |
assignee: | nobody → Alexis Bruemmer (alexis-bruemmer) |
Changed in juju: | |
status: | Triaged → Invalid |
tags: | added: ateam |
Changed in juju: | |
milestone: | 2.0.0 → none |
assignee: | Alexis Bruemmer (alexis-bruemmer) → nobody |
Changed in juju-core (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Nicholas Skaggs (nskaggs) |
description: | updated |
description: | updated |
Changed in juju-core (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in juju-core (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in juju-core (Ubuntu Xenial): | |
assignee: | nobody → Nicholas Skaggs (nskaggs) |
importance: | Undecided → High |
This ultimately a blocker for putting Juju into Ubuntu. They require juju clients to work with the next Ubuntu release. The next-release test was put in place because Juju clients fell over when they didn't recognise their host series.
There may come a time when Ubuntu only get clients, and the package test will need to switch to the current LTS. It is possible to change the package tests to do this