***** LATERALIZABLE REFSET AUTOMATION IS NO LONGER WORKING - Maria is asking Darryn to run it manually for now, until the problem can be permanently resolved in
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
FRI-477
*****
2
Discussion of existing Known Issues from the previous Release
Traceability failures
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-8675
July 2022 release issues logged here
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-9209
confirmed by Michael as false positives.
Traceability failures for August 2022 release logged here
Instead of usual manual Content validation, we now just need confirmation that all Projects had automated validation run against them, and were clean before promotion.
New Issues identified by the community from the previous Monthly Release.
Decision on whether to fix the issues:
VERY QUICKLY in time for this upcoming release?
In good time for the next monthly release?
Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion . - DONE
MRCM: Checked with Yong - NO CHANGES FOR AUGUST 2022
AAT to validate all correct in the final AUGUST 2022 release...
4. Ref set description changes August 2022 release - MBR no changes identified via descriptions file.
4
Mapping schedule
Chris confirmed today that we would not be able to get the new automated process up and running for this release cycle - therefore need to confirm that everyone is ready to continue with the old manual process for one more cycle?
Ready for testing but no need to rush this cycle - will be ready for May release...
1. First rundeck job will pickup the right date from the Release schedule, and then run the data import
2. Second rundeck job will be run by Maria (once Mapping tasks are complete), to add 2x new task id's into the job and generate the mapsDonna confirmed she's happy with the schedule, and they're also already up to date with the final content.
Mapping process delivered ICD-0 + ICD10 files to AAT on time this cycle
Did mapping process work well this time?? Yes, process was good
HOWEVER, the counts don't match Donna's manual counts exactly, so we will investigate further:
ICD-0 = Manual mapping count = ???? new records, only ???? new records coming through in Delta files
ICD-10 = Manual mapping count = ???? new records, 485 new records coming through in Delta files
Delta file showed most differences were due to 47 updated records in the Delta, in addition to that there was only one missing concept:
1196866006
Confirmed with Rick that this was a concept that was added to the content (therefore came through to mapping in the drip feed), and was then removed from the content before the monthly release!
Therefore should be missing from the Delta files - just should also be removed from Donna's manual counts (based on the drip feed) - she will work with Rick to get visibility of the Mapping QA report to remove these concepts from her counts
(see email trail at 16:24 on 15/2/2022)
Maria confirmed manual process went well again this month
April 2022:
Donna ran new report that Rick created to double check no invalid mappings, all clean now
Mark/Donna to complete mapping on Monday
June 2022:
Rick to confirm whether or not the difference in the Deleted record count (in the new automated mapping stats report) is anything to be concernedabout ....
July 2022:
ICD-0 - very few changes expected
ICD-10 - expecting 1000+ changes due to large number of intentional inactivations this cycle
August 2022:
ICD-0 - very few changes expected
ICD-10 - expecting 320+ changes due to large number of intentional inactivations this cycle
Donna flagged up a potential issue where one concept (1231691008) is mapped to two same codes - so it will look like a duplicate to our validation - but we can safely whitelist it as an intentional change within the spec of ICD-10
Upload of mapping content to 2x branches planned for Friday 12th this cycle...
5
Brief run through of the known issues already identified by the content team during the QA batch process, to ensure that technical team are aware of them, and can either resolve them in time for the release, or confirm as known issues.
6
DevOps resource confirmed
Chris Terance will be the resource for the July August release...(though Joe will cover last few days of cycle whilst Chris is on leave)
7
Versioning and Change Freeze
Plan is to follow the new processes as now defined:
Timing of the Release validation on 21st in order to allow enough time after sign off to complete re-opening tasks for the AP before 5pm on 21st April as planned - meeting moved to 9:30am on 21st to give us as much time as possible...
Intermittent problems with the 12am Daily Build have been caught by backup 2am Daily Build run so far, BUT could in theory run into problems with the mapping drip feed that also runs at 2am. However, this should be mopped up by the Saturday Friday drip feed, so shouldn't be a problem - agreed auto-job setup for 3am on Monday Friday morning each cycle to catch any stragglers as well...
If we find issues during pre-versioning validation this has a knock on effect on the timing of DevOps' versioning
The main concern here is the visibility for the Content Team if we can't get them back up within the same day as planned
Therefore, if we get to 15:00 on the day of versioning and still cannot sign off the PreProd content, we need to let Maria know so that she can give the team plenty of notice that they won't be back in the tool until tomorrow at the earliest.
RICK found another new issue with the Run and Reload job in Rundeck when testing the maps yesterday. Rick has now added the "Published" flag into the query for picking up the previously published package which should resolve this issue...
Another minor issue though with this is moving the auto-job to 3am results in a clash with the drip feed - Rick has submitted a ticket (INFRA-9419) to discuss potential long term options for automation in order to circumvent this issue