[FIX] Minio: Wrong data path in v.16.0 v1.17.0 fresh installation

[rjshrjndrn]

Describe the issue

On fresh installation of OR v1.16.0 and v1.17.0, minio persistent volume path is wrong, and because of that, restarting the node/pod won't persist the data.
(This issue won't affect upgrades)

These steps shows how to fix the issue, while retaining the data(if you not yet restarted)

Steps for vanilla installation

1. sudo su 
2. pod=$(kubectl get po -n db | grep minio | awk '{print $1}')
3. pv_path=$(ls /var/lib/rancher/k3s/storage | grep minio)
4. kubectl -n db cp $pod:/bitnami/minio/data $pv_path
5. chown -R 1001:1001 $pv_path
6. kubectl patch deployment minio -n db --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/volumeMounts/0/mountPath", "value":"/bitnami/minio/data"}]'
7. HELM_OPTIONS="--set forceMigration=true" openreplay  -u

[isclever]

Any solution if you have rebooted? Or how to at get it to cache the assets again in the "new" bucket?

[rjshrjndrn]

@isclever You can't retrieve the rebooted sessions.
regarding the new bucket: There was a issue in the above comments, its fixed. Please redo them once again.

[isclever]

I ran the updated commands but assets are still not loading.

I am getting a AccessDeniedAccess Denied.https then the path to the file. HTTP return code is 403.

These are for sessions created after I have run the command.

[rjshrjndrn]

@isclever #1911

There was one more related issue. Have fixed that.

HELM_OPTIONS="--set forceMigration=true" openreplay -u to fix the issue