Cloud Functions V2 API - Unable to use 8192 [342557692]

Assigned

Bug

Status Update

No update yet.

Description

pe...@cityswift.com

created issue #1

May 24, 2024 12:48PM

Problem you have encountered:

Unable to use 8192M in PATCH to https://cloudfunctions.googleapis.com/v2/{function.name} (gen1 cloud function)
Below snippet body i used in my PATCH, that does not work(any of the other supported memory's do work though)

{
  'name': 'projects/myproj/locations/europe-west2/functions/my-function',
  'serviceConfig': {
    'availableMemory': '8192M',
  },
  'environment': 'GEN_1'
}

Error/response(added new lines for readability)

googleapiclient.errors.HttpError: <HttpError 400 when requesting https://cloudfunctions.googleapis.com/v2/projects/myproj/locations/europe-west2/functions/my-function?alt=json returned 
"Failed to update 1st Gen function projects/myproj/locations/europe-west2/functions/my-function memory_mb: Invalid memory allocation. 
Should be one of: [128, 256, 512, 1024, 2048, 4096, 8192]".

Refs:

What you expected to happen:

Deploy cloud function Gen1, using 8192M via V2 cloud functions API

Steps to reproduce:

PATCH to https://cloudfunctions.googleapis.com/v2/{function.name}, with availableMemory set to 8192M

Other information (workarounds you have tried, documentation consulted, etc):

I tried using 8192Mi, which was accepted but defaulted to 256M after deployment
Deploying via the GCP console, or gcloud CLI, work perfect. Maybe they are using the v1 cloudfunctions API

Comments

va...@google.com <va...@google.com> May 27, 2024 07:02AM

Assigned to ku...@google.com.

pe...@cityswift.com <pe...@cityswift.com> #2May 27, 2024 08:02AM

Hello,

Thank you for reaching out to us with your request.

We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.

We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the Issue Tracker providing a detailed description of your issue.

Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.

ku...@google.com <ku...@google.com> #3May 29, 2024 02:48PM

Reassigned to gc...@google.com.

Hello,

Thank you for reaching out to us with your request.

We have duly noted your feedback and will thoroughly validate it. Currently, this has been forwarded to the engineering team for further investigation. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.

Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.

pe...@cityswift.com <pe...@cityswift.com> #4May 29, 2024 07:37PM

Thanks,

I also posted on the community, in the event others hit this issue.

Repro steps also outlined here if needed:

https://www.googlecloudcommunity.com/gc/Serverless/Cloud-Functions-V2-API-Unable-to-use-8192-or-4096-on-gen1-PATCH/m-p/757058/highlight/true#M3886

pe...@cityswift.com <pe...@cityswift.com> #5Jun 7, 2024 10:58AM

Hi all,

Good news

I was able to PATCH 8192M and 4096M successfully, using v2 API on gen1 cloud function.

So maybe Google/GCP updated the V2 cloudfunctions API for gen1 cloud functions recently.

current_cloud_function["serviceConfig"]["availableMemory"] = "8192M"
current_cloud_function["serviceConfig"]["availableMemory"] = "4096M"

Issue 342557692