You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ytimocin opened this issue
Apr 12, 2024
· 2 comments
Labels
importantThis item is a high priority Issue we intend to address as soon as possibletriagedThis item has been triaged by project maintainers and is in the backlog
What is happening?
The pod webshoppingagg is not getting into READY state after the deployment of eShop application (both containers and azure).
I have seen bunch of examples of this error: Waiting for deployment "webshoppingagg" rollout to finish: 0 of 1 updated replicas are available.... I will be tagging this issue in the failed run issues.
What should be done?
We should try to reproduce this locally by deploying eShop on Containers and eShop on Azure. After that we can understand what is going on.
One other way to solve this is to get the logs of the failed runs and see what is happening.
sylvainsf
added
triaged
This item has been triaged by project maintainers and is in the backlog
important
This item is a high priority Issue we intend to address as soon as possible
labels
Apr 22, 2024
The Wait for all pods to be ready step is unnecessary because the previous step, Deploy app, should wait for all pods to be ready before returning a successful deployment message. This was discussed with @rynowak in one of sync sessions. That is why I am removing this step from both of our test workflows.
importantThis item is a high priority Issue we intend to address as soon as possibletriagedThis item has been triaged by project maintainers and is in the backlog
What is happening?
The pod
webshoppingagg
is not getting into READY state after the deployment of eShop application (both containers and azure).I have seen bunch of examples of this error:
Waiting for deployment "webshoppingagg" rollout to finish: 0 of 1 updated replicas are available...
. I will be tagging this issue in the failed run issues.What should be done?
We should try to reproduce this locally by deploying eShop on Containers and eShop on Azure. After that we can understand what is going on.
One other way to solve this is to get the logs of the failed runs and see what is happening.
AB#11768
The text was updated successfully, but these errors were encountered: