Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uploading custom images via haproxy doesn't work #63

Open
bjornt opened this issue Sep 3, 2024 · 1 comment
Open

Uploading custom images via haproxy doesn't work #63

bjornt opened this issue Sep 3, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@bjornt
Copy link

bjornt commented Sep 3, 2024

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
Copy link

r00ta commented Sep 3, 2024

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

@skatsaounis skatsaounis added the bug Something isn't working label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants