2.1 agents can fail to read from 2.2 controllers
Bug #1697936 reported by
John A Meinel
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
| 2.1 |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
If you upgrade a Juju controller from 2.1 to 2.2, it is possible that some agents will start failing with messages about incomplete JSON and closed connections.
This happens when you have very large Config being set for units. In 2.2 the websocket library we use will send chunked responses if the content size gets large enough. 2.1 does not support chunked messages.
At the moment, the only plan for 'fixing' this is to upgrade to 2.2 for the agents.
| Changed in juju: | |
| status: | Triaged → Fix Committed |
| milestone: | none → 2.2.0 |
| Changed in juju: | |
| milestone: | 2.2.0 → 2.2.1 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
