Kitfox contact point - Vasili Kapylou
Jira ticket instructions Lotus (R1 2022) PO Bugfix and Hotfix Release Process:
Here are the PreMorningGlory BugFest
Tenant #2 https://mg-roots.int.aws.folio.org
Tenant #3 https://mg-stem.int.aws.folio.org
Morning Glory BugFest preparation EPIC - - BF-276Getting issue details... STATUS
Morning Glory Bugfest general info
Overall MG BF prep status
Outstanding tasks
Completed tasks
Closed Lotus BF environmental issues
Closed Lotus BF non-environmental issues
# | Date | Action | Status | Description/Comments | Jira | Responsible Team |
---|---|---|---|---|---|---|
1 | OKAPI token expiration - Check with CP → Oleksii Petrenko | |||||
2 | Prepare pre-morning-glory bugfest environment | DONE | https://mg-prep.int.aws.folio.org folio:folio | Kitfox | ||
3 |
| Pre-bugfest-clean-up | DONE | Existing Lotus issues Manual actions: 1) Circulation - tons of policies, locations, etc - Need to identify that is not used before deletion - Julie Bickle - 2) Inventory - Settings - Charlotte Whitt - Automated actions: | ||
4 |
| Create 3d tenant for Lotus BF environment with sample and reference data (As AQA environment) | DONE | Vasili Kapylou | ||
5 |
| Clean up data Import jobs and most of the data import custom mapping and job profiles | DONE |
UPDATE: All done except 3 field mapping profiles that cannot be deleted due to UI problem; added bug - BF-291Getting issue details... STATUS for Kitfox | ||
6 | Update the Inventory HRID prefix settings to reflect the Morning Glory release | DONE | To minimize chances of problems with Inventory HRID settings, as of Morning Glory Bugfest, we will be adding the flower prefix to the HRID settings for Bugfest, increasing the start number, and then asking testers to ensure that any users they create for testing DO NOT have the permission: Settings (Inventory): Create, edit and delete HRID handling. | None | Ann-Marie Breaux | |
7 |
| Review 300k records to make final decision at next sync-up | IN PROGRESS | 1) Create ticket in Jira→ Magda Zacharska - BF-292Getting issue details... STATUS 2) Discover 300k records → Ann-Marie Breaux Charlotte Whitt 3) Fix known issues → Ruslan + Kitfox 4) Need sync up with Magda related to random ones that we viewed in MG Bugfest Prep had source = FOLIO, not source = MARC | ||
8 | Remove stale permission sets from Settings > Users (Added by Erin Nettifee ) | This should be done before #17 below It would really help to clean up this list of test permissions, but it may be hard to identify what to cleanup If a permission set isn't assigned to any users, the permission set should be removed If a permission set is assigned to a user, but that user account is expired, the permission set should be removed If a permission set is assigned to a user, but the user account hasn't been modified in more than a year, the permission set should be removed | TBD Talk with Zak | |||
9 |
| Have historical data that could be affected by migration to simulate production upgrade | 1) Prepare required test data → POs & Dev Teams 2) Not to skip migration errors, not to delete records during migration → Kitfox, Oleksii Petrenko | |||
10 |
| Deadline for wipe actions | ||||
11 |
| Apply Apply Lotus HF#1 | DONE | |||
12 | Adjust data at new bugfest env → POs | POs | ||||
13 |
| Scripts are ready for new modules deployment: | DONE | All scripts for ui modules are ready, waiting for release versions. | Kitfox | |
| Create a data snapshot for Pre-Morning Glory | DONE | ||||
- | Prepare master branch for planform-complete with MG modules versions | DONE | ||||
14 | - | Migrate Lotus env to Morning Glory Bugfest | DONE |
-
BF-301Getting issue details...
STATUS
| Kitfox | |
15 |
| Deploy new modules | DONE |
-
BF-299Getting issue details...
STATUS
| Kitfox | |
16 | Add the default permission sets and users (the ones in the hosted ref envs) | DONE | Kitfox | |||
17 |
| Verify permissions for existing users | Discuss with CP | |||
18 |
| Deployment to MG bugfest env is competed. Data set is ready | DONE | These are the outstanding items that need to be verified/changed in bugfest-mgi env:
| Kitfox | |
19 |
| Verify that modules configuration is updated in FSE branch | DONE | Kitfox | ||
20 |
| Create a data snapshot for Morning Glory | DONE | Kitfox | ||
21 |
| Prepare and share links to MG BF logs | DONE | How to get logs from MG bugfest environment (Logs are updated every 15 minutes)Couple of ways to access logs:
| Kitfox | |
22 | Create set of Rally tickets for daily MG BF refresh | DONE | Need jira/rally | Kitfox | ||
23 |
| Prepare sFTP access to MG BF env | Need Jira for verification | Discuss with Dennis Bridges and team. | ||
24 | - | Smoke test - Manual & Automated | DONE | |||
25 | POs check the Bugfest env | POs | ||||
26 |
| Tests claimed | DONE | Bug Fest Morning Glory (R2 2022) | QA Manager | |
27 |
| DB Schema comparison - | DONE | ticket is created in rally | FSE | |
28 | High Availability verification | Discuss with Taras Spashchenko | DevTeams | |||
29 | Multi Tenant verification | Bug Fest Morning Glory MULTI-TENANT (R2 2022) | DevTeams | |||
30 |
| Migration from Lotus to MG time measuring → | Please create ticket at Jira/Rally Hanna Hulevich | ticket is created in rally | FSE | |
31 | Review release notes with DevOps (FSE + Community) and discuss deployment approach | RM |
1 Comment
Julie Bickle
A lessons learnt for Nolana: BF-310 - Getting issue details... STATUS
"Morning Glory Bufgest environment was deployed with outdated database snapshot, where all the requests were stored in old pre-TLR format. We ran TLR data migration manually, now everything should be fine."