[2.7.4] relation-changed events for container-scoped app relation data may fire for primary units before they see their own subordinate
Bug #1866828 reported by
Dmitrii Shcherbakov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
* Two apps, one primary, one subordinate;
* Both have two units;
* A leader subordinate writes app relation data to a container-scoped relation for all primaries to read;
* The first primary observes the leader subordinate (relation-joined) which then writes some data to the app relation data bag;
* The second primary comes up but gets a relation-changed event for the app relation data before it observes (relation-joined) its own subordinate - relation-list returns no units.
See https:/
summary: |
[2.7.4] relation-changed events for container-scoped app relation data - may fire for primary units before they see their subordinate + may fire for primary units before they see their own subordinate |
To post a comment you must log in.
I think this changes if you have relation-created, because then you know about the application and application data before you have to know about a single unit.
The potential patch in Juju is attached.
Essentially, you just look at application changes after you look for new units.