I am using Maas 3.3/stable successfully while deploying the official Ubuntu 20.04 Maas Image on a server. I can commission the server (using ubuntu 20.04 also), deploy and release continuously without any issue.
But if I try to deploy an official Ubuntu 18.04 or 22.04 image it doesn’t work. (with the same server, same settings everywhere). The process status gets stuck on performing PXE boot as per below:
I have already tried with multiple MaaS Versions like 3.4/edge, 3.2/stable but it is no different. 20.04 always works flawlessly 18.04 and 22.04 don’t.
Any tips?
Just some more detail.
I thought that the issue could be with the image downloading or something since the image version that always worked across multiple MaaS versions was the default one that is included (20.04).
But I tried with some more Ubuntu versions downloaded after Maas Installation and here are the results (always maintaining the same setup, settings and repeatable tests (multiple deploys releases and achieving the same result):
Ubuntu 23.04 - Works
Ubuntu 23.10 - Works
Ubuntu 22.10 - Doesn’t work (same errors as 22.04)
I wonder if you can capture the same console output for a 20.04 boot. Is there something obvious that happens there that doesn’t happen in the other versions?
I would guess that commissioning with 22.04 or 18.04 would also fail but it might be useful to check.
Another thought I had was you might have a custom curtin_preseed for 20.04 but not other versions. But I don’t think you’re getting far enough for that to matter.
Is this restricted to a specific server or is this behavior with all servers you deploy?
I would want to see more of the failed deployments’ console output. If you could screen-record the boot process, perhaps you’ll see an error earlier in the process that will give some hints.
Not sure what’s going on, these are just my initial thoughts on the problem.
I’m having a very similar issue with ipv6. Hosts boot with no apparent consistency.
Half of the times they boot and download the squashfs, the rest they fail with “network is unreachable”.
I have captured rack and gateway traffic and screen recorded the hosts since I can’t wrap my head around this, it almost feels like a sneaky race condition.
All of these recordings contain sensitive data though, is there any way I can share them with the MAAS team in order to debug this?
Moreover, I’ve set up a debugging host with a bridge (2 interfaces that pass through all traffic) to capture packets just before the host, and regardless of which distro I boot it always succeeds with no error; as soon as I plug the host back directly into the switch it starts failing, hence my suggestion of a race condition.
if you are a Canonical customer you should open a case on the customer portal
if you are a community user since there is no formal agreement it’s up to you to share your logs/data with Canonical and/or the community.
For example, you can use whatever tool you prefer (google drive, mail, whatever) and give somebody (for example, me) access. I can then upload your logs to our internal storage and give read permissions to the team
I’m a community user. I’ll share the files to your email as replacing all my data in the logs would be way too long and break the packet captures, not to mention editing the screen recordings.
If the solution is related to this thread I’ll post it here as well.
Thanks!
yup sounds good, if you could also open a bug with all the information you have it would be great. I will then attach the logs to that bug (will be readable only for people within Canonical)
I confirm that with ubuntu 23.10 it works perfectly. It most likely is due to the bug I linked in the previous comment.
So much network debugging for nothing :’)
Is there anything I can do to force ubuntu 23 as commissioning OS? It only lets me choose LTS distros.
thanks for the input.
Right now I only have one server to test.
I am going to test with another server if possible to see if it is something related to this one and then post the videos if I can
BR
Thanks but since we only support LTS for commissioning it’s not my priority at the moment Only one person asked for it, in case you have the same need (but from your last message I guess not) you might coordinate with him to sort it out
Alright, in case I face any issues I’ll contact you.
In the meantime I’ll keep using 23.10 to commission while I wait for the patched kernel for 22.04.
Only one person asked for it, in case you have the same need (but from your last message I guess not) you might coordinate with him to sort it out