Temporal workflow deadlock
Bug #2085160 reported by
Anton Troyanov
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.7 | |||||
3.6 |
In Progress
|
High
|
MAAS Lander | |||
3.7 |
Fix Committed
|
High
|
Anton Troyanov |
Bug Description
ERR Workflow panic Attempt=4 Error="Potential deadlock detected: workflow goroutine \"root\" didn't yield for over a second" Namespace=default RunID=d632074b-
Oct 22 01:24:21 ivcontroller maas-agent[31561]: WRN Failed to process workflow task. Attempt=4 Error="Potential deadlock detected: workflow goroutine \"root\" didn't yield for over a second" Namespace=default RunID=d632074b-
The failing workflow is:
WorkflowID=
We might want to wrap this logic into local activity instead.
Related branches
maas:auto-backport-2085160-3.6
- Jacopo Rota: Disapprove
- Anton Troyanov: Approve
- MAAS Lander: Needs Fixing
-
Diff: 392 lines (+158/-108)4 files modifiedsrc/maasagent/internal/dhcp/service.go (+21/-21)
src/maasagent/internal/httpproxy/service.go (+73/-70)
src/maasagent/internal/power/service.go (+29/-17)
src/maasagent/internal/workflow/utils.go (+35/-0)
~troyanov/maas:fix-2085160
- Javier Fuentes: Approve
- MAAS Lander: Approve
-
Diff: 392 lines (+158/-108)4 files modifiedsrc/maasagent/internal/dhcp/service.go (+21/-21)
src/maasagent/internal/httpproxy/service.go (+73/-70)
src/maasagent/internal/power/service.go (+29/-17)
src/maasagent/internal/workflow/utils.go (+35/-0)
description: | updated |
To post a comment you must log in.