0

I deployed a MaaS region+rack controller and tried to runcommissioning of 3 nodes on it.

First time I did it, it was a success, all the nodes were enlisted and commissioned really quickly, in, like, 10 minutes. Awesome!

But then I deleted one of them and tried to re-add it. It started commissioning again, and now this process takes forever.

I opened its IPMI console and I see that although the boot process is running more or less successfully, each step of cloud-init takes something like 2 minues.

Most of the queries from machine to MaaS API result in status 204:

tail -f /var/log/maas/regiond.log

2019-12-15 19:47:23 regiond: [info] 10.100.70.31 POST /MAAS/metadata/status/xaxfnw HTTP/1.1 --> 204 NO_CONTENT (referrer: -; agent: python-requests/2.18.4)
2019-12-15 19:47:23 regiond: [info] 10.100.70.31 POST /MAAS/metadata/status/xaxfnw HTTP/1.1 --> 204 NO_CONTENT (referrer: -; agent: python-requests/2.18.4)

As for the cloud-init scripts, they run fine, but take ~30 minutes altogether (as can be seen in IPMI interface):

enter image description here

As a separate issue, I often see MaaS frontend losing connection to its backend django server and being stuck in a state like this:

enter image description here

At the same time I'm connected over SSH to MaaS server and I'm sure that ssh conneciton is fine - it's displaying and updating regiond.log.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.