IssueTracker

Hi

Thank you for reaching out to us.

To assist us in conducting thorough investigation, we kindly request your cooperation in providing the following information regarding the reported issue.

1. Has this scenario ever worked as expected in the past?
2. Do you see this issue constantly or intermittently ?
3. If this issue is seen intermittently, then how often do you observe this issue ? Is there any specific scenario or time at which this issue is observed ?
4. To help us understand the issue better, please provide detailed steps to reliably reproduce the problem.
5. It would be greatly helpful if you could attach screenshots of the output related to this issue.

Your cooperation in providing these details will enable us to dive deeper into the matter and work towards a prompt resolution. We appreciate your assistance and look forward to resolving this issue for you.

We would request you to please revert to us with the required information in common understandable language preferably English and the steps to reproduce it. Thank you for your understanding and cooperation.

Hi,

I am the developer mentioned by OP.

1. I can't tell if this ever worked as expected in the past, since it was my first experience deploying to Google App Engine. However, I believe it did work fine. There's no reason to think otherwise.
2. Yes, it happened constantly. All my attempts were unsuccessful, no matter if trying to deploy from my machine or from the App Engine's cloud shell. Even when deploying different source codes, with different app.yaml configs. While the region remained as southamerica-east-1, it would not work.
3. Create new project > create an app within the project, with southamerica-east-1 as the selected region > deploy a Java Spring Boot app to a B1 instance

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.

I'm encountering the same issue when trying to deploy Python 3.x applications to the southamerica-east1 region.

Files are uploaded to the proper Cloud Storage bucket, and the build succeeds in Cloud Build, but something goes wrong when gcloud calls google.appengine.v1(beta).Versions.CreateVersion:

{
    "done": true,
    "error": {
        "code": 4,
        "message": "Timed out fetching pod."
    },
    "metadata": {
        "@type": "type.googleapis.com/google.appengine.v1beta.OperationMetadataV1Beta",
        "endTime": "2024-07-03T07:32:43.692Z",
        "insertTime": "2024-07-03T07:28:02.391Z",
        "method": "google.appengine.v1beta.Versions.CreateVersion",
        "target": "apps/<redacted>/services/default/versions/20240703t042752",
        "user": "<redacted>@gmail.com"
    },
    "name": "apps/<redacted>/operations/625b936f-82ad-4651-94d4-a03ce8731679"
}

The issue appears to be related to the Transition from Container Registry.

Deployments on projects with REDIRECTION_FROM_GCR_IO_DISABLED (gcloud artifacts settings disable-upgrade-redirection) work fine. However, deployments on new projects with mandatory redirection from gcr.io, or on old projects that have enabled the redirection manually (gcloud artifacts settings enable-upgrade-redirection), will fail with a "Timed out fetching pod." error.