mod-password-validator 2.1.0 upgrade fails in multi-tenant environment

Description

Overview:
In a multi-tenant environment, the mod-password-validator-2.1.0 upgrade from v2.0.2 fails with an error like this:

This is appears to be due to the fact that the upgrade script attempts to remove the f_unaccent function, which is used in index definitions for previous versions of mod-password-validator. If there are multiple tenants on a system, the upgrade fails, because not all tenants can be upgraded simultaneously.

There is no workaround that I can see other than to leave mod-password-validator at v2.0.2.

Update RMB-cleanup scripts with specifying the schema. This is possible with ${database.defaultSchemaName}

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Wayne Schneider April 25, 2022 at 1:01 PM

Excellent, that seems like it will serve. Thank you!

Javokhir Abdullaev April 25, 2022 at 12:44 PM

Hi  task is completed by specifying schema, tested locally no issues were observed.  

Wayne Schneider December 23, 2021 at 2:22 PM

Yes, I'm still seeing issues with this. It appears that the upgrade script will try to remove the f_unaccent function from the public schema, which can cause issues in environments with modules that still depend on that function being in the public schema rather than in the individual module's schema. This appears to be the case at least for the Iris version of mod-finance-storage, and perhaps others.

Shans Kaluhin November 30, 2021 at 10:20 AM

Hi , is this ticket still relevant?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 22, 2021 at 2:42 PM
Updated April 26, 2022 at 2:16 PM
Resolved April 26, 2022 at 2:16 PM
TestRail: Cases
TestRail: Runs