MaaS deployment failing

I’m running MaaS v2.9.2 and am running into an issue where node OS (Ubuntu 20.04 LTS) are failing. The commissioning step runs without any errors.

The deployment failure event is described as “Node installation failure - ‘cloudinit’ running modules for final” and there is no information contained in the installation log accessed through the web UI. Is there a location that stores this logging locally?

Wondered if there are any tips or suggestions for debugging this issue.


Hi @arnsong

Can you send us some information?

Identify your version and build

We need to know the version and build (and packaging format) that you’re running. You mentioned 3.1, but we need a little more information.

If you’re using a snap

If you’re using a snap, execute snap list maas at the command line, which will return some lines like this:

$ snap list maas
Name  Version                       Rev    Tracking     Publisher   Notes
maas  3.0.0~beta2-9796-g.2182ab55f  13292  latest/edge  canonical✓  -

Please add the output of that command to a comment on this post.

If you’re using a Debian package

If you’re using a deb, execute apt list maas at the command line, and enter whatever it returns into a comment to this post, as in the snap example above.

Using CLI, UI, or API?

Next, you’ll need to specify which interface you’re using, and generally what command(s) you were attempting.

Explain what happens

Being as concise and specific as you can, please explain a little more about what seemed to go wrong. You mentioned that commissioned machines don’t show any storage. You also mentioned that you can “unstick” the controllers from waiting for a rack controller sync. Can you show us some screenshots of the machines that commission with no storage, for example?

Explain how to reproduce your issue

In addition to the explanation above, you should create a step-by-step list of what you did to reproduce the problem. Sounds like it’s pretty simple – just try to commission a machine – but we’d like to be sure.

Take relevant screenshots

If you think it will help – especially when using the UI – try and capture screenshots of any unexpected results or ambiguous actions. Your goal isn’t to document your experience in pictures, but to provide a visual reference where verbal descriptions fall short. Name these so you can sync them with your explanation (e.g., “screenshot-1”). You can just upload them into your comment.

Locate and capture logfiles

If at all possible, capture logfiles for the time period surrounding your error situation. On snap, these files are located as follows:

  • /var/snap/maas/common/log/maas.log
  • /var/snap/maas/common/log/regiond.log
  • /var/snap/maas/common/log/rackd.log
  • /var/snap/maas/common/log/rsyslog/$MACHINE_NAME/$RELEVANT_DATE/messages

If you’re using packages, you’ll find the files in these locations:

  • /var/log/maas/maas.log
  • /var/log/maas/regiond.log
  • /var/log/maas/rackd.log
  • /var/log/maas/rsyslog/$MACHINE_NAME/$RELEVANT_DATE/messages

Ideally, you’d want to put these in a pastebin and link its location in your comment.

Thanks for this. We’ll need this additional information in order to try and figure out what’s going on.

@arnsong, did you ever figure this out? if not, there’s info we need to help (see the previous reply).