Oversized client machine log makes machine state stuck in "deploying"

Bug #1922620 reported by Roy Zuo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Triaged
Medium
Unassigned
3.4
Won't Fix
Medium
Unassigned

Bug Description

In /var/lib/maas/http/nginx.conf, client_max_body_size is set to 10M, which means the biggest file upload maas-http would take is 10MB.

If a post install script generates output larger than this, log uploading will fail with 413 status code after a few attempts. This would surprise maas and the machine would be stuck in "deploying" state even if post install script is successfully executed.

> sleeping 32.: HTTP Error 413: Request Entity Too Large

Personally I think 10M is a reasonable size for max upload size, but there should be same safeguarding for situations when the file size is larger than this.

Tags: sts
Alberto Donato (ack)
Changed in maas:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

The max size was bumped to 10M due to this issue: https://bugs.launchpad.net/maas/+bug/1807058 There seems to be no reason to ever reject the client response due to the size. We will change the nginx config to lift the max size limit.

Changed in maas:
importance: Low → Medium
milestone: none → 3.4.0
Alberto Donato (ack)
Changed in maas:
milestone: 3.4.0 → 3.4.x
Changed in maas:
milestone: 3.4.x → 3.5.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.