deployment failure when bundle includes charm2 published charm
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-quickstart |
In Progress
|
High
|
Brad Crittenden | ||
Bug Description
juju-1.
juju-quickstart
Test bundle with ubuntu and benchmark-gui:
$ cat test.yaml
services:
ubuntu:
charm: cs:trusty/ubuntu-5
bui:
charm: cs:trusty/
series: trusty
Quickstart accepts deployment and returns to the prompt, but doesn't actually deploy anything after juju-gui (i let it sit > 1 hour):
$ juju-quickstart --debug test.yaml
...
juju quickstart v2.2.4
contents loaded for bundle (services: 2)
...
requesting a deployment of bundle with the following services:
bui, ubuntu
21:27:18 DEBUG juju:161 API message: --> {"Request": "Import", "Params": {"YAML": "series: trusty\nservices:\n bui:\n charm: cs:trusty/
21:27:18 DEBUG juju:172 API message: <-- {"Response": {"DeploymentId": 0}, "RequestId": 1}
bundle deployment request accepted
use the GUI to check the bundle deployment progress
...
The GUI doesn't show much, but the notification area has a tooltip box that briefly says:
Updated status for deployment id: 0
The deployment is currently in progress
| Francesco Banconi (frankban) wrote | #1 |
| Changed in juju-quickstart: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Brad Crittenden (bac) wrote | #2 |
| Changed in juju-quickstart: | |
| assignee: | nobody → Brad Crittenden (bac) |
| status: | Triaged → In Progress |
This is related to bug 1531999
The GUI charm uses the deployer, and the deployer fails when deploying a charm that's only on the new charm store, as it still uses the legacy one. Once the deployer bug is fixed, we need to include the new deployer release in the juju gui charm.