Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


#Module/areaIssue summaryDescriptionAssigneeStatus
1

Mod-orders-storage

Logging issue, no logs

Prepare fix ASAP because of any issues development team be blind

In Progress
Done
2

OKAPI

Version tagging

OKAPI added to install.json cause the installation problems -

https://

issues

folio-org.

folio

atlassian.

org

net/browse/FOLIO-2836 issue for OKAPI version

Done
3
Login with folio user

Login is not working for folio user at Honeysuckle env

Done
4

Mod-audit

Could not connect to DB, did not get correct configuration

  • Resolved at bugfest now
  • Taken in to account of SlavaH
  • Need to make sure that nothing wrong with deployment description
  • Need to talk with HW-> Oleksii P
  • Our issue with mod-audit seems to have been with what seems to be a recent change and the order of precedence resolving Postgres configuration.Our default task definition template defines one postgres environment variable. Postgres by default order resolves configuration values first by environment variable then by configuration file. The code snippet below totally bypasses the configuration file when any environment variable is defined. We adapted our templates and successfully deployed mod-audit in bugfest-honeysuckle.---------------------It really does ignore the config file if any DB related environment variables are set.
    Below, config is retrieved from the Envs class, which reads the DB environment variables:

        if (config.size() > 0) {
          log.info("DB config read from environment variables");
        } else {
          //no env variables passed in, read for module's config file
          config = LoadConfs.loadConfig(getConfigFilePath());
          // LoadConfs.loadConfig writes its own log message
        }

    https://github.com/folio-org/raml-module-builder/blob/35a5c4bdc5f6b2806e0d1ce135694fc2315ca230/domain-models-runtime/src/main/java/org/folio/rest/persist/PostgresClient.java#L528-L534 
Done
/Review
5

Mod-quick-mark

Not working
  • Source of deployment is branch of planform complete
  • Create jira ticket for John Malconian to update platform complete branch
  • Review platform complete Q3 2020 branch with JohnM and get understanding of wrong version #
  • Resolved/Released
Done
6

Mod-circulation

Memory leak

issues
folio
org
  • net/browse/CIRC-961
  • Attach crash dump to jira ticket -> Craig
  • Conduct meeting to align next steps after review of dump -> Taras, OleksiiP
  • Issue identified, leak is caused by pubsub issue, moved to Folijet responsibility -
  • https://
issues
folio
orgIn Progress
  • net/browse/MODPUBSUB-127
  • Pubsub issue potentially affect following modules:
    • mod-source-record-storage - Folijet - Awaiting release
    • mod-source-record-manager - Folijet - Released
    • data-import-processing-core - Folijet - Not affected
    • mod-inventory - Core Functional - Not affected
    • mod-feesfines -Vega - Not affected
    • mod-patron-blocks - Vega -Not affected
    • mod-audit - Firebird - In review
  • Pubsub has been released.
Kateryna Senchenko
  • Since it tries to create a new instance of Vertx it looks like PubSubPublishingService.publishEvent call is done outside of the main event loop and it tries to create a completely new instance of Vertx every time it calls publishEvent
  • @Oleksandr Kurash backport of PubsubPublishingService where changes are required
  • Write heap dump before container down at performance environment -> @Martin Tran
Done
7Platform completePlatform complete is not up to date
  • Source of deployment is branch of planform complete
  • Create jira ticket for John Malconian to update platform complete branch
  • Update documentation at release procedures → Anton Emelianov (Deactivated)
  • Share process updates with devs → Oleksii Petrenko
Done
8

Mod-feesfines

issue with permissions

Issues at UI-Users - uiu-1918. Added at sprint of Vega
Open
Done
9

RMB

new release - RMB 31.1.3

Discuss influence with Julian

Fixes 'current transaction is aborted', 'there is already a transaction in progress', and 'prepared statement "XYZ" already exists'

Open
Done
10
Permission set

Run script that redefine permission set

In progress
11RMB - Platform upgrade

Q2 to Q3 upgrade fails with "ERROR: tuple concurrently updated"

The following modules are affected:

mod-orders-storage-11.1.0
mod-inventory-storage-19.4.1
mod-login-7.1.0
mod-circulation-storage-12.1.0
mod-organizations-storage-3.2.0
mod-finance-storage-6.0.0
mod-calendar-1.10.0
mod-template-engine-1.10.0
mod-feesfines-15.9.1
mod-patron-blocks-1.1.0
mod-notes-2.10.0
mod-courses-1.1.0
mod-data-import-converter-storage-1.9.0
mod-source-record-manager-2.4.0
mod-data-import-1.11.0
mod-tags-0.7.0
mod-erm-usage-3.0.0
mod-erm-usage-harvester-2.0.0
mod-invoice-storage-4.1.0
mod-password-validator-1.8.0

"POST request for module_version /_/tenant failed with REVOKE ALL PRIVILEGES ON SCHEMA public FROM module_schema;"

Jira Legacy
serverSystem JIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-744

Jira Legacy
serverSystem JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-750

Jira Legacy
serverSystem JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyFOLREL-450

Jira Legacy
serverSystem JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-756

RMB-756 is blocked by modules that need to upgrade to RMB 31.1.5 (= FOLREL-450) and need to release a new version with this upgrade (blocked-by links in RMB-756).

(RMB-755 is needed only if the upgrade test RMB-756 fails:

Jira Legacy
serverSystem JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-755
)

Released|Upgrading modules