Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OOB Deploy Request - 4 PRs #93833

Open
9 of 10 tasks
eselkin opened this issue Sep 27, 2024 · 0 comments
Open
9 of 10 tasks

OOB Deploy Request - 4 PRs #93833

eselkin opened this issue Sep 27, 2024 · 0 comments
Labels
frontend operations platform-sre For issues related to the platform SRE team

Comments

@eselkin
Copy link
Contributor

eselkin commented Sep 27, 2024

Instructions

Please fill out the necessary details and list the PRs related to the OOB deployment in the sections below.

PRs Related to OOB

Active Daily Users Impacted

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

    687,166 pageviews/day for Homepage bug
    121,261 pageviews/day for VAMC
    3,815 pageviews/day for Vet Centers
    40 pageviews/day for new modernized Regional office pages
    2,482 pageviews/day for Campaign landing pages

Has fix been confirmed in Staging?

  • Yes
  • No (was confirmed on Tugboat and RI)

Description

  • Please provide the details/reason for the OOB Deploy

    Recent DST changes to packages and fixes merged in today did not resolve all issues with display of homepage, VAMC, Vet Center, VBA, or CLP pages

Verify The following

  • The OOB Deploy Request is after the 2pm EST cutoff for 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

Footnotes

  1. (See Deployment Policy and Deployment Schedules

  2. https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/tree/master/Postmortems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend operations platform-sre For issues related to the platform SRE team
Projects
None yet
Development

No branches or pull requests

1 participant