Description
Instructions
Please fill out the necessary details and list the PRs related to the OOB deployment in the sections below.
PRs Related to OOB
- Please provide the list of PRs related to the need for this OOB Deploy below:
Active Daily Users Impacted
- How many active users are impacted at this time and day.
We currently do not have the exact number. We know that as of today, at least 4,000 Medallia complaints are logged. The ticket changed urgency today when the PMs found out the bug was a bigger issue than initially thought. For further info reach out to our PMs @kingbmike and @oddballpete.
Has fix been confirmed in Staging?
- Yes
- No
Description
- Please provide the details/reason for the OOB Deploy
This bug has the potential to affect the set of all LOA1 users who access the vets-website Dashboard (aka va.gov/my-va). We want to remove the potential for any of them to continue encountering and logging the error.
Engineers on call for issue: @AdamKing0126 @john-rodriguez-adhocteam @nicksayre
Verify The following
- The OOB Deploy Request is after the cutoff time for the regular deploy.1
- The OOB Deploy Request is critical and must be resolved before the next automated deploy.
- You are prepared to create an Incident Post Mortem2 within two business days.
Performed by Platform Support Team
- PagerDuty OOB Deploy Incident Opened
- OCTO-DE staff acknowledgment of Request, via
/pd trigger - Notification is posted in the appropriate Slack support and team Channels
- Infrastructure/Operations has acknowledge the Requests (This applies to revproxy and fwdproxy, but is not required for Frontend and Backend requests)
- Security Team has Reviewed the requests (This is not necessary for requests that are not related to security)
CC: @department-of-veterans-affairs/vsp-operations , @department-of-veterans-affairs/vsp-product-support
Activity