This message was deleted.
# fleeta
adamant-kite-43734
10/12/2022, 3:00 PMThis message was deleted.
l
limited-potato-16824
10/12/2022, 3:02 PMI should also add that I have removed the k3s cluster from Rancher and re-added it two times but the issue is still there.
q
quick-sandwich-76600
10/14/2022, 6:46 AMHi @limited-potato-16824, may please you remove the k3s cluster from Rancher and then try to clean any Rancher resource that may remain on it using this process: https://github.com/rancher/rancher-cleanup .Once cleaned, try to register it again and let me know if it made any difference.
l
limited-potato-16824
10/14/2022, 8:52 AMThanks for replying @quick-sandwich-76600, I did run the rancher-cleanup job and re-joined the cluster to Rancher but I still have the same issue.
I have also tried:
• join the cluster with another name
• Deleted the table k3s.kine in mysql and started up the cluster on a single node.
I still have the same issue, so I think this is Rancher related and not something in the k3s cluster
limited-potato-16824
10/14/2022, 9:23 AMOne step closer to the truth, I can now see this error message in Rancher in the fleet-agent bundle deployment:
"ErrApplied(1) [Cluster fleet-default/k3s-rnd: cannot re-use a name that is still in use]"
limited-potato-16824
10/14/2022, 12:42 PMAlso deleted the /var/lib/rancher directory and re-joined the cluster but no luck
limited-potato-16824
10/14/2022, 12:48 PMHow is the fleet-agent deployment generated in Rancher?
q
quick-sandwich-76600
10/14/2022, 1:51 PMI don't know how the process works. In any case, the last error you mentioned can help. It may happen that it's somehow stuck and not being shown on the UI, but the object is there.
l
limited-potato-16824
10/14/2022, 1:54 PMYeah, I think so too and I have been digging for hours now but I can't find it. It's hiding 😄
q
quick-sandwich-76600
10/14/2022, 1:57 PMMay you please run this on your local cluster https://gist.github.com/juanbrny/6fd755c5019745678a73933ed1c1638c? . Make sure that FASTMODE=0 and ONLY_SYSTEM_NAMESPACES=1 (just the opposite of the default values that you can see in the script). As that can dump confidential data, please share it privately with me or do your own debugging looking for references to "k3s-rnd" in the results.
l
limited-potato-16824
10/14/2022, 2:04 PMI just did a sanity check and added the k3s cluster to out rancher dev environment and everything works fine there
limited-potato-16824
10/14/2022, 2:04 PMI'll take a look at that script. Thank you
q
quick-sandwich-76600
10/14/2022, 2:05 PMYes, that confirms that a not properly deleted object should exist somewhere ...
quick-sandwich-76600
10/14/2022, 2:05 PMA silly question, is this the K3s cluster where you changed INT to BIGINT some weeks ago or is a different one?
l
limited-potato-16824
10/14/2022, 2:06 PMNo, this is a separate k3s cluster
limited-potato-16824
10/14/2022, 2:06 PMstill holding my breath that the one we did the changes in will behave 😄
🤞 1
limited-potato-16824
10/20/2022, 7:21 AMI ended up installing a new Rancher for this site and the cluster connects successfully to that Rancher installation. I will continue to investigate why this fails in the older Rancher installation we have with a new cluster.
q
quick-sandwich-76600
10/20/2022, 9:46 AMThere's clearly some data there that need to be removed. You mentioned the other day that you removed most of the results but not the bundle. Can you go to Continuous Delivery / Bundles and delete the bundle with the cluster ID (or delete it with the cli)?
216 Views