Apigee X is taking long time to deploy an API Proxy/Shared-Flow

[shrenikkumar-s]

Apigee X is taking long time to deploy an API Proxy/Shared-Flow and failed to deploy intermittently on 22-Nov-2022. After few hours the failures have stopped but it's taking enormous amount of time to deploy (sometimes up-to-an hour via UI) and it's observed that it happens for even a dummy proxy (that has not many policies). When checked, we've also found out that this is happening for some of other enterprises.

We've an outstanding case raised to Google but at the moment they're not sure of what's happening/if it's affecting multiple customers. So wanted to know if this is being faced by anyone else at the moment.

As always, I'm hoping for some quick and clear thoughts 🙂

@kurtkanaskie 

@dchiesa1 

@tomwilding72 

@raweed 

[brendanvu]

Can you share what's the support case number ? Just the case number would do. We will look into the details.

[shrenikkumar-s]

Thanks and here it is: 42357859

Thanks, I'm sure people working on the ticket. The reason I raised here is I get more insights on thr issue 🙂

[shrenikkumar-s · Accepted solution]

The issue is resolved for now & captured in Apigee Release Notes & Known issues.

Thanks everyone.

RCA: API proxy and shared flow deployments taking up to 30 minutes.
API proxies and shared flows could take around 20 to 30 minutes to deploy in the runtime plane in certain circumstances due to a 'socket closed' error in synchronizer.

https://cloud.google.com/apigee/docs/release/release-notes#sub:~:text=Known%20issue%3A%20260324159
https://cloud.google.com/apigee/docs/release/known-issues#260324159