allow juju-gui to run on machine zero in azure
Bug #1343410 reported by
Jay R. Wren
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-quickstart |
Triaged
|
High
|
Unassigned | ||
Bug Description
juju 1.20 now supports disabling AS: availability-
quickstart could expose this and allow deploying juju-gui to machine 0 for demo purposes
| Changed in juju-quickstart: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Francesco Banconi (frankban) wrote | #1 |
| Changed in juju-quickstart: | |
| importance: | Low → High |
To post a comment you must log in.
From a duplicate bug:
From email:
> When creating an Azure environment, the availability-
> "true" by default. This prevents some Juju commands to run, especially the
> co-location commands (juju deploy --to X <charm> doesn't work)
>
> However, when the flag is turned to "false" those commands are enabled
> again.
>
> juju-quickstart doesn't seem to follow the same logic. Its documentation
> says that it's going to *try* to colocate the state server and the GUI. On
> Azure, it apparently decides that it's never possible to colocate, which
> means quickstart always end up with 2 units.
>
> Is there a way that can be changed so that when the availability set is
> false, then GUI gets deployed to machine 0 (and in this case I can write a
> feature request) or is there a good reason for that to happen as it does?