Comment 9 for bug 1472711

Revision history for this message
Andreas Hasenack (ahasenack) wrote : Re: MAAS node has "failed deployment", juju just says "pending"

Here are apache logs from since I ran "juju add-machine" to select a node I prepared to fail:

10.96.10.86 - - [10/Jul/2015:20:10:46 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&op=list HTTP/1.1" 200 844 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:10:48 +0000] "POST /MAAS/api/1.0/nodes/?op=acquire HTTP/1.1" 200 825 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:10:49 +0000] "GET /MAAS/api/1.0/nodes/node-65d52b5c-546c-11e4-821d-2c59e54ace74/?op=details HTTP/1.1" 200 9149 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:10:49 +0000] "GET /MAAS/api/1.0/networks/?node=node-65d52b5c-546c-11e4-821d-2c59e54ace74 HTTP/1.1" 200 559 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:10:49 +0000] "GET /MAAS/api/1.0/networks/maas-eth0/?op=list_connected_macs HTTP/1.1" 200 898 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:10:49 +0000] "GET /MAAS/api/1.0/networks/maas-eth0/?op=list_connected_macs HTTP/1.1" 200 898 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:10:49 +0000] "POST /MAAS/api/1.0/nodes/node-65d52b5c-546c-11e4-821d-2c59e54ace74/?op=start HTTP/1.1" 200 842 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:11:01 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-65d52b5c-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 855 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:11:17 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-65d52b5c-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 855 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:11:49 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-65d52b5c-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 855 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:12:51 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-5c4d39da-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 844 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:12:54 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-65d52b5c-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 855 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:15:02 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-65d52b5c-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 856 "-" "Go 1.1 package http"
10.96.10.86 - - [10/Jul/2015:20:17:07 +0000] "GET /MAAS/api/1.0/nodes/?agent_name=4a4b73ac-1417-4b66-869e-9e335f194486&id=node-5c4d39da-546c-11e4-821d-2c59e54ace74&op=list HTTP/1.1" 200 844 "-" "Go 1.1 package http"

At this point, the node has failed already:
$ maas admin-atlas nodes deployment-status nodes=node-65d52b5c-546c-11e4-821d-2c59e54ace74
{
    "node-65d52b5c-546c-11e4-821d-2c59e54ace74": "Failed deployment"
}

Not to juju:
$ juju status
environment: scapestack-trusty
machines:
  "0":
    agent-state: started
    agent-version: 1.24.2
    dns-name: sekine.scapestack
    instance-id: /MAAS/api/1.0/nodes/node-5c4d39da-546c-11e4-821d-2c59e54ace74/
    series: trusty
    hardware: arch=amd64 cpu-cores=4 mem=16384M
    state-server-member-status: has-vote
  "2":
    agent-state: pending
    dns-name: barley.scapestack
    instance-id: /MAAS/api/1.0/nodes/node-65d52b5c-546c-11e4-821d-2c59e54ace74/
    series: trusty
    hardware: arch=amd64 cpu-cores=4 mem=16384M
services: {}
networks:
  maas-eth0:
    provider-id: maas-eth0
    cidr: 10.96.0.0/16

This is what apache logs when I run the MAAS CLI command:
10.172.68.106 - - [10/Jul/2015:20:19:44 +0000] "GET /MAAS/api/1.0/nodes/?op=deployment_status&nodes=node-65d52b5c-546c-11e4-821d-2c59e54ace74 HTTP/1.1" 200 361 "-" "Python-httplib2/0.8 (gzip)"

I don't see any such "deployment_status" in the apache logs that didn't come from my MAAS CLI run.