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
pchaigno opened this issue
May 11, 2021
· 2 comments
Labels
area/CIContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
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.
The text was updated successfully, but these errors were encountered:
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
area/CIContinuous Integration testing issue or flakeci/flakeThis is a known failure that occurs in the tree. Please investigate me!staleThe stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale.
Happened in a PR with unrelated changes (touching only
test/
):https://github.com/cilium/cilium/runs/2555946845
cilium-sysdump-out.zip(2).zip
The text was updated successfully, but these errors were encountered: