Cloud Functions Incident #18038
Investigating an issue with GCF deployment
Incident began at 2018-10-17 03:39 and ended at 2018-10-17 17:07 (all times are US/Pacific).
| Date | Time | Description | |
|---|---|---|---|
| Oct 17, 2018 | 17:07 | The issue with deployment should have been resolved for all affected users as of 17:07 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence. |
|
| Oct 17, 2018 | 16:30 | The issue with Functions deployment in US and Asia regions are now fixed. |
|
| Oct 17, 2018 | 15:26 | The issue is limited to deploys to the Node 8 beta runtime with projects that use yarn package manager. Experimental support for yarn builds was recently added to Functions, and appears to break deploys for developers using the yarn.lock file. A temporary workaround is to remove the yarn.lock file before deploying. |
|
| Oct 17, 2018 | 15:08 | We are still investigating the issue with Functions deployment. We will provide another status update by 16:00 US/Pacific with current details. |
|
| Oct 17, 2018 | 13:45 | We are investigating an issue with deploying functions. Current workaround is to delete yarn.lock. We will provide more information by 15:00 US/Pacific. |