Comment 18 for bug 1681278

You mentioned your YAML for configuring MAAS, but you don't have an http-proxy set in that configuration.

It isn't quite clear what you mean by 'looping at the same step', is the issue that we are requesting a machine from MAAS, and MAAS is responding with a machine that it claims will be started, but that machine is actually failing to start?

Are you able to use the MAAS GUI to actually provision a machine directly (Acquire Node)?

It sounds like you do a have an HTTP Proxy, so its possible you have to configure the Apt HTTP Proxy in MAAS.

In both cases the MAAS Response has this line:
        "status": 9,
Which looking at MAAS source I find:
    #: The node is being installed.
    DEPLOYING = 9
    #: The node has been allocated to a user and is ready for deployment.
    ALLOCATED = 10

That means that MAAS is trying to create and initialize the machine, but it never gets to 'status: ALLOCATED' which is the point where maas has a functioning machine and has handed off control of that machine to Juju for us to start configuring the machine.

To debug the MAAS failures will probably require interacting with the MAAS team. The first step would be to make sure you can Allocate a machine (such that it gets all the way to where you can SSH in as the 'ubuntu' user).