Skip to content
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.

Sign up for GitHub

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

Jump to bottom

e2e remove or fix (BadRequest): previous terminated container #722

Closed
andraxylia opened this issue Sep 10, 2017 · 7 comments
Closed

e2e remove or fix (BadRequest): previous terminated container #722

andraxylia opened this issue Sep 10, 2017 · 7 comments
Assignees
@mandarjog @andraxylia
Labels
area/test and release
Milestone
0.3

Comments

@andraxylia
Copy link
Contributor

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
@andraxylia andraxylia self-assigned this Sep 10, 2017
@andraxylia andraxylia added this to the Istio 0.2 milestone Sep 10, 2017
@andraxylia andraxylia mentioned this issue Sep 10, 2017
Merged
@ldemailly
Copy link
Member

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
(the fix would be to capture the output and only log it if the command is successful)

@ldemailly
Copy link
Member

fix in #726

@linsun
Copy link
Member

linsun commented Sep 28, 2017

@ldemailly could this be closed with your prior comment?

@ldemailly ldemailly modified the milestones: Istio 0.2, Istio 0.3 Sep 28, 2017
@ldemailly
Copy link
Member

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

@GregHanson
Copy link
Member

not seeing this message in prow e2e logs anymore - closing

@ldemailly
Copy link
Member

it should still be in mixer test logs but I think it's fine

kyessenov pushed a commit to kyessenov/istio that referenced this issue Aug 13, 2018
@qiwzhang
Not to send legacy quota for v2 config. (istio#722)
aaf25ca
kyessenov pushed a commit to kyessenov/istio that referenced this issue Aug 13, 2018
@qiwzhang
Revert "Not to send legacy quota for v2 config." (istio#725)
ef74122 
* 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.
@vhosakot
Copy link

I see this error too when I run istio 0.8 e2e tests with istio 0.8 and k8s 1.10.1. Is there a solution/workaround for this?

$ make e2e_simple E2E_ARGS="--auth_enable --use_local_cluster --istioctl /usr/local/bin/istioctl"

2018-07-23T19:45:58.053137Z	info	No previous log command failed: "Error from server (BadRequest): previous terminated container \"citadel\" in pod \"istio-citadel-64dccddd68-jsm2z\" not found\n" exit status 1
2018-07-23T19:46:00.855624Z	info	No previous log command failed: "Error from server (BadRequest): previous terminated container \"hyperkube\" in pod \"istio-mixer-post-install-7gvfz\" not found\n" exit status 1
2018-07-23T19:45:59.157769Z	info	No previous log command failed: "Error from server (BadRequest): previous terminated container \"egressgateway\" in pod \"istio-egressgateway-6cdc5596bc-9jks9\" not found\n" exit status 1
2018-08-21T16:03:37.035351Z	info	No previous log command failed: "Error from server (BadRequest): previous terminated container \"mixer\" in pod \"istio-policy-76d789bcfd-mg6s6\" not found\n" exit status 1

* command failed: "Error from server (BadRequest): container \"citadel\" in pod \"istio-citadel-67b787bdbd-728lq\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"hyperkube\" in pod \"istio-cleanup-old-ca-wxvgv\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"egressgateway\" in pod \"istio-egressgateway-6cdc5596bc-krxnz\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"ingress\" in pod \"istio-ingress-6bb787fb4f-gv9gf\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"ingressgateway\" in pod \"istio-ingressgateway-69cbd9f65c-slkmz\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"hyperkube\" in pod \"istio-mixer-post-install-gdztp\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"discovery\" in pod \"istio-pilot-7647f9665-lcgm5\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"mixer\" in pod \"istio-policy-6f96f698f6-9lrtm\" is waiting to start: ContainerCreating\n" exit status 1
* command failed: "Error from server (BadRequest): container \"sidecar-injector-webhook\" in pod \"istio-sidecar-injector-6f9d85fc55-9m9hd\" is waiting to start: ContainerCreating\n" exit status 1

howardjohn pushed a commit to howardjohn/istio that referenced this issue Jan 12, 2020
@elfinhe @istio-testing
mesh profile diff should not outputs usage info when diff is found. (i…
8aea87c 
…stio#722)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mandarjog mandarjog

@andraxylia andraxylia

Labels
area/test and release
Projects
None yet
Milestone
0.3
Development

No branches or pull requests
7 participants
@mandarjog @linsun @ldemailly @vhosakot @andraxylia @GregHanson @geeknoid