juju can't deploy MAAS VM nodes, 16.04 deployed instead of 18.04

[Imran Khakoo]

I'm using MAAS with a mixture of bare metal and VM nodes. My main purpose is to test Ubuntu 18.04 in an MAAS+juju+Openstack use case.

As I have done with 14.04 and 16.04, I created VMs, copied ssh keys and used virsh as the power config in MAAS. VM and bare metal nodes were enlisted and commissioned correctly.

I then linked juju and MAAS the usual way, via "juju add-credential maas".

The problem I'm facing now is, when I try to bootstrap juju to a VM node, the MAAS status for that VM node changes to "deploying" but the VM doesn't turn on. When I do a "virsh list", I can see the VM is off. MAAS web UI correctly shows the VM is off. If I manually deploy 18.04 to that VM via MAAS, it deploys correctly. It seems something may be wrong in the juju-MAAS-virsh coupling?

Additionally, when I bootstrap to a bare metal node, the bootstrap succeeds, but 16.04 is deployed, not 18.04. Is there a way to force 18.04 to be deployed?

juju version
2.3.2-bionic-amd64

MAAS version: 2.3.0 (6434-gd354690-0ubuntu1)

[John A Meinel (jameinel)]

Are you doing "add-machine" or are you deploying a charm? If you are
deploying a charm, does it support bionic as a series, is it the default
series?

You can probably set "default-series" as a model-config to request, or
"juju bootstrap --bootstrap-series=bionic".

I don't know the specific issue around VM showing up as deploying but not
being turned on. We'd need more logging, etc, to understand what is going
on there.

On Mon, Jan 22, 2018 at 11:07 AM, Imran Khakoo <email address hidden>
wrote:

> Public bug reported:
>
> I'm using MAAS with a mixture of bare metal and VM nodes. My main
> purpose is to test Ubuntu 18.04 in an MAAS+juju+Openstack use case.
>
> As I have done with 14.04 and 16.04, I created VMs, copied ssh keys and
> used virsh as the power config in MAAS. VM and bare metal nodes were
> enlisted and commissioned correctly.
>
> I then linked juju and MAAS the usual way, via "juju add-credential
> maas".
>
> The problem I'm facing now is, when I try to bootstrap juju to a VM
> node, the MAAS status for that VM node changes to "deploying" but the VM
> doesn't turn on. When I do a "virsh list", I can see the VM is off. MAAS
> web UI correctly shows the VM is off. If I manually deploy 18.04 to that
> VM via MAAS, it deploys correctly. It seems something may be wrong in
> the juju-MAAS-virsh coupling?
>
> Additionally, when I bootstrap to a bare metal node, the bootstrap
> succeeds, but 16.04 is deployed, not 18.04. Is there a way to force
> 18.04 to be deployed?
>
>
> juju version
> 2.3.2-bionic-amd64
>
> MAAS version: 2.3.0 (6434-gd354690-0ubuntu1)
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1744652
>
> Title:
> juju can't deploy MAAS VM nodes, 16.04 deployed instead of 18.04
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1744652/+subscriptions
>

[Imran Khakoo (imrankhakoo)]

Hi, juju bootstrap --bootstrap-series=bionic worked. Thank you very much.