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

Errors with harvested ressources #8726

Closed
gannebamm opened this issue Feb 1, 2022 · 4 comments
Closed

Errors with harvested ressources #8726

gannebamm opened this issue Feb 1, 2022 · 4 comments
Assignees
Labels
master needs further investigation Issue or reason for specific behaviour needs further investigation

Comments

@gannebamm
Copy link
Contributor

Expected Behavior

If I define a GeoNode Unified Harvester to copy resources:
grafik

these resources will be accessible by my node.

Actual Behavior

Some resources are not able to get copied and throw keyword errors:
grafik

The other resources´ metadata are copied (ResourceBase objects) but the content itself is not present:
grafik

Layer resources are not loaded properly as well:
grafik

Even though they are part of GeoServer:
grafik

But there is an additional geonode_ in the layers name.

Steps to Reproduce the Problem

  1. Define harvester with copy configuration (master as harvester node, 3.2.x as instance which gets harvested)
  2. Harvest resources
  3. try to open the resources

Specifications

  • GeoNode version: master
  • Installation method (manual, GeoNode Docker, SPCGeoNode Docker): GeoNode Docker
  • Additional details:

There are many PRs and ISSUEs targeting the new harvester feature (https://github.com/GeoNode/geonode/pulls?q=is%3Apr+harvest ; https://github.com/GeoNode/geonode/issues?q=is%3Aissue+harvester). It was first discussed as part of the GNIP-89 (#7664). Some of the issues I encountered were addressed before (#7947 (review)) but should be fixed by now. I would encourage other users and admins to test this feature more thorough.

@gannebamm gannebamm added needs further investigation Issue or reason for specific behaviour needs further investigation master labels Feb 1, 2022
@giohappy
Copy link
Contributor

@ricardogsilva can you please take a look a this issue?

@ricardogsilva
Copy link
Member

@giohappy, I will take a look at it

@gannebamm
is this still relevant?
are you able to share a public GeoNode URL that I may use as a harvest test target where I can reproduce the problem?

@gannebamm
Copy link
Contributor Author

gannebamm commented Mar 29, 2022

Hi @ricardogsilva
Sorry, I was busy with getting our instance publicly available and will not have time to test this before next week. The URL https://atlas.thuenen.de will provide some datasets as 3.3.x GeoNode instance beginning at 01.04 (this Friday).

@gannebamm
Copy link
Contributor Author

stale

@gannebamm gannebamm closed this as not planned Won't fix, can't repro, duplicate, stale Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master needs further investigation Issue or reason for specific behaviour needs further investigation
Projects
None yet
Development

No branches or pull requests

3 participants