Race condition with add-machine and deploy commands
Bug #1776279 reported by
Peter Matulis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
It seems there is a race condition when the 'add-machine' and 'deploy' commands are used in quick succession.
juju bootstrap --no-gui aws aws
juju add-machine -n 2
juju deploy mysql
juju status
Only two machines get spawned and MySQL is deployed upon machine '0', instead of machine '2'.
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 1776279] [NEW] Race condition with add-machine and deploy commands | #1 |
| Changed in juju: | |
| importance: | Undecided → Medium |
| status: | New → Incomplete |
Revision history for this message
| Peter Matulis (petermatulis) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
If you have done "juju add-machine" then it is available as a "provisioned
but unused" machine, so it can be used for "juju deploy mysql".
I would expect it to be deployed to machine 0 if you haven't explicitly put
anything else there.
On Mon, Jun 11, 2018 at 10:47 PM, Peter Matulis <<email address hidden>
> wrote:
> Public bug reported:
>
> It seems there is a race condition when the 'add-machine' and 'deploy'
> commands are used in quick succession.
>
> juju bootstrap --no-gui aws aws
> juju add-machine -n 2
> juju deploy mysql
> juju status
>
> Only two machines get spawned and MySQL is deployed upon machine '0',
> instead of machine '2'.
>
> https:/
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
>
> ** Tags: docteam
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> Race condition with add-machine and deploy commands
>
> To manage notifications about this bug go to:
> https:/
>