MAAS failed to respond to POST'd deploy request but still deployed node
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Critical
|
Unassigned | ||
2.2 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
maas version: 2.2.2-6099-
juju version: 2.2.4-0ubuntu1~
=Description=
When using juju to deploy a bundle to MAAS, juju received an EOF/no response from the MAAS server when POST'ing to MAAS to deploy the node:
logsink.
MAAS did not log this POST request in regiond.log. However, the node started its deploying process and eventually reach deployed. Since juju got no response from MAAS when trying to deploy the node, juju considered the node in an error state and the deployment of the bundle failed.
Here's the summarized event log for the node: http://
MAAS and juju logs will be attached. This is an HA setup with 3 region controllers and 2 rack controllers. There are quite a "few could not serialize access due to concurrent update" errors in the logs.
=Expected behavior=
MAAS should always return a response to the client.
=Reproduction steps=
I don't have a good way to reproduce the reliably. I saw similar behavior in bug 1717301 - it seems like they could be the same root cause.
tags: | added: foundations-engine |
Changed in maas: | |
status: | New → Incomplete |
Changed in maas: | |
importance: | Undecided → Critical |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.0beta2 |
tags: | added: internal |
Changed in maas: | |
status: | New → Triaged |
Changed in maas: | |
milestone: | 2.3.0beta2 → 2.3.0beta3 |
Changed in maas: | |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | Triaged → Incomplete |
assignee: | Blake Rouse (blake-rouse) → nobody |
Changed in maas: | |
status: | Incomplete → Invalid |
Changed in maas: | |
milestone: | 2.3.0beta3 → none |
Why is this marked incomplete?