Enforce hard event order guarantees during critical sequences
Bug #2059972 reported by
Leon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
During steady-state (after startup), idempotency is easy. Not so during startup (unless we go with "common exit hook", in which case event type doesn't matter anymore).
Juju should enforce hard event order guarantees during critical sequences:
- Startup sequence. Example: start always after pebble-ready; peer relation joins always before regular relations.
- Upgrade sequence. Example: strictly upgrade-charm -> config-changed -> pebble-ready (if appl.) -> start
- Teardown sequence. Example: peer relation departs only after all regular relations are gone (https:/
| description: | updated |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
