Manual backups and restores fail
Bug #1917680 reported by
Jay Kuri
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-k8s-discourse |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
It is currently not possible to do an on-demand backup in the k8s deployed environment. Automated backups appear to work properly.
Likewise attempts to restore from the UI using a backup file currently fail. They can be restored directly if you access the pod via kubectl exec.
This appears to be related to the environment needed for these processes to function properly. Paths and configuration details seem to be missing when these processes are kicked off.
Revision history for this message
| Jay Kuri (jk0ne) wrote | #1 |
| Changed in charm-k8s-discourse: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
To post a comment you must log in.
Suspect that if everything in the container environment is pushed into the environment of the unicorn process, it may work. Something to look into.