Add-unit with a KVM fails to warn about spaces

Bug #1804308 reported by Michael Skalka on 2018-11-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

When adding a kvm container unit of an existing service using `juju add-unit <service> --to kvm:<machine>` if there are multiple spaces available on that machine Juju will fail to warn the user and deploy the node resulting in the following error in the machine section of the juju status:

failed to start machine 0/kvm/0 (unable to setup network: no obvious space for container "0/kvm/0", host machine has spaces: "one", "undefined"), retrying in 10s (8 more attempts)

Richard Harding (rharding) wrote :

We should make this like the lxd code where if you've not used any spaces in the model yet we don't require you to bind endpoints. If you do have spaces work in the model then we require explicit placements to avoid guessing.

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.5.1

I do believe the same thing happens for an lxd container. Rereading this,
it sounds just that Michael would like a deploy time check of this rather
than a provisioning check.
We traditionally haven't done deploy time checks because the machines don't
exist until provisioned but for lxd/kvm:N we know the machine details.

There are edge cases we will want to be careful of. The machine N doesn't
have to be provisioned before you ask for a container, and you might be
mixing multiple locations at the same time (deploy takes -n and --to can be
given a list).

I do think it would be much better user experience, though.

John
=:->

On Wed, Nov 21, 2018, 00:50 Richard Harding <<email address hidden>
wrote:

> We should make this like the lxd code where if you've not used any
> spaces in the model yet we don't require you to bind endpoints. If you
> do have spaces work in the model then we require explicit placements to
> avoid guessing.
>
> ** Changed in: juju
> Status: New => Triaged
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Milestone: None => 2.5.1
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1804308
>
> Title:
> Add-unit with a KVM fails to warn about spaces
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1804308/+subscriptions
>

Ian Booth (wallyworld) on 2019-01-28
Changed in juju:
milestone: 2.5.1 → 2.5.2
Changed in juju:
milestone: 2.5.2 → 2.5.3
Changed in juju:
milestone: 2.5.3 → 2.5.4
Changed in juju:
milestone: 2.5.4 → 2.5.5
Changed in juju:
milestone: 2.5.6 → 2.5.8
Changed in juju:
milestone: 2.5.8 → 2.5.9
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers