-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
e2e remove or fix (BadRequest): previous terminated container #722
Comments
yes, it's true that the error message is misleading but the fix is not to delete the command as it is needed when the pod does crash |
fix in #726 |
@ldemailly could this be closed with your prior comment? |
well I put a workaround (printing "expect error if there is no crash") but we still have the slightly misleading messages and that other PR was closed but not merged -> 0.3 |
not seeing this message in prow e2e logs anymore - closing |
it should still be in mixer test logs but I think it's fine |
* Revert "Strip out "spiffe://" in the identity (istio#719)" This reverts commit 99a482f. * Revert "Revert "Remove -release in filename when doing release build of proxy (istio#704)" (istio#723)" This reverts commit 13669ce. * Revert "Not to send legacy quota for v2 config. (istio#722)" This reverts commit aaf25ca.
I see this error too when I run istio 0.8 e2e tests with istio
|
These msg are everywhere in the log, but the containers exist, and the kubectl get return correct values.
If not a real problem, do not log them, they pollute.
W0910 05:59:13.187] Error from server (BadRequest): previous terminated container "istio-ingress" in pod "istio-ingress-2398531633-mtghq" not found
The text was updated successfully, but these errors were encountered: