OOB Deploy Request

[allisonlu]

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:

  https://github.com/department-of-veterans-affairs/vets-website/pull/27329

Active Daily Users Impacted

• How many active users are impacted at this time and day.

  The errors occur when a veteran attempts to retrieve a list of appointments. They won’t be able to see their appointments. Graph of the requests/error 20 mi n per bar

  

Has fix been confirmed in Staging?

• [ ] Yes
• [ ] No

Description

• Please provide the details/reason for the OOB Deploy

  After today's deployment the VAOS appointment controller started to see a large spike in errors in parsing appointment start dates. I believe a changed pushed out to Vets Website changed the date formatting causing parsing errors in the VAOS appointment controller.

Verify The following

• [x] The OOB Deploy Request is after the 2pm EST cutoff for regular deploy.[^1]
• [x] The OOB Deploy Request is critical and must be resolved before the next automated deploy.
• [x] You are prepared to create an Incident Post Mortem^2 within two business days.

[^1]: (See Deployment Policy and Deployment Schedules

Performed by Platform Support Team

• [x] PagerDuty OOB Deploy Incident Opened
• [x] OCTO-DE staff acknowledgment of Request, via /pd trigger
• [ ] #72925
• [ ] Infrastructure/Operations has acknowledge the Requests

• [ ] Security Team has Reviewed the requests

  CC: @department-of-veterans-affairs/vsp-operations , @department-of-veterans-affairs/vsp-product-support

[va-vsp-bot]

This issue is stale. If it is no longer valid, please close issue. Otherwise please update