Instance key stability in refresh requests
Bug #1944582 reported by
Maximiliano Bertacchini
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Heather Lanigan | ||
2.9 |
Fix Released
|
High
|
Heather Lanigan |
Bug Description
In order to collect, aggregate, and track accurate metrics & kpis for parallel installs, i.e. multiple instances of the same charm in a model, the snap store needs *stable* instance keys across refresh requests over time. Instance keys are currently randomly generated for each context item on each request, afaik.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Heather Lanigan (hmlanigan) |
milestone: | none → 3.0.0 |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
PR for juju 3.0 /github. com/juju/ juju/pull/ 13379
https:/
When the refresh action is called, a unique, stable instance-key will be set, equivalent to <model- uuid>:a# <application- name>. Any instance-key which is only a uuid, should not be considered stable.
All charmhub metrics work in juju will be back ported to 2.9 shortly.