...
- 2019-08-12 11:12 User reported on MS Teams on Monday that '..issue with the API between TIS and GMC as we have 9 under notice on TIS for 30.11.2019 but far more than this on GMC connect and for Dec 2019 1 on TIS but 11 on GMC connect'
- 2019-08-12 11:50 Jay volunteered to look into this and asked for support from the team. Pepe and Jay started an investigation. Not sure what was looked at this point and lots of other dicussions about whether this is a fire_fire issue and whether reval in itself is a priority.
- 2019-08-13 12:07 This is the time by which all the chit chats, Question Time and other political discussions had finished without a clear conclusion. About an hour in total since raised.
- 2019-08-13 16:45 BA (Ashley) investigation started in order to raise a ticket into our backlog
- 2019-08-13 17:00 Ashey Ashley found an error message on both the GMC SYNC and INTREPID REVAL ETLs - '...no hosts matched...' and raised this with the PO who concurred it's a fire_fire issue.
- 2019-08-13 17:14 Ashley posted a reply to the thread on slack dev channel alerting the opsteam that this is a potential infrastructure issue and not a bug in the application code itself that requires a dev to fix.
- 2019-08-13 17:23 John kindly stepped in and started looking into a fix. (John Simmons (Deactivated) please add details of the fix here/to the ticket)
- 2019-08-13 17:35 Fix applied and GMC SYNC re-run which completed successfully
- 2019-08-13 17:42 REVAL ETL re-run and completed successfully
- 2019-08-13 17:52 PO's alerted by John of the fix.
- Need to check in the morning of 14/08 with the users if this has resolved the reported issue.
...
Should have taken ETL's into consideration of docker images that needed moving to new repo- Impact of the ETLs not running should have been considered and look at resolving this as a fire_fire issue
- Improvement to the slack monitoring of the GMC SYNC ETL and INTREPID REVAL ETL needs to be looked at including more information about the Ansible failure into the slack notification. - John Simmons (Deactivated) , I this might need a ticket.
Jira Legacy server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TISNEW-3264
What went well
- One Once I understood the reval process, (documented here Revalidation - Application Architecture Review), it became apparent that the issue is likely to be with the GMC SYNC and/or REVAL ETLs
- Fast fix by John when pointed out about the error, and re-run of etl's meaning that the correct data was in prod before the start of the next working day.
What went wrong
...