Juju backup doesn't contain .juju files
Bug #1427257 reported by
Gema Gomez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Medium
|
Unassigned | ||
juju-core (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
We have lost a machine from which we deployed a cloud today. This is the node that had the .juju credentials and all the charms. The juju environment is still there but we have no access to the bootstrap node or any other machine for that matter (we lost the certificates).
After this event happened we decided to make a juju backup of another cloud and check what is inside. We couldn't find the certificates or CA files in it that would have allowed us to recover the environment so we are copying all that manually at the moment.
The juju version used for the test is: 1.20.10-
tags: | added: cts |
tags: | added: backup-restore |
Changed in juju-core: | |
milestone: | none → 1.24-alpha1 |
Changed in juju-core: | |
milestone: | 1.24-alpha1 → none |
Changed in juju-core: | |
status: | In Progress → Triaged |
tags: |
added: sts removed: cts |
tags: | added: sts-needs-review |
tags: | removed: sts-needs-review |
Changed in juju-core: | |
status: | Triaged → Invalid |
tags: | removed: sts |
Changed in juju-core (Ubuntu): | |
status: | New → Invalid |
To post a comment you must log in.
AFAICT, you are talking about the files in the .juju directory of the juju client machine. The .juju directory may contain credentials that are unrelated to the environment being backed up, so it would be a security breach to include *all* files, but it would be possible to back up the .jenv file for the particular environment. But you'd presumably also need the relevant ssh private key.
It's possible, but I think it also makes sense to place the onus on the juju user to back up their own .juju directory and credentials.