Relations fails with more than 3 applications
Bug #1905275 reported by
Archana krishnan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned |
Bug Description
We tried to replace init containers with relations in 2.8.6-bionic-amd64 ,we have some 4 applications where one is dependent on another.
If we have only 3 apps, App3 will wait for App2 and App2 will wait for App1 .This scenario(
If we bring in 4th Application, App2 has to wait for App1 and App3 has to wait for App2 and App4 has to wait for App3.This scenario (App1->
Track: https:/
Changed in juju: | |
status: | Incomplete → New |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 3.0.0 |
Changed in juju: | |
milestone: | 3.0.0 → 3.0.1 |
Changed in juju: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in juju: | |
milestone: | 3.0.2 → 3.0.3 |
To post a comment you must log in.
This sounds like it might be a design issue with the charms.
If you have a complex set of dependencies between apps, you probably want to code things so that the charms drop into a waiting state, rather than being blocked, if a relation is missing. They can then fire off appropriate events when the relation joins.
What framework are you using to write the charms?