Oversized client machine log makes machine state stuck in "deploying"
Bug #1922620 reported by
Roy Zuo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.4 |
Won't Fix
|
Medium
|
Unassigned | |||
3.5 |
Won't Fix
|
Medium
|
Unassigned | |||
3.6 |
Triaged
|
Medium
|
Unassigned |
Bug Description
In /var/lib/
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.
Changed in maas: | |
importance: | Undecided → Low |
status: | New → Triaged |
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.
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.