We need some more information.
Can you please identify your version and build
We need to know the version and build (and packaging format) that you’re running. Here’s how to get that info:
If you’re using a snap
If you’re using a snap, execute
snap listmaas at the command line, which will return some lines like this:
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 it hangs at the second PXE boot prompt. Is there anything to indicate that it can’t find an image for that second boot, for example?
Try and 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. This might be a little complicated with Juju, but anything you can tell us may help.
Any relevant screenshots?
Can you get a console on the R430 to watch the boot process, or lack thereof? If so, screenshots might save a lot of typing. You can just upload them into your comment.
Locate and capture logfiles
I dunno if any logfiles will help with this, but you might check these:
- the rsyslog file of the affected machine(s), if it exists.
On snap, they’re in:
If you’re using Debian packages, they’re somewhere else:
Ideally, you’d want to put these in a pastebin and link the pastebin location in your comment.
Thanks for this. We’ll very likely need this additional info to sort this.