POST /async returns 504 instead of 408
Bug #1455501 reported by
Andreas Hasenack
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Charm |
Fix Released
|
High
|
Free Ekanayaka | ||
Bug Description
When deploying landscape via the trunk charm, the POST requests to /ajax are handled by the appserver first, and then redirected to the async process.
This somehow broke the auto-refresh of the progress bar in the region deploy page, maybe even for activities in general. These POSTs to /ajax now return 504 and the client (browser) doesn't reconnect anymore. It used to receive a 408, which the client knows how to interpret and handle, and reconnect.
Related branches
lp:~free.ekanayaka/landscape-charm/haproxy-timeout
- Fernando Correa Neto (community): Approve
- Chris Glass (community): Approve
- 🤖 Landscape Builder: Approve (test results)
-
Diff: 47 lines (+12/-0)2 files modifiedlib/relations/haproxy.py (+8/-0)
lib/relations/tests/test_haproxy.py (+4/-0)
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #1 |
| tags: | removed: kanban |
| Changed in landscape: | |
| assignee: | nobody → Free Ekanayaka (free.ekanayaka) |
| Changed in landscape: | |
| status: | New → In Progress |
| tags: | added: kanban squad-beta upgradable-charm |
| information type: | Proprietary → Public |
| affects: | landscape → landscape-charm |
| Changed in landscape-charm: | |
| status: | In Progress → Fix Committed |
| tags: | removed: kanban |
| Changed in landscape-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
