Charm can fail due to missing private key on scale out
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Snap |
Fix Released
|
Critical
|
Unassigned | ||
Sunbeam Charms |
Fix Released
|
Critical
|
Unassigned |
Bug Description
In a recent deployment a single unit failed because it had received a certificates relation joined event but had no private key available to generate a csr.
Looking at the code the generation of the private key happens when an install event is received BUT if the peer relation is not ready the request is deferred. In the case of this unit the event was deferred, then the pod was killed (I assume by k8s), a new pod was created and the install hook did not fire so no key was generated.
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
2023-09-
Changed in charm-ovn-central-k8s: | |
assignee: | nobody → Liam Young (gnuoy) |
Changed in snap-openstack: | |
status: | Fix Committed → Fix Released |
Changed in sunbeam-charms: | |
status: | Fix Committed → Fix Released |
Changed in snap-openstack: | |
importance: | Undecided → Critical |
Changed in sunbeam-charms: | |
importance: | Undecided → Critical |
Fix commited in https:/ /review. opendev. org/c/openstack /charm- ops-sunbeam/ +/899713