[Add Forge Now] process https://git.ideasonboard.org

https://webapp.staging.swh.network/admin/add-forge/request/62/
Type: cgit

changed milestone to %Extend archive coverage [Roadmap - Collect]

added AddForgeNow label

Request completly messed up in staging environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5649.

Request completly messed up in production environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5649.

The lister image wasn't on the node so the pod creation took more time than the pipeline defined listing delay (300 seconds).

~ ᐅ kbs describe pod $(kbs get po -n swh | awk '/cgit/{print $1}') -n swh | tail -1
  Normal   Pulling           5m57s  kubelet            Pulling image "container-registry.softwareheritage.org/swh/infra/swh-apps/lister:20231121.1"

I relaunch the job.

Request successfully processed in staging environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5649.

The pipeline failed on the production environment:

$ scheduler_register_lister
Usage: swh scheduler add-forge-now [OPTIONS] COMMAND [ARGS]...
Try 'swh scheduler add-forge-now -h' for help.
Error: Scheduler class (local/remote) must be instantiated

I launch the production first ingestion manually.

closed