Comment 0 for bug 1604962

Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

A node reached the end of installation and was marked Failed Deployment, but I can't discover the reason it was marked that.

I've attached logs from the MAAS server, and the event log, and the install log.

In the event log we see this:
        {
            "type": "Node changed status",
            "level": "INFO",
            "node": "4y3hdg",
            "hostname": "hayward-11",
            "id": 1436389,
            "description": "From 'Deploying' to 'Failed deployment'",
            "created": "Wed, 20 Jul. 2016 01:01:00"
        },
        {
            "type": "Node installation",
            "level": "DEBUG",
            "node": "4y3hdg",
            "hostname": "hayward-11",
            "id": 1436388,
            "description": "'cloudinit' running modules for final",
            "created": "Wed, 20 Jul. 2016 01:01:00"
        },

In the install log we see this:
Length: unspecified [text/plain]
Saving to: '/dev/null'

     0K 138K=0s

2016-07-20 01:00:50 (138 KB/s) - '/dev/null' saved [2]

curtin: Installation finished.

This is from this run:

http://10.245.162.43:8080/job/pipeline_deploy/8151/console

This is with juju 2.0 beta 12 and maas 2.0 RC2.