Non-leader units stuck on Waiting on relations: db
Bug #2019086 reported by
Diko Parvanov
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Charm |
Triaged
|
High
|
Unassigned |
Bug Description
using latest/stable revision 87, the leader is active/idle but the non-leader units are stuck:
landscape-server/0* active idle 0 10.5.1.130 Unit is ready
landscape-server/1 waiting idle 1 10.5.1.16 Waiting on relations: db
landscape-server/2 waiting idle 2 10.5.2.250 Waiting on relations: db
Removing and re-adding the db relation towards postgresql (using 14/stable rev 288) doesn't change anything.
Removing the 2 waiting units and adding again - same situation. On a single landscape-server unit there is no problem.
Changed in landscape-charm: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: cdo-qa foundations-enginer |
tags: |
added: foundations-engine removed: foundations-enginer |
To post a comment you must log in.
We are seeing this with SQA too, except that the leader is also in the `waiting on relations: db` state. We collected some crashdumps here: https:/ /oil-jenkins. canonical. com/artifacts/ a02a6b88- 187c-42dc- 91bc-38fb06db1e 85/generated/ generated/ lma-maas/ juju-crashdump- lma-maas- 2023-06- 03-17.19. 42.tar. gz