juju add-machine still assumes precise (maas)

[Mark W Wenning]

set up a maas system on Ubuntu 14.04 with 2 nodes, both set with Release = trusty.
environment.yaml is set for basic maas, relevant snippet follows:
 # https://juju.ubuntu.com/docs/config-maas.html
    maas:
        type: maas

        # maas-server specifies the location of the MAAS server. It must
        # specify the base path.
        #
        maas-server: 'http://192.168.0.2/MAAS/'

        # maas-oauth holds the OAuth credentials from MAAS.
        #
        maas-oauth: 'bhgerCSAq3PbBcLUtp:qjJE2qQBBCVpt3shSZ:VqZ2HYmqFfqAjLWaXyYUYzbprHB7aBQB'
        bootstrap-timeout: 1200
        bootstrap-retry-delay: 30

"juju bootstrap --upload-tools --debug" works OK, brings up first machine
subsequent "juju add-machine" commands will try to add a precise node, of which there are none:
test@test-Latitude-14-Rugged-Extreme-7404:~$ juju add-machine
test@test-Latitude-14-Rugged-Extreme-7404:~$ juju status
environment: maas
machines:
  "0":
    agent-state: started
    agent-version: 1.18.1.1
    dns-name: T110ii.maas
    instance-id: /MAAS/api/1.0/nodes/node-7533b9bc-d1e3-11e3-bfab-0c54a5f0ce34/
    series: trusty
  "1":
    instance-id: pending
    series: precise
services: {}

Adding "default-series: trusty" to environment.yaml does not seem to work either.

running: juju add-machine --series="trusty"
    will create the right machine, but machine will remain "pending" until the nodes ahead of it are destroyed
    with (for example) "juju destroy-machine 1".

Then the trusty machine will come up OK.

[John A Meinel (jameinel)]

I believe the need to kill the precise machine (destroy-machine 1) is
actually bug #1311676, which should have a fix available. (If we don't
have tools for a machine then it will fail cleanly rather than causing the
provisioner to go into a failure loop).

That fix should be available in 1.18.2, along with the fix so that
"--upload-tools" always provides both Precise and Trusty tools.

That said, I'm not sure what a plain "juju add-machine" without any extra
arguments is going to do, as it may depend on the platform that you are
calling it from.

John
=:->

On Sat, May 3, 2014 at 1:17 AM, Curtis Hovey <email address hidden> wrote:

> ** Changed in: juju-core
> Status: New => Triaged
>
> ** Changed in: juju-core
> Importance: Undecided => High
>
> ** Tags added: add-machine maas-provider
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1315473
>
> Title:
> juju add-machine still assumes precise (maas)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1315473/+subscriptions
>

[Ian Booth (wallyworld)]

If distro-info command is not available to use in order to find out the latest lts, then it defaults to provisioning a precise machine. The fix is to make the fallback trusty instead of precise.