ab17182
commented
12 months ago Hi tandrez, funnily enough, I just started playing with MAAS this weekend and got to the same point where a W11 VM gets built fine but ends in a "Failed deployment" state:
I used this as a guide: https://github.com/canonical/packer-maas/blob/d16375241ed5b8f196e3b35f1e4e5c0b9bec41f3/windows10/README.md
I never did create a cloudbase-init-unattend.conf file because the walk-through in the above never mentions it but I saw that you did. Where does that file need to reside? Also, did you use the same guide above or did you use something else? Only reason I ask is because it seems like the information is really sparse. I decided that I'd start putting a Terraform template together that'd build the VM that the MAAS rack+region server be installed on in Proxmox and use Ansible to automate the installation of MAAS and then look to see if I can automate the building of a WIndows Imaging environment using Ansible+Packer and then share it with everyone. Basically it'd be the equivalent of "Kubespray" for MAAS. All people would do is provide their own Windows ISO and it'd just add to MAAS with it ready to be deployed without a failed deployment state at the end. It's a real shame the product doesn't just do this out of the box.
I saw this was posted on June 27th so quite some time had passed. Hopefully you read this and can get back to me to let me know whether you fixed it or still have issues.
ader1990
Hi,
I'm using Canonical MAAS to deploy Windows 11 and 2022 on baremetal desktops and servers respectively. At the end of the deployment, the machine boots successfully in Windows and I can login without problem. The problem is that the machine hangs in the "Deploying" state in MAAS and eventually change to "Failed deployment" after the deployment timeout (30min). I have figured out that the issue concerns Cloudbase-Init. The logs indicate that it cannot retrieve the metadata from MAAS with an HTTP error 401 Unauthorized (please see log exctract below).
cloudbase-init-unattend.log:
cloudbase-init-unattend.conf:
The thing is that I can access the metadata URL with a web browser on the machine without error (HTTP 200) and when I manually start the cloudbase-init service on the machine, it works (the machine reboots and change to "Deployed" state in MAAS if I do it before the deployment timeout expiration).
I have tried increasing the
retry_countparameter to100in case the network was not ready but it does not solve the problem.Link to the thread in MAAS Discourse with more history: Need help to deploy Windows 11 custom image
Any help would be greatly appreciated.