[2.5] Pod VMs failing to load ldlinux.c32

[Vern Hart]

We're seeing an issue at a customer site where pod VMs are failing to commission.

This could be related to the vlan 0 issue (noted here: https://bugs.launchpad.net/maas/+bug/1805920) since the pod VMs on infra1 (where the dhcp server is) commissioned without error.

This is with maas 2.5.0. Since the last deployment where we didn't see this issue was on 2.4.3, we're temporarily redeploying with 2.4.3 (from https://code.launchpad.net/~mpontillo/+archive/ubuntu/maas-2.4/) to see if the issue goes away.

[Vern Hart (vern)]

Rolling back to 2.4.3 did indeed resolve the pod VM commissioning problem. Now we need to determine what regressed.

[Mike Pontillo (mpontillo)]

In the 2.5 environment, can you check that the nginx process is properly serving up each image?

(Just checking: I assume all of the MAAS servers been upgrade to 2.5...?)

Can you try the following command to make sure the boot loader is present and available on each rack controller via both HTTP and TFTP?

    curl -I http://<rack-controller>:5248/images/ldlinux.c32
    curl -s tftp://localhost/ldlinux.c32 | sha1sum

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]