-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable-AzContainerAppRevision disables wrong revision #26748
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @howang-ms, @Greedygre. |
this looks like this disable request does not contain the revision name, please help take a look @howang-ms @Greedygre |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @howang-ms, @Greedygre. |
Hi @elonmallin Which revision do you expect to deactivate? And which revision you feel should still active? At 2024-11-22 12:00:44.7718030 deactivate d20241122r610389 |
Hi @elonmallin |
Hi, I unfortunately don't remember the exact revision number but if I passed Is it possible to continue without an email? It looks like you found the requests already so subscription id might already be visible there in the url |
We will only disable the revision that executed with Disable-AzContainerAppRevision. |
Description
I have a a container app with
myrev1
which is running and working andmyrev2
which is failing and restarting the replicas all the time so traffic is still going tomyrev1
. I'd like to stopmyrev2
from restarting forever and maybe activating if it somehow becomes healthy to avoid a sneaky release at a random time later.I tried
Disable-AzContainerAppRevision -ContainerAppName myapp -ResourceGroupName myrg -RevisionName myrev2
but this deactivates bothmyrev1
andmyrev2
meaning my app withmyrev1
which was healthy and running is now also stopped and not justmyrev2
.This seems like a bug since it should just stop the revision that I pass in to the command I assume.
Issue script & Debug output
Environment data
Module versions
Error output
The text was updated successfully, but these errors were encountered: