Invenio versioning

[jwhitelbl]

Is this helm chart expecting a maximum or minimum version of invenio?

Versioning: Helm master pulled on sept 25, 2024 container version derived from registry.cern.ch/inveniosoftware/almalinux:latest including default latest invenio from pip (invenio-3.4.1)

Describe the bug

Installer pod outright fails:

jwhite@proxmox0:~/invenio$ kubectl logs install-init-l5vtw -n invenio
Usage: invenio [OPTIONS] COMMAND [ARGS]...
Try 'invenio --help' for help.

Error: No such command 'db'.

Steps to Reproduce

1. git clone https://github.com/inveniosoftware/helm-invenio.git; cd helm-invenio/charts/invenio
2. customize overrides.yml for site including local docker repo with above-mentioned versioning for container
3. helm install -f overrides.yaml -n invenio invenio .
4. check kubectl logs for installer pod

Expected behavior

installer pod completes without error

[lindhe]

I'm not sure the init Job works. It's been there since before I did my pretty significant rewrites of the chart and I never used the init Job so maybe it's broken. I might look into it some day, unless someone fixes it before I do.

What I typically do exec into the pod and run the wipe_recreate.sh script. It's similar to what the init Job does.

WORKER_POD_NAME="$(kubectl get pods -l app=worker -o jsonpath='{.items[0].metadata.name}')"
kubectl exec -it "${WORKER_POD_NAME:?}" -- bash -c 'yes | /opt/invenio/src/wipe_recreate.sh'

[jwhitelbl]

Thanks for that. Do you folks have a recommended base dockerfile for the web/worker/etc? Or even "what packages should I be jamming on top of registry.cern.ch/inveniosoftware/almalinux:latest ? I keep running into paths missing, etc.

jwhite@proxmox0:~/invenio$ kubectl -n invenio exec -it "${WORKER_POD_NAME:?}" -- bash -c 'yes | /opt/invenio/src/wipe_recreate.sh'
bash: line 1: /opt/invenio/src/wipe_recreate.sh: No such file or directory
command terminated with exit code 127
jwhite@proxmox0:~/invenio$ 

[lindhe]

I have requested that they set a "known good image" by default, so it's easier to get started. I think it was delayed because v12 was not released. Now it is, so perhaps it's possible to revisit that topic.

When I've been testing things, I've used ghcr.io/inveniosoftware/demo-inveniordm/demo-inveniordm@sha256:2193abc2caec9bc599061d6a5874fd2d7d201f55d1673a545af0a0406690e8a4 I think that should work! Except maybe for this bug which (if it's still an issue) is resolved by removing the health probes for web.