Problem enabling Weaver in PAVICS

[tlvu]

Describe the bug

Added ./components/weaver to EXTRA_CONF_DIRS in env.local, then ./pavics-compose.sh up -d. Got the error below. Not sure how to diagnose. Need pointers.

Is it failing registering the catalog provider in Weaver or Magpie?

executing './components/weaver/post-docker-compose-up'
++ set +o
+ old_state='set +o allexport
set -o braceexpand
set +o emacs
set +o errexit
set +o errtrace
set +o functrace
set -o hashall
set +o histexpand
set +o history
set +o ignoreeof
set -o interactive-comments
set +o keyword
set +o monitor
set +o noclobber
set +o noexec
set +o noglob
set +o nolog
set +o notify
set +o nounset
set +o onecmd
set +o physical
set +o pipefail
set -o posix
set +o privileged
set +o verbose
set +o vi
set -o xtrace'
+ set +x
Running: ./components/weaver/post-docker-compose-up
  Requested Weaver WPS providers: [
    catalog
    finch
    flyingpigeon
    hummingbird
    malleefowl
    raven
]
  Will retry requests at most for 120s
[Weaver] Wait for response from Magpie to login [https://lvupavicsmaster.ouranos.ca/magpie]........... OK!
Validate Magpie token... OK!
[Weaver] Wait for response from Weaver [https://lvupavicsmaster.ouranos.ca/twitcher/ows/proxy/weaver].... OK!
[Weaver] Using URL: [https://lvupavicsmaster.ouranos.ca/twitcher/ows/proxy/weaver]
[Weaver] Wait for response from remote WPS provider [catalog] on [https://lvupavicsmaster.ouranos.ca/twitcher/ows/proxy/catalog]........
[Weaver] Got valid response from remote WPS provider [catalog].
[Weaver] Unregistering any remote WPS provider matching [catalog].
[Weaver] Delete [catalog] response: 404
[Weaver] Registering remote WPS provider [catalog] on [https://lvupavicsmaster.ouranos.ca/twitcher/ows/proxy/catalog]...
[Weaver] ERROR: Failed registration of remote WPS provider [catalog] on [https://lvupavicsmaster.ouranos.ca/twitcher/ows/proxy/catalog].
Error:

+ exit 23

Relevant logs in docker logs weaver:

[2022-11-30 21:58:51,037] WARNING  [MainThread][weaver.tweens] Handled request exception:
  Cause: [DELETE https://lvupavicsmaster.ouranos.ca:4001/providers/catalog]
  Error: [(HTTPNotFound) <404> Provider catalog cannot be found.]

[fmigneault]

Yes, it seems to be having trouble getting a WPS response from catalog service to register it. Weaver needs to receive a 200 response from catalog in order to know its details and validate it before registering it.

[tlvu]

When trying to recover my broken Magpie in this issue https://github.com/Ouranosinc/Magpie/issues/549, I wipe /data/magpie_persist and let it re-create from scratch and now suddenly this Weaver error is gone.

Does Weaver have some expectations for some starting state of Magpie?

In this case, activating Weaver on an already in used Magpie in production might be problematic.

[fmigneault]

The only thing Weaver needs to register the provider is that the WPS endpoint of catalog is readable for the GetCapabilities request. Since the post-script uses the Magpie admin credentials, the actual permissions should not matter at all.

[tlvu]

Not able to reproduce anymore, closing.