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.

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

CI: ConformanceAKS: unable to retrieve cilium status: error dialing backend: dial tcp 10.240.0.35:10250: i/o timeout #16097

Closed
pchaigno opened this issue May 11, 2021 · 2 comments
Labels
area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Projects

Comments

@pchaigno
Copy link
Member

Happened in a PR with unrelated changes (touching only test/):
https://github.com/cilium/cilium/runs/2555946845
cilium-sysdump-out.zip(2).zip

Run cilium status --wait
Error: Unable to determine status:  timeout while waiting for status to become successful: context deadline exceeded
    /¯¯\
 /¯¯\__/¯¯\    Cilium:         2 errors
 \__/¯¯\__/    Operator:       1 errors
 /¯¯\__/¯¯\    Hubble:         1 warnings
 \__/¯¯\__/    ClusterMesh:    1 warnings
    \__/

DaemonSet         cilium                   Desired: 2, Ready: 2/2, Available: 2/2
Containers:       cilium                   Running: 2
Image versions    cilium                   quay.io/cilium/cilium-ci:08b0f90fc2de5ff22d648a7478ace9bb2788ad7e: 2
Errors:           cilium                   cilium-4j8vt             unable to retrieve cilium status: error dialing backend: dial tcp 10.240.0.35:10250: i/o timeout
                  cilium                   cilium-2zptk             unable to retrieve cilium status: error dialing backend: dial tcp 10.240.0.4:10250: i/o timeout
                  cilium-operator          cilium-operator          context deadline exceeded
Warnings:         clustermesh-apiserver    clustermesh-apiserver    clustermesh is not deployed
                  hubble-relay             hubble-relay             hubble relay is not deployed

Error: Process completed with exit code 1.
@pchaigno pchaigno added area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! labels May 11, 2021
@stale
Copy link

stale bot commented Jul 11, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Jul 11, 2021
@stale
Copy link

stale bot commented Jul 30, 2021

This issue has not seen any activity since it was marked stale. Closing.

@stale stale bot closed this as completed Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake ci/flake This is a known failure that occurs in the tree. Please investigate me! stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Projects
No open projects
CI Force
  
Awaiting triage
Development

No branches or pull requests

1 participant