canonical / maas-anvil

A snap for managing charmed MAAS deployments.
https://maas.io
Apache License 2.0
3 stars 7 forks source link

Uploading custom images via haproxy doesn't work #63

Open bjornt opened 2 months ago

bjornt commented 2 months ago

I have a three-node deployment where haproxy is configured to use a VIP.

If I point the maas client to port 80, it doesn't matter if it's the VIP or the real IP, the command to upload the image succeeds.

However, if I look at the UI, I can see that the status of the image is "Queued for download". Also, if I look at the filesystem, I can see that there's an .incomplete file for the image on two of the regions, and on the third it's completely missing.

If I instead point the client to the 5240 port, which goes directly to the region server, the image gets uploaded correctly.

r00ta commented 2 months ago

The issue here is that we are hardcoding the port 5240 in the temporal workflow activity https://github.com/canonical/maas/blob/d869acf9b6e4e3ee27d80eeb2e701d3c9fa3e22b/src/maasserver/workflow/bootresource.py#L148