Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Restore of geonode backup is not working #156

Open
AlexGacon opened this issue Mar 6, 2024 · 4 comments
Open

Bug: Restore of geonode backup is not working #156

AlexGacon opened this issue Mar 6, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@AlexGacon
Copy link
Collaborator

Bug Description

In order to migrate a GeoNode instance to GeoNode K8s, we tried to dump and restore the environment using the geonode commands.

The restore is not working, because the backup_restore folder is not available on the geoserver pod.

I am not sure if mounting the PVC on the pod is enough because of the ReadWrite access mode

Reproduction Steps

best to provide your values.yaml, a brief description of your cluster and version of geonode-k8s here.

Behavior

A description of what you expected to happen and what actually happened.

Additional Information

Any additional information or context that may be helpful in resolving the bug.

@AlexGacon AlexGacon added the bug Something isn't working label Mar 6, 2024
@AlexGacon
Copy link
Collaborator Author

@mwallschlaeger have you already used this feature in the case of GeoNode K8s?

@mwallschlaeger
Copy link
Contributor

@AlexGacon hey no i havent tried this approach. We're about to use https://github.com/zalando/postgres-operator/blob/master/docs/administrator.md#wal-archiving-and-physical-basebackups to backup and restore geonode databases together with a flat copy of the volume

@mwallschlaeger
Copy link
Contributor

This could be part of a list in the docs listing geonode features currently not functional in geonode-k8s

@mwallschlaeger
Copy link
Contributor

mwallschlaeger commented Apr 11, 2024

@AlexGacon is this maybe related to the latest fixes in geonode v4.2.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants