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

load_result not working in batch jobs when using OIDC user #126

Closed
soxofaan opened this issue Feb 24, 2022 · 0 comments
Closed

load_result not working in batch jobs when using OIDC user #126

soxofaan opened this issue Feb 24, 2022 · 0 comments
Assignees

Comments

@soxofaan
Copy link
Member

originally reported here https://discuss.eodc.eu/t/caching-openeo-results/197/22

using load_result fails with something like

 openeo_driver.errors.JobNotFoundException: The batch job ‘4cfc3e73-4847-483f-a580-34d765e86f30’ does not exist.

after some digging, I found that the job lookup inside a batch job does not work because the batch job uses the proxyuser as user id while the job registry uses (OIDC based) user id

soxofaan added a commit that referenced this issue Feb 25, 2022
openEO processing in batch jobs needs real user id
for `load_result` and UDPs to work properly.
Proxy user id is just necessary when submitting the job.
soxofaan added a commit that referenced this issue Mar 9, 2022
PR #128 follow up: no need to keep proxy user id in batch job itself

also be more simple/strict in `argv` handling batch_job.py
soxofaan added a commit that referenced this issue Mar 9, 2022
PR #128 follow up: no need to keep proxy user id in batch job itself

also be more simple/strict in `argv` handling batch_job.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant