Comment 9 for bug 1314409

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I'm doing some debugging by looking in the maas access log.

It looks like an environment was destroying its environment around this time:

10.245.0.190 - - [29/Apr/2014:16:09:23 +0000] "POST /MAAS/api/1.0/nodes/node-9df8a42a-c4cd-11e3-824b-00163efc5068/?op=release HTTP/1.1" 200 717 "-" "Go 1.1 package http"

and there we can see the node in question getting released.

Shortly after in the log, there's a load of DELETEs being issued to remove the environment files. So far, so good.

The next time this node is mentioned is hours later when I see it in these two entries:

10.245.0.182 - - [29/Apr/2014:20:44:01 +0000] "POST /MAAS/api/1.0/nodes/?op=acquire HTTP/1.1" 200 723 "-" "Go 1.1 package http"
10.245.0.188 - - [29/Apr/2014:20:44:01 +0000] "POST /MAAS/api/1.0/nodes/?op=acquire HTTP/1.1" 200 723 "-" "Go 1.1 package http"
...
10.245.0.182 - - [29/Apr/2014:20:44:02 +0000] "POST /MAAS/api/1.0/nodes/node-9df8a42a-c4cd-11e3-824b-00163efc5068/?op=start HTTP/1.1" 200 723 "-" "Go 1.1 package http"
10.245.0.188 - - [29/Apr/2014:20:44:02 +0000] "POST /MAAS/api/1.0/nodes/node-9df8a42a-c4cd-11e3-824b-00163efc5068/?op=start HTTP/1.1" 200 723 "-" "Go 1.1 package http"

Two IP addresses are simultaneously trying to start the same node.

Sadly it does look like a bug in MAAS from this evidence.