We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On attempt to import an eks cluster into rancher:v2.8-head I see following error messages in eks-operator pod logs.
Versions: rancher:v2.8-74d6c7a4c1f564eb2389508e48466590f12fab5a-head rancher-eks-operator:103.6.0+up1.3.6-rc.1
rancher:v2.8-74d6c7a4c1f564eb2389508e48466590f12fab5a-head
rancher-eks-operator:103.6.0+up1.3.6-rc.1
Command used for provisioning EKS cluster (using latest eksctl 0.198.0):
eksctl create cluster --name=th-imported --region=eu-west-2 --nodes=1 --node-type=t3.xlarge --node-volume-size=20 --managed --kubeconfig=kubeconfig-th-eks-imported --version 1.28
It is probably harmless and the cluster has been imported successfully, I could scale and add nodepools but the errors seems to be a bit suspicious.
time="2024-12-11T13:36:03Z" level=info msg="Starting eks.cattle.io/v1, Kind=EKSClusterConfig controller" time="2024-12-11T13:36:03Z" level=info msg="Starting /v1, Kind=Secret controller" time="2024-12-11T13:36:03Z" level=error msg="Error removing metadata from failure message: message body not formatted as expected" 2024-12-11T13:36:03.955416239Z time="2024-12-11T13:36:03Z" level=error msg="Error recording ekscc [] failure message: resource name may not be empty" 2024-12-11T13:36:04.768479213Z time="2024-12-11T13:36:04Z" level=info msg="cluster [c-5kzvt] finished updating" 2024-12-11T13:36:04.771995869Z time="2024-12-11T13:36:04Z" level=error msg="Error removing metadata from failure message: message body not formatted as expected" 2024-12-11T13:36:04.772034729Z time="2024-12-11T13:36:04Z" level=error msg="Error recording ekscc [] failure message: resource name may not be empty" 2024-12-11T13:36:05.227893452Z time="2024-12-11T13:36:05Z" level=info msg="cluster [c-5kzvt] finished updating" 2024-12-11T13:36:05.755315041Z time="2024-12-11T13:36:05Z" level=info msg="cluster [c-5kzvt] finished updating" time="2024-12-11T13:38:36Z" level=info msg="waiting for cluster [c-5kzvt] to update nodegroups [th-my-group]" time="2024-12-11T13:38:37Z" level=info msg="waiting for cluster [c-5kzvt] to update nodegroups [th-my-group]" time="2024-12-11T13:39:07Z" level=info msg="waiting for cluster [c-5kzvt] to update nodegroups [th-my-group]" time="2024-12-11T13:39:38Z" level=info msg="waiting for cluster [c-5kzvt] to update nodegroups [th-my-group]" time="2024-12-11T13:40:08Z" level=info msg="waiting for cluster [c-5kzvt] to update nodegroups [th-my-group]" time="2024-12-11T13:40:39Z" level=info msg="cluster [c-5kzvt] finished updating"
The text was updated successfully, but these errors were encountered:
@thehejik - 2.8 is EOM. If the import is successful, I'd vote to close this issue as wontfix (except @yiannistri thinks otherwise 😉)
Sorry, something went wrong.
Also spotted on AKS rancher/aks-operator#665
No branches or pull requests
On attempt to import an eks cluster into rancher:v2.8-head I see following error messages in eks-operator pod logs.
Versions:
rancher:v2.8-74d6c7a4c1f564eb2389508e48466590f12fab5a-head
rancher-eks-operator:103.6.0+up1.3.6-rc.1
Command used for provisioning EKS cluster (using latest eksctl 0.198.0):
It is probably harmless and the cluster has been imported successfully, I could scale and add nodepools but the errors seems to be a bit suspicious.
The text was updated successfully, but these errors were encountered: