firewaller should be more resilient to missing instances
Bug #2034717 reported by
Simon Richardson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Confirmed
|
High
|
Unassigned | ||
Bug Description
If we don't have an instance then we shouldn't bounce the firewaller worker, instead we should log it and then continue.
| Changed in juju: | |
| assignee: | Simon Richardson (simonrichardson) → nobody |
| Changed in juju: | |
| milestone: | 2.9.45 → 2.9.46 |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | 2.9.46 → none |
| tags: | added: bitesize |
To post a comment you must log in.
The next 2.9.46 candidate release will not include a fix for this bug and we don't plan on any more 2.9 releases. As such it is being removed from its 2.9 milestone.
If the bug is still important to you, let us know and we can consider it for inclusion on a 3.x milestone.