Unable to update/stop/start function app when startup is failing "Cannot modify this site because another operation is in progress"

[bentmar]

Which trigger/binding are you using?
Service bus

Which language are you using?
C#

Expected behavior
If my function app crashes on startup because of any reason really. I should be able to stop it to avoid creating huge amounts of logs in application insights. If the app crashes due to a missing env variable that is needed for the app to run i should be able to update that env variable.

Actual behavior
When the function pulls an image that might have issues starting, I cant stop/start/update. Instead i get this error
Cannot modify this site because another operation is in progress. Details: Id: 928cccc3-271f-42e3-8f61-b8cf3c6ab3e7, OperationName: StartContainerAppOperation, CreatedTime: 11/12/2024 6:22:49 PM, RequestId: af54152a-4a45-4799-8ca5-c20682a83e24, EntityType: 3
The app will start, die, start, repeat. The portal will show the app as in error, and the option to stop it. But clicking stop will result in error, same with updating app settings. It seems like the issue resolves itself after a while (i will eventually be able to stop/start/update), but that takes way too long.

To Reproduce
Steps to reproduce the behavior:

1. make an existing container app env hosted (consumption only) function pull an image that throws an error in program.cs
2. Stop the function app from the portal (works the first time)
3. Start the function app from the portal (might work, might fail with similar errors as above)
4. Update any env variable from the portal results in similar errors as above

Additional context
This feels very unreliable and potentially dangerous if one is not able to quickly fix something that ends up in production, and instead is faced with errors. One cant even rollback (point to a different image), since "Cannot modify this site because another operation is in progress". i dont know the exact time it takes for one to be able to stop/update/start the app once this error occurs. Ive been able to update/stop/start after 2hrs when ive seen this error, but i didnt try constantly for 2hrs. If the app starts with no errors, i will not have any issues starting/stopping/updating. It seems like azure can get stuck in "starting/stopping" even after the failing app has started (but crashes forever) = you cannot stop it or update it.

[raorugan]

Ack in this! Allow us to investigate and get back to you on this!

[aloiva]

Hi @bentmar, we have identified the issue causing this and the fix for this is pending rollout. While the fix is waiting for rollout, consider waiting 15 minutes before trying out any other operation since as you pointed out, it auto resolves after a bit of time.

[bentmar]

Nice to hear! Any guesstimates on when the fix will be rolled out? This year?

[aloiva]

Deployment to all azure regions will be finished by the end of February. But if there's a certain region you're interested in, let us know! It might be finished earlier, so we'll let you know when the fix reaches in that region.

[bentmar]

yes please let me know. Its mainly NEU and WEU. Thanks!

[raorugan]

Noted!

[egnirra]

Any update on when this might be released for swedencentral? @aloiva