Closed marcustut closed 5 days ago
Please attach the must-gather archive. n/a
we can't invest time into investigating your issue if you don't invest time to provide the required information
The must-gather archive is a **mandatory** part of every bug report.
dial tcp: lookup B521A69C295412345512389.yl4.ap-south-1.eks.amazonaws.com on [::1]:53: read udp [::1]:45116->[::1]:53: read: connection refused"
Looks like firewall blocks DNS traffic from that node or your DNS service is down.
Please attach the must-gather archive. n/a
we can't invest time into investigating your issue if you don't invest time to provide the required information
The must-gather archive is a **mandatory** part of every bug report.
Sorry, I'll get back to this later with the must-gather archive.
As for @zimnx, I did manually SSH-ed into the node and ran the API Call through curl
, it worked fine. I also tried launching a debug pod with the same image docker.io/scylladb/scylla-operator:1.12
and ran the API call through curl and it worked fine too.
@tnozicka @zimnx I have updated the issue with the must-gather logs
This is the log file I got from the must-gather program
you need to upload the folder it created, not the log from its creation
"Gathering artifacts" DestDir="scylla-operator-must-gather-tc7c7mp7jnt6"
This is the log file I got from the must-gather program
you need to upload the folder it created, not the log from its creation
"Gathering artifacts" DestDir="scylla-operator-must-gather-tc7c7mp7jnt6"
Sorry, I updated the issue with the entire archive
Archive is empty
Archive is empty
Sorry, reuploaded it
I'm facing the exact same issue too. @zimnx May I know if you got a chance to look at it?
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
/lifecycle stale
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
/lifecycle rotten
The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
/close not-planned
@scylla-operator-bot[bot]: Closing this issue, marking it as "Not Planned".
What happened?
I followed the guide to setup EKS but since I already have an existing clusters with karpenter, I didn't create a new cluster with the
eks-cluster.yaml
provided. After I deploy the operator, local-csi-driver I then deploy a ScyllaCluster manifest but thecluster-node-setup
pod kept failing with this errorSo apparently somehow it was failing at not able to call
get node
through the kubernetes api but the error is not regarding authentication but some tcp / udp connection refused.What did you expect to happen?
The cluster-node-setup to succeed and XFS filesystem is created and scyllacluster continue to be created
How can we reproduce it (as minimally and precisely as possible)?
use Karpenter cluster with a nodepool using
i4i
instances and deploy the operatorScylla Operator version
v1.12
Kubernetes platform name and version
Please attach the must-gather archive.
scylla-operator-must-gather-tc7c7mp7jnt6.zip
Anything else we need to know?
No response