-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed as duplicate of#49685
Closed as duplicate of#49685
Copy link
Labels
JIRATo be used in correspondence with the internal ticketing system.To be used in correspondence with the internal ticketing system.area/harvesterinternalkind/bugIssues that are defects reported by users or that we know have reached a real releaseIssues that are defects reported by users or that we know have reached a real releasepriority/1status/backport-candidatestatus/need-design-reviewteam/hostbustersThe team that is responsible for provisioning/managing downstream clusters + K8s version supportThe team that is responsible for provisioning/managing downstream clusters + K8s version support
Description
Rancher Server Setup
- Rancher version: v2.8.0
- Installation option (Docker install/Helm Chart): as a helm chart on a single-node k3s cluster
- Proxy/Cert Details:
Information about the Cluster
- Infrastructure Provider = Harvester
User Information
- What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
- Admin
Describe the bug
After one of my harvester nodes was unexpected rebooted, rancher is no longer able to provision machines in the upstream harvester HCI infrastructure.
Trying to scale up an existing managed RKE2 cluster from rancher gets the following error:
machine Downloading driver from https://192.168.20.10/assets/docker-machine-driver-harvester
machine Doing /etc/rancher/ssl
machine docker-machine-driver-harvester
machine docker-machine-driver-harvester: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
machine Trying to access option which does not exist
machine THIS ***WILL*** CAUSE UNEXPECTED BEHAVIOR
machine Type assertion did not go smoothly to string for key
machine Running pre-create checks...
machine Error with pre-create check: "the server has asked for the client to provide credentials (get settings.harvesterhci.io server-version)"
machine The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
And creating a brand new cluster has a different error:
machine Downloading driver from https://192.168.20.10/assets/docker-machine-driver-harvester
machine Doing /etc/rancher/ssl
machine docker-machine-driver-harvester
machine docker-machine-driver-harvester: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
machine error loading host testing-pool1-31b05da3-dlchl: Docker machine "testing-pool1-31b05da3-dlchl" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
Looks like the connection between Rancher and Harvester is broken?
SURE-8423
SURE-8516
ettoreciarcia
Metadata
Metadata
Assignees
Labels
JIRATo be used in correspondence with the internal ticketing system.To be used in correspondence with the internal ticketing system.area/harvesterinternalkind/bugIssues that are defects reported by users or that we know have reached a real releaseIssues that are defects reported by users or that we know have reached a real releasepriority/1status/backport-candidatestatus/need-design-reviewteam/hostbustersThe team that is responsible for provisioning/managing downstream clusters + K8s version supportThe team that is responsible for provisioning/managing downstream clusters + K8s version support