Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Upgrade issue between Q1 and Q2: PubSub ModuleRegistrationException

Description

Upgraded release of mod-circulation from v18.0.9 to v19.0.2 for an existing Diku tenant with data.

The request sent to Okapi was this, with reference and sample data set to true:

curl -w '\n' -D - -X POST -H "Content-type: application/json" \ -d @upgrade.json \ $OKAPI_URL/_/proxy/tenants/$TENANT_ID/install?deploy=false\&preRelease=false\&tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue

Also tried, after rolling back the DB instances, with sample and reference data set to false, with the same error.

Okapi returned the following error during the tenant API call:

POST request for mod-circulation-19.0.2 /_/tenant failed with 500: org.folio.util.pubsub.exceptions.ModuleRegistrationException: Module's subscribers were not registered in PubSub. HTTP status: 400

mod-circulation logs:

21:38:21 INFO PubSubClientUtils Reading MessagingDescriptor.json 21:38:21 INFO PubSubClientUtils Registering events for publishers 21:38:21 INFO PubSubClientUtils Registering module's publishers 21:38:21 INFO PubSubClientUtils Module's publishers were successfully registered 21:38:21 INFO PubSubClientUtils Registering module's subscribers 21:38:21 ERROR PubSubClientUtils org.folio.util.pubsub.exceptions.ModuleRegistrationException: Module's subscribers were not registered in PubSub. HTTP status: 400 21:38:21 ERROR bRegistrationService Error during module registration in mod-pubsub java.util.concurrent.CompletionException: org.folio.util.pubsub.exceptions.ModuleRegistrationException: Module's subscribers were not registered in PubSub. HTTP status: 400 at java.util.concurrent.CompletableFuture.encodeRelay(CompletableFuture.java:326) ~[?:1.8.0_222] at java.util.concurrent.CompletableFuture.completeRelay(CompletableFuture.java:338) ~[?:1.8.0_222] at java.util.concurrent.CompletableFuture.uniRelay(CompletableFuture.java:911) ~[?:1.8.0_222] at java.util.concurrent.CompletableFuture$UniRelay.tryFire(CompletableFuture.java:899) ~[?:1.8.0_222] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) ~[?:1.8.0_222] at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) ~[?:1.8.0_222] at org.folio.util.pubsub.PubSubClientUtils.lambda$registerSubscribers$4(PubSubClientUtils.java:139) ~[mod-circulation.jar:?] at io.vertx.core.http.impl.HttpClientRequestImpl.handleResponse(HttpClientRequestImpl.java:390) ~[mod-circulation.jar:?] at io.vertx.core.http.impl.HttpClientRequestBase.checkHandleResponse(HttpClientRequestBase.java:158) ~[mod-circulation.jar:?] at io.vertx.core.http.impl.HttpClientRequestBase.handleResponse(HttpClientRequestBase.java:139) ~[mod-circulation.jar:?] at io.vertx.core.http.impl.Http1xClientConnection.handleResponseBegin(Http1xClientConnection.java:608) ~[mod-circulation.jar:?] at io.vertx.core.http.impl.Http1xClientConnection.handleHttpMessage(Http1xClientConnection.java:576) ~[mod-circulation.jar:?] at io.vertx.core.http.impl.Http1xClientConnection.handleMessage(Http1xClientConnection.java:566) ~[mod-circulation.jar:?] at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:369) ~[mod-circulation.jar:?] at io.vertx.core.impl.WorkerContext.lambda$wrapTask$0(WorkerContext.java:35) ~[mod-circulation.jar:?] at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[mod-circulation.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [mod-circulation.jar:?] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222] Caused by: org.folio.util.pubsub.exceptions.ModuleRegistrationException: Module's subscribers were not registered in PubSub. HTTP status: 400 at org.folio.util.pubsub.PubSubClientUtils.lambda$registerSubscribers$4(PubSubClientUtils.java:137) ~[mod-circulation.jar:?] ... 13 more

UPDATE: more info from about mod-feesfines not being able to register in mod-pubsub:

Jason Root:
It got further, but still fails:

POST request for mod-feesfines-15.8.1 /_/tenant failed with 500: org.folio.util.pubsub.exceptions.ModuleRegistrationException: EventDescriptor was not registered for eventType: FEE_FINE_BALANCE_CHANGED . Status code: 403

Jason Root:
From mod-feesfines:15.8.1:

Caused by: org.folio.util.pubsub.exceptions.ModuleRegistrationException: EventDescriptor was not registered for eventType: FEE_FINE_BALANCE_CHANGED . Status code: 403 ERROR PubSubClientUtils [2135993eqId] org.folio.util.pubsub.exceptions.ModuleRegistrationException: EventDescriptor was not registered for eventType: LOAN_RELATED_FEE_FINE_CLOSED . Status code: 403 PostgresClient [2135608eqId] trying to execute: UPDATE diku_mod_feesfines.rmb_internal_index SET remove = TRUE

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1
  • 15 Jul 2020, 08:07 PM

Checklist

hide

TestRail: Results

Activity

Show:

Hongwei JiJuly 31, 2020 at 7:15 PM

Discussed with , he will close pubsub tickets and mention the issue in q1->q2 upgrade doc.
Just a FYI that q1 mod-authtoken 2.4.0 this line does not quote the perm name. That could fail the perm expansion. We decided not to spend more time on this issue though.

Ann-Marie BreauxJuly 31, 2020 at 4:33 PM

How do we finalize and close https://folio-org.atlassian.net/browse/MODPUBSUB-112#icft=MODPUBSUB-112 and MODPUBSUB-106? Is any additional verification needed? If so, who does it and when? Is some sort of documentation needed, on GitHub or in the release notes? If so, who writes it and how soon? I'm not understanding how to finish this.

jrootJuly 31, 2020 at 4:24 PM
Edited

Well, it's still a problem... An operational concern that needs to be taken into account by either the Sys Admin via documentation on upgrading, or Okapi's tenant install API.

Ann-Marie BreauxJuly 31, 2020 at 4:22 PM

Does that mean we can close https://folio-org.atlassian.net/browse/MODPUBSUB-112#icft=MODPUBSUB-112 and MODPUBSUB-106?

Hongwei JiJuly 31, 2020 at 3:19 PM

, I discussed with our EBSCO team. The reason we did not see this issue is because we have new mod-authtoken running before enabling. So there is no need to verify this again. Thanks.

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Folijet

Parent

Fix versions

Release

Q2 2020 Hot Fix #1

Affected Institution

TAMU

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 8, 2020 at 10:12 PM
Updated August 5, 2020 at 5:30 PM
Resolved July 24, 2020 at 2:11 PM
TestRail: Cases
TestRail: Runs

Flag notifications