Rakshith R bde286ef49 osd: re-open encrypted disk during osd-prepare-job if closed ...

This commit implements this corner case during osd-prepare job.
```
The encrypted block is not opened, this is an extreme corner case
The OSD deployment has been removed manually AND the node rebooted
So we need to re-open the block to re-hydrate the OSDInfo.

Handling this case would mean, writing the encryption key on a
temporary file, then call luksOpen to open the encrypted block and
then call ceph-volume to list against the opened encrypted block.
We don't implement this, yet and return an error.
```
When underlying PVC for osd are CSI provisioned, the encrypted device
is closed when PVC is unmounted due to osd pod being deleted.
Therefore, this may occur more frequently and needs to be handled.
This commit implements the fix for the same.

Signed-off-by: Rakshith R <rar@redhat.com>

2022-11-30 18:54:23 +05:30

..

test

osd: re-open encrypted disk during osd-prepare-job if closed

2022-11-30 18:54:23 +05:30

error_test.go

ceph: embed the buffer in the error

2021-02-03 17:28:47 +01:00

error.go

ceph: embed the buffer in the error

2021-02-03 17:28:47 +01:00

exec_pod.go

core: add context parameter to functions

2022-03-22 08:19:07 +05:30

exec_test.go

osd: re-open encrypted disk during osd-prepare-job if closed

2022-11-30 18:54:23 +05:30

exec.go

osd: re-open encrypted disk during osd-prepare-job if closed

2022-11-30 18:54:23 +05:30

log.go

Migrate logging package from built-in to github.com/coreos/capnslog, allow user specified logging level, tune logging levels for existing log statements

2016-11-16 14:19:42 -08:00

translate_exec.go

osd: re-open encrypted disk during osd-prepare-job if closed

2022-11-30 18:54:23 +05:30