Closed zhuwenxing closed 1 year ago
chaos type: pod-kill image tag: master-20221208-d67e878f target pod: indexcoord failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-cron/detail/chaos-test-kafka-cron/346/pipeline log:
artifacts-indexcoord-pod-kill-346-server-logs.tar.gz artifacts-indexcoord-pod-kill-346-pytest-logs.tar.gz
a failed job after the chaos chaos type: pod-failure image tag: master-20221208-d67e878f target pod: kafka failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-cron/detail/chaos-test-kafka-cron/357/pipeline
/assign @jiaoew1991 /unassign
It is still reproduced in master-20221212-e977e014
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-cron/detail/chaos-test-cron/464/pipeline
log:
artifacts-indexcoord-pod-kill-464-server-logs.tar.gz
@yah01
/assign @zhuwenxing this should be fixed with #21107
Not reproduced in master-20221212-56e722f9
It reproduced in 2.2 branch. image tag: 2.2.0-20221216-1aa7a9a8
log: artifacts-datacoord-pod-kill-531-server-logs.tar.gz artifacts-datacoord-pod-kill-531-pytest-logs.tar.gz
@yah01
Please take a look
/assign @zhuwenxing
verified and passed in master-20221227-d0d0db8c
and 2.2.2-20221222-0fdc1a04
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
chaos type: pod-failure image tag: master-20221208-d67e878f target pod: datacoord failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-cron/detail/chaos-test-kafka-cron/355/pipeline
log:
artifacts-datacoord-pod-failure-355-server-logs.tar.gz
artifacts-datacoord-pod-failure-355-pytest-logs.tar.gz
Anything else?
No response