dry-tiger-7977706/19/2022, 8:28 AM
broad-crayon-5258906/24/2022, 12:16 AM
sparse-art-4804306/28/2022, 7:28 PM
jolly-musician-6358606/29/2022, 7:35 PM
I did some basic hardware checks, such as disk storage (the machine has 512 nvme for OS and 4T for VM data), but still have no idea why it still give me this error. Anyone know what could go wrong here? Everything is default out of box for now. Really appreciate it!🙏
0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
freezing-farmer-715606/30/2022, 2:59 PM
colossal-vr-3048206/30/2022, 5:38 PM
colossal-vr-3048206/30/2022, 5:45 PM
quick-waitress-2163207/04/2022, 12:58 PM
, etc..) with different kind of hardware and via rancher spin up clusters in
? Can i do it with node taints? and how to configure the toleration in rancher?
bumpy-portugal-4075407/06/2022, 2:06 PM
binary on the havester nodes. So please, can you add
to the next harvester release? Yes, I know there is a workaround with
but this is simply unnecessary complicated. Is it possible to generate a support bundle from cli? How? And finally: Is there a way to upload the support bundle from command line also?
kubectl exec ... -- cat file >localfile
damp-vegetable-4864507/07/2022, 4:43 PM
lemon-bear-3573107/08/2022, 1:40 PM
sticky-summer-1345007/11/2022, 1:29 PM
stale-painting-8020307/11/2022, 6:45 PM
crooked-scooter-5817207/12/2022, 3:30 PM
polite-megabyte-6347607/15/2022, 2:36 PM
Jul 15 14:34:53 rancher-system-agent: W0715 14:34:53.242176 3390 reflector.go:437] firstname.lastname@example.org/tools/cache/reflector.go:168: watch of *v1.Secret ended with: an error on the server ("unable to decode an event from the watch stream: stream error: stream ID 167; INTERNAL_ERROR") has prevented the request from succeeding
rough-teacher-8837207/17/2022, 10:58 AM
I've been trying to trace the error but I'm having some difficulties finding the correct related objects in the two kubernetes clusters. What I suspect might be the issue is that rancher attempts to create a machinedeployment on the harvester cluster, which is in the api namespace
failed to create fleet-default/cluster1 <http://cluster.x-k8s.io/v1alpha4|cluster.x-k8s.io/v1alpha4>, Kind=Cluster for rke-cluster fleet-default/cluster1: Internal error occurred: failed calling webhook "<http://default.cluster.cluster.x-k8s.io|default.cluster.cluster.x-k8s.io>": failed to call webhook: the server could not find the requested resource, failed to create fleet-default/cluster1-bootstrap1 <http://cluster.x-k8s.io/v1alpha4|cluster.x-k8s.io/v1alpha4>, Kind=MachineDeployment for rke-cluster fleet-default/cluster1: Internal error occurred: failed calling webhook "<http://default.machinedeployment.cluster.x-k8s.io|default.machinedeployment.cluster.x-k8s.io>": failed to call webhook: the server could not find the requested resource
while rancher expects it to be in the api namespace
Before I go through the hoops of upgrading rancher I figured I'd check here if this is a known issue. If so, are there plans to support some amount of backwards compatibility from different rancher versions to harvester and vice versa?
faint-oxygen-9431007/20/2022, 6:40 PM
proud-addition-2185407/21/2022, 4:38 PM
freezing-farmer-715607/21/2022, 11:27 PM
bumpy-portugal-4075407/28/2022, 4:03 PM
bumpy-portugal-4075407/28/2022, 4:04 PM
boundless-student-3482907/28/2022, 8:23 PM
swift-market-1682907/30/2022, 8:14 PM
CRD”. Are there instructions as to exactly that this CR needs to look like?
stale-painting-8020307/29/2022, 10:02 PM
, the rancher shows Harvester cluster in Pending state and never connects. I have verified that I can ping the LB IP from the harvester server. The LB is forwarding requests to the rancher on ports 80, 443, 9345 (rancher_supervisor), 6443 (kube_api). These are all working correctly through the LB. Are there any other port listeners required for Harvester to communicate with rancher?
hundreds-evening-8407108/05/2022, 5:10 PM
faint-oxygen-9431008/08/2022, 5:03 PM
its seems like harvester is trying to use 10.53.0.10 for DNS lookup? Thats not the DNS server we have configured on the server. any idea why harvester is trying to use that IP for DNS lookup instead of the server/address configured in the /oem/99_custom.yaml file?
2022-08-08T16:18:03.274063754Z time="2022-08-08T16:18:03Z" level=error msg="error syncing 'cluster-registration-url': handler harvester-setting-controller: Get \"<https://kube.blah.dev/v3/import/zvk4bvccqsvrjh5fpck6vm9tzgrbfjvgtgrh4wtq7r9mmtnk7s9l4j_c-m-mzc7k67k.yaml>\": dial tcp: lookup <http://kube.blah.dev|kube.blah.dev> on 10.53.0.10:53: no such host, requeuing"
big-judge-3388008/10/2022, 4:05 PM
witty-jelly-9584508/10/2022, 6:00 PM
nutritious-father-3579508/10/2022, 6:33 PM
adventurous-engine-9302608/10/2022, 10:29 PM
adventurous-engine-9302608/10/2022, 10:29 PM
square-orange-6012308/10/2022, 10:57 PM
adventurous-engine-9302608/11/2022, 12:41 AM
square-orange-6012308/11/2022, 12:42 AM
witty-jelly-9584508/11/2022, 8:08 AM
adventurous-engine-9302608/22/2022, 10:33 PM