Google Cloud Service Health

Google Cloud Service Health
Incidents
Google Engineers identified an issue with Cloud Build Github Pull Request Triggers.

This page provides status information on the services that are part of Google Cloud. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/.

Available
Service information
Service disruption
Service outage

Incident affecting Cloud Developer Tools, Cloud Build

Google Engineers identified an issue with Cloud Build Github Pull Request Triggers.

Incident began at 2021-09-22 03:30 and ended at 2021-09-23 11:49 (all times are US/Pacific).

Date	Time	Description
24 Sep 2021	10:25 PDT	We apologize for the inconvenience this service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Support by opening a case using https://cloud.google.com/support (All Times US/Pacific) Incident Start: 22 September 2021 03:30 Incident End: 23 September 2021 11:49 Duration: 1 day, 8 hours, 19 minutes Affected Services and Features: Google Cloud Platform - Cloud Build service triggers failed Regions/Zones: Global Description: Google Cloud Build service, used to run builds on Google Cloud Platform (GCP), experienced integration issues with GitHub. In this case, the Pull Request Triggers – with comment control enabled – failed for some users with the ‘writer’ role. From preliminary analysis, the issue was caused by an unexpected response received from the GitHub collaborator API call used to validate user permissions. Customer Impact: GCP builds failed to initiate when GitHub Pull Requests were created by users granted ‘write’ permissions on a repository via team permissions. “Needs /gcbrun from a collaborator” error message was displayed after Triggers failed. Additional details: The issue was mitigated after our engineering team rolled out a mitigation to unblock comment controlled triggers that are invoked by users with the ‘writer’ role.
23 Sep 2021	14:47 PDT	The issue with Cloud Build has been resolved for all affected users as of Thursday, 2021-09-23 14:45 US/Pacific. We thank you for your patience while we worked on resolving the issue.
23 Sep 2021	09:38 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: Mitigation work is still underway by our engineering team. The mitigation is expected to complete by Thursday, 2021-09-23 14:45 US/Pacific.} We will provide more information by Thursday, 2021-09-23 15:00 US/Pacific. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
23 Sep 2021	09:09 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: Mitigation work is still currently underway by our engineering team. We will provide more information by Thursday, 2021-09-23 10:00 US/Pacific. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
23 Sep 2021	08:30 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: Mitigation work is currently underway by our engineering team. We will provide more information by Thursday, 2021-09-23 09:00 US/Pacific. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
23 Sep 2021	08:11 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: Mitigation work is currently underway by our engineering team. We will provide more information by Thursday, 2021-09-23 08:30 US/Pacific. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
22 Sep 2021	20:53 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: Mitigation work is currently underway by our engineering team. We will provide more information by Thursday, 2021-09-23 07:00 US/Pacific. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
22 Sep 2021	18:04 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: Mitigation work is currently underway by our engineering team. We will provide more information by Wednesday, 2021-09-22 21:00 US/Pacific. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
22 Sep 2021	15:46 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers. Description: We are continuing to make progress with partners on investigating this issue. Options for mitigation are being explored as well. We will provide an update by Wednesday, 2021-09-22 18:00 US/Pacific with latest details. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
22 Sep 2021	13:45 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers Description: We are continuing to work with our partner to investigate the issue, and exploring other options for mitigation. We will provide an update by Wednesday, 2021-09-22 16:00 US/Pacific with current details. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
22 Sep 2021	11:40 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers Description: We are continuing to work with our partner to investigate the issue. We will provide an update by Wednesday, 2021-09-22 14:00 US/Pacific with current details. Diagnosis: Users with write access to a repository via a team are no longer considered collaborators in the GitHub API. This affects customers with GitHub Pull Request comment control triggers as certain users will no longer be able to trigger builds. Workaround: To workaround this, the users should be given the writer role to a repository directly.
22 Sep 2021	10:14 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers Description: We have attempted a rollback of the current release in an effort to mitigate the issue, but have not seen improvements in the situation. We are continuing to work with our partner to investigate the issue. We will provide an update by Wednesday, 2021-09-22 12:00 US/Pacific with current details. Diagnosis: GitHub Pull Request Triggers with comment control enabled are not firing for customers with the "writer" role. Workaround: A workaround is to use the "collaborator" role.
22 Sep 2021	09:28 PDT	Summary: Google Engineers are investigating an issue with Cloud Build Github Pull Request Triggers Description: We are experiencing an issue with Cloud Build related to Github Pull Request Triggers. Our engineering team continues to investigate this issue to identify a mitigation. We are also reaching out to our partner to assist with the investigation. We will provide an update by Wednesday, 2021-09-22 10:30 US/Pacific with current details. Diagnosis: GitHub Pull Request Triggers with comment control enabled are not firing for customers with the "writer" role. Workaround: A workaround is to use the "collaborator" role.
22 Sep 2021	08:51 PDT	Summary: Google Engineers are investigating an Issue with Cloud Build Description: We are experiencing an issue with Cloud Build related to Github Pull Request Triggers. Our engineering team continues to investigate this issue to identify a mitigation. We will provide an update by Wednesday, 2021-09-22 09:35 US/Pacific with current details. Diagnosis: GitHub Pull Request Triggers with comment control enabled are not firing for customers with the "writer" role Workaround: A workaround is to use the "collaborator" role.
22 Sep 2021	08:06 PDT	Summary: Google Engineers are investigating an Issue with Cloud Build Description: We are experiencing an issue with Cloud Build related to Github Pull Request Triggers Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-09-22 09:15 US/Pacific with current details. Diagnosis: GitHub Pull Request Triggers with comment control enabled are not firing for customers with the "writer" role Workaround: A workaround is to use the "collaborator" role.
22 Sep 2021	07:43 PDT	Summary: Google Engineers are investigating an Issue with Cloud Build Description: We are experiencing an issue with Cloud Build related to Github Pull Request Triggers Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-09-22 09:15 US/Pacific with current details. Diagnosis: There is a regression for Github Pull Request Triggers with comment control enabled. Customers with the "writer" role may not be able to trigger builds Workaround: A workaround is to use the "collaborator" role.

All times are US/Pacific