Skip to:

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

Perform testing of ECS tenant recreating on Rancher

Description

Purpose:

We need to perform testing of tenant re-creating for ECS mode on rancher after related Thunderjet stories will be completed(see Links section). 

Testing flow will simulate situation when originally tenant(that added to the consortium) was created without sample/reference data, also have some data like users and inventory to keep, and after we need to re-create tenant with sample/reference data enabled with preserving the existing data on the tenant

Testing flow:

  • Create Okapi tenant with sample/reference data

  • Create some data like couple of staff users, create some Inventory records on this tenant

  • Make DB backup of this single desired tenant

  • Delete tenant from ECS by calling mod-consortia DELETE tenant endpoint

  • Delete tenant from Okapi

  • Create a new Okapi tenant with the same tenantId with reference/sample data enabled

  • Restore tenant data from DB backup

  • Add newly created tenant to ECS consortium

  • Check that previously created users have affiliations, inventory records are also available, sample/reference data also appears

 

Environment

None

Potential Workaround

None

Attachments

9

Checklist

hide

TestRail: Results

Activity

Show:

Arsen Atoyan February 2, 2024 at 7:31 AM

Tested, results in comments

Serhii_Nosko February 2, 2024 at 6:45 AM

Looks good, you used this flow how to soft-delete and re-add the ECS tenant as expected, now you can use this instrument to temporary hide ECS member tenant for performing some maintenance work for the Okapi tenant if needed, this story can be closed, thanks  

 

Arsen Atoyan February 2, 2024 at 1:03 AM
Edited

The flow was tested on  https://folio-tmp-test-1-consortium.ci.folio.org

1. We have 3 institutional tenants below and let's focus on University tenant

Also, we can check it from the postman

2. We can soft delete this tenant

3. Let's check the result after deleting

Now from UI

4. Let's re-add a university tenant to consortia{*}*

5. University affiliation is appears now and we can successfully switch to this affiliation

Conclusion: User tenant affiliations that are stored in the central tenant look as before, because there wasn't any physical deleting from mod-consortia tables during the tenant soft-deleting process.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Kitfox

Release

Quesnelia (R1 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 12, 2023 at 7:49 AM
Updated February 2, 2024 at 7:31 AM
Resolved February 2, 2024 at 7:31 AM
TestRail: Cases
TestRail: Runs

Flag notifications