juju reporting cryptic error when trying to upgrade a machine with a full filesystem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christian Muirhead |
Bug Description
Hi,
Controller is running 2.3.8, machine agent on a hosted model is running 2.3.7
The controller is logging the following messages :
2018-07-18 13:50:21 DEBUG juju.apiserver httpcontext.go:298 sending error: 400 failed to write agent binaries: write tcp 10.X.Y.
2018-07-18 13:50:21 WARNING juju.apiserver log.go:172 http: multiple response.
2018-07-18 13:50:21 ERROR juju.apiserver tools.go:62 cannot write response: http: wrote more than the declared Content-Length
It turns out that this be because the juju machine agent on 1.2.3.4, currently 2.3.7, is trying to download the 2.3.8 agent but fails because its filesystem is full.
As soon as I cleared some space on the filesystem, the machine agent upgraded itself to 2.3.8.
I believe juju should handle full filesystems better, including logging.
Thanks
tags: | added: canonical-is |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Christian Muirhead (2-xtian) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
@Junien Fridrick,
This a nice report - thank you!
Any suggestions on how juju could "handle full filesystems"? :D