Spun up a completely new Kubernetes cluster in a new-to-me DigitalOcean region. Added nodeodm and broker as deployments, db and webodm itself as stateful sets (due to their need for persistent storage), and the logs for webapp were being spammed with this warning. Here is the first occurrence of it:
INFO Added [[coreplugins.measure.plugin]] plugin to database
INFO Registered [coreplugins.posm-gcpi.plugin]
INFO Registered [coreplugins.diagnostic.plugin]
INFO Registered [coreplugins.fullscreen.plugin]
INFO Registered [coreplugins.lightning.plugin]
INFO Registered [coreplugins.contours.plugin]
INFO Registered [coreplugins.measure.plugin]
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
INFO Booting WebODM 1.9.14
WARNING Debug mode is ON (for development this is OK)
INFO Registered [coreplugins.posm-gcpi.plugin]
INFO Registered [coreplugins.diagnostic.plugin]
I went to the welcome page, created an account, added nodeodm:3000 as a processing node, and saw the usual page with First Project. Still getting spammed with the warnings:
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
INFO Added jmt to default group
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
WARNING Not Found: /api/projects/1/tasks/6ac3fa06-86cf-4103-aec7-9f890b0ef952/
I exec’ed into the webapp container to check out the volume:
[email protected]:/webodm# ls -al /webodm/app/media
total 44
drwxr-xr-x 7 root root 4096 Apr 29 03:30 .
drwxr-xr-x 1 root root 4096 Apr 27 14:46 ..
drwxr-xr-x 3 root root 4096 Apr 29 03:30 CACHE
drwx------ 2 root root 16384 Apr 29 03:29 lost+found
drwxr-xr-x 3 root root 4096 Apr 29 03:30 plugins
drwxr-xr-x 2 root root 4096 Apr 29 03:30 settings
drwxr-xr-x 2 root root 4096 Apr 29 03:30 tmp
No “projects” directory, though I’m not sure at what point it gets created.
Just for fun, tried to upload images and got the same error I got last time I tried this.
I tried to create a project task directory /webodm/app/media/project/1/task/6ac3fa06-86cf-4103-aec7-9f890b0ef952/ using the working version I have running in docker-compose as a template, didn’t help. Tried creating a second project in the UI and uploading images to it, that failed the same way.
I am now 100% convinced that the problem behind the warning is the root cause of my issues here with Kubernetes. Help?