| 2016-09-30 16:02:52 |
Nicholas Skaggs |
bug |
|
|
added bug |
| 2016-09-30 16:03:49 |
Nicholas Skaggs |
description |
Since --upload-tools is now no longer needed, juju needs to fallback to using bundled jujud in the case where no matching tools are found in streams. For example,
6:38:07 INFO juju.environs.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
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.bootstrap tools.go:74 found 15 packaged agent binaries
..
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.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
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. |
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.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
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.bootstrap tools.go:74 found 15 packaged agent binaries
..
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.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
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. |
|
| 2016-09-30 16:04:06 |
Nicholas Skaggs |
tags |
|
ci regression |
|
| 2016-09-30 16:22:35 |
Curtis Hovey |
tags |
ci regression |
ci packaging regression |
|
| 2016-09-30 16:22:43 |
Curtis Hovey |
juju: status |
New |
Triaged |
|
| 2016-09-30 16:22:53 |
Curtis Hovey |
juju: importance |
Undecided |
Critical |
|
| 2016-09-30 16:23:00 |
Curtis Hovey |
juju: milestone |
|
2.0.0 |
|
| 2016-09-30 16:41:37 |
Alexis Bruemmer |
juju: assignee |
|
Alexis Bruemmer (alexis-bruemmer) |
|
| 2016-10-04 22:16:16 |
Alexis Bruemmer |
juju: status |
Triaged |
Invalid |
|
| 2016-10-04 22:56:46 |
Alexis Bruemmer |
tags |
ci packaging regression |
ateam ci packaging regression |
|
| 2016-10-06 01:29:17 |
Curtis Hovey |
juju: milestone |
2.0.0 |
|
|
| 2016-10-06 01:29:20 |
Curtis Hovey |
juju: assignee |
Alexis Bruemmer (alexis-bruemmer) |
|
|
| 2016-10-25 17:06:36 |
Nicholas Skaggs |
bug task added |
|
juju-core (Ubuntu) |
|
| 2016-10-25 17:06:47 |
Nicholas Skaggs |
juju-core (Ubuntu): status |
New |
In Progress |
|
| 2016-10-25 17:09:02 |
Nicholas Skaggs |
juju-core (Ubuntu): assignee |
|
Nicholas Skaggs (nskaggs) |
|
| 2016-10-25 17:20:28 |
Nicholas Skaggs |
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.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
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.bootstrap tools.go:74 found 15 packaged agent binaries
..
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.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
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. |
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.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
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.bootstrap tools.go:74 found 15 packaged agent binaries
..
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.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
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-manual-provider ensuring juju works with the next release before a juju update will be disabled per the bug.
[Verification]
The autopkgtest future-manual-provider should now be skipped with
SKIP: Juju won't bootstrap unknown without published agent (LP:1629376) |
|
| 2016-10-25 17:21:54 |
Nicholas Skaggs |
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.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
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.bootstrap tools.go:74 found 15 packaged agent binaries
..
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.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
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-manual-provider ensuring juju works with the next release before a juju update will be disabled per the bug.
[Verification]
The autopkgtest future-manual-provider should now be skipped with
SKIP: Juju won't bootstrap unknown without published agent (LP:1629376) |
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.manual init.go:120 series: zakkety, characteristics: arch=amd64 cpu-cores=1 mem=3855M
..
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.bootstrap tools.go:74 found 15 packaged agent binaries
..
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.com/juju/juju/cmd/juju/commands/bootstrap.go:738: failed to bootstrap model} {github.com/juju/juju/tools/list.go:19: no matching tools available}])
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-manual-provider ensuring juju works with the next release before a juju update will be disabled per the bug.
[Verification]
The autopkgtest future-manual-provider should now be skipped with
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://autopkgtest.ubuntu.com/packages/j/juju-core/. |
|
| 2016-10-26 15:01:13 |
Mathieu Trudel-Lapierre |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-10-26 15:01:13 |
Mathieu Trudel-Lapierre |
bug task added |
|
juju-core (Ubuntu Xenial) |
|
| 2016-10-26 15:01:23 |
Mathieu Trudel-Lapierre |
juju-core (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-10-26 15:02:45 |
Mathieu Trudel-Lapierre |
juju-core (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-10-26 15:02:53 |
Mathieu Trudel-Lapierre |
juju-core (Ubuntu Xenial): assignee |
|
Nicholas Skaggs (nskaggs) |
|
| 2016-10-26 15:02:59 |
Mathieu Trudel-Lapierre |
juju-core (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2016-10-26 15:03:14 |
Mathieu Trudel-Lapierre |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-10-27 19:27:25 |
Brian Murray |
juju-core (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-10-27 19:27:29 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2016-10-27 19:27:32 |
Brian Murray |
tags |
ateam ci packaging regression |
ateam ci packaging regression verification-needed |
|
| 2016-10-28 17:36:38 |
Nicholas Skaggs |
tags |
ateam ci packaging regression verification-needed |
ateam ci packaging regression verification-done |
|
| 2016-11-14 20:11:59 |
Launchpad Janitor |
juju-core (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
