Containerd relation not reconfigured after initial drop of relation
Bug #1983106 reported by
Adam Dyess
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Docker Registry Charm |
Fix Released
|
Undecided
|
Adam Dyess | ||
Bug Description
when the docker-registry relation is broken between docker-registry and containerd, this charm leaves a flag `charm.
This means that
`
juju remove-relation docker-registry containerd
juju add-relation docker-registry containerd
`
doesn't reconfigure the new relation, preventing the `configure_client` code from setting all the registry config again on the relation
Revision history for this message
| Adam Dyess (addyess) wrote | #1 |
| Changed in layer-docker-registry: | |
| milestone: | none → 1.24+ck1 |
| assignee: | nobody → Adam Dyess (addyess) |
| status: | New → Fix Committed |
| tags: | added: backport-needed |
| tags: | removed: backport-needed |
| Changed in layer-docker-registry: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed
https:/