When a secret's tracked revision is removed, it cannot track a new one
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Caner Derici |
Bug Description
Juju 3.4.2, microk8s.
Given an application secret and a unit that is tracking a non-latest revision, if the charm executing on that unit removes the tracked revision, then it seems to get into a broken state (with respect to the secret) that it cannot get out of, in that it can't get the secret (fine - the revision is gone), but it also can't `--refresh` to move to a newer revision either.
To reproduce:
Given this charm:
```python
class TestingSecretRe
def __init__(self, framework: ops.Framework):
def _on_install(self, event):
def _on_set(self, event):
secret = self.model.
def _on_get(self, event):
secret = self.model.
def _on_remove(self, event):
secret = self.model.
```
Pack and deploy, and then run:
```
juju run testing-
juju run testing-
juju run testing-
juju run testing-
```
Changed in juju: | |
milestone: | none → 3.4.3 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
assignee: | nobody → Caner Derici (cderici) |