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

CI: Cilium L4LB NAT-46x64 (ci-nat46x64): failed to create cluster #19350

Closed
YutaroHayakawa opened this issue Apr 7, 2022 · 2 comments
Closed

CI: Cilium L4LB NAT-46x64 (ci-nat46x64): failed to create cluster #19350

YutaroHayakawa opened this issue Apr 7, 2022 · 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.

Comments

@YutaroHayakawa
Copy link
Member

CI failure

Error output:

Creating cluster "kind" ...
 • Ensuring node image (kindest/node:v1.21.1) 🖼  ...
 ✓ Ensuring node image (kindest/node:v1.21.1) 🖼
 • Preparing nodes 📦 📦   ...
 ✓ Preparing nodes 📦 📦 
 • Writing configuration 📜  ...
 ✓ Writing configuration 📜
 • Starting control-plane 🕹️  ...
 ✗ Starting control-plane 🕹️
ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged kind-control-plane kubeadm init --skip-phases=preflight,addon/kube-proxy --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1

Full logs: logs_397248.zip
CI Build: https://github.com/cilium/cilium/runs/5847845630?check_suite_focus=true

Root cause may be the same as #17305
@YutaroHayakawa YutaroHayakawa 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 Apr 7, 2022
@YutaroHayakawa YutaroHayakawa mentioned this issue Apr 7, 2022
Merged
@github-actions
Copy link

github-actions bot commented Jun 7, 2022

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

@github-actions github-actions bot added the stale The stale bot thinks this issue is old. Add "pinned" label to prevent this from becoming stale. label Jun 7, 2022
@github-actions
Copy link

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

@giorio94 giorio94 mentioned this issue May 23, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@YutaroHayakawa