With the new Release 7.0.0.rc1 the driver has rke2 support. I created a cluster in a public lan without problems. Thats working fine.
When i try to create the cluster in a private lan with our own dhcp i've the problem that the docker machine driver dosn't use the correct ip (is my guess). In the logs i get the 'Got existing NIC!' Output from waiting for the ip change. When i update the IP in the dcd the driver continues it's workflow, but on the target node, where i can successfully login with my ssh key provided in the cloud config i don't see any other ssh connections try. It seems that the driver isn't using the updated ip.
Expected behavior
I can create successfully a rke2 cluster in a private lan with a dhcp lease provided by a customer dhcp.
Environment
Docker Machine Driver Ionos Cloud version:
7.0.0.rc1
Configuration Files
How to Reproduce
Steps to reproduce the behavior:
Creata a RKE2 Cluster in a private LAN and with waitforIPchange active
Update the IP in the DCD to the new IP provided by the private DHCP
The driver recognized the ip change but can't connect via ssh.
Error and Debug Output
Container: machine
Filter
Disconnected
Downloading driver from https://rancher.kogo4ic.de/assets/docker-machine-driver-ionoscloud
2023-08-01T12:23:59.962945783Z Doing /etc/rancher/ssl
docker-machine-driver-ionoscloud
docker-machine-driver-ionoscloud: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped
Running pre-create checks...
(rke-test4-pool1-1aeb9ff4-zmq6c) IONOS Cloud Driver Version: 7.0.0-rc.1
(rke-test4-pool1-1aeb9ff4-zmq6c) SDK-GO Version: 6.1.3
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing LAN!
(rke-test4-pool1-1aeb9ff4-zmq6c) Creating machine under LAN 2
(rke-test4-pool1-1aeb9ff4-zmq6c) Creating machine under vdc-dmz datacenter
Creating machine...
(rke-test4-pool1-1aeb9ff4-zmq6c) Creating SSH key...
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing LAN!
(rke-test4-pool1-1aeb9ff4-zmq6c) Image Alias: ubuntu:20.04
(rke-test4-pool1-1aeb9ff4-zmq6c) Server created!
(rke-test4-pool1-1aeb9ff4-zmq6c) NIC attached to datacenter!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
(rke-test4-pool1-1aeb9ff4-zmq6c) Got existing NIC!
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
2023-08-01T12:27:01.639926388Z Waiting for SSH to be available...
Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
2023-08-01T12:30:03.733748683Z The default lines below are for a sh/bash shell, you can specify the shell you're using, with the --shell flag.
2023-08-01T12:30:03.733822273Z
Description
With the new Release 7.0.0.rc1 the driver has rke2 support. I created a cluster in a public lan without problems. Thats working fine. When i try to create the cluster in a private lan with our own dhcp i've the problem that the docker machine driver dosn't use the correct ip (is my guess). In the logs i get the 'Got existing NIC!' Output from waiting for the ip change. When i update the IP in the dcd the driver continues it's workflow, but on the target node, where i can successfully login with my ssh key provided in the cloud config i don't see any other ssh connections try. It seems that the driver isn't using the updated ip.
Expected behavior
I can create successfully a rke2 cluster in a private lan with a dhcp lease provided by a customer dhcp.
Environment
Docker Machine Driver Ionos Cloud version:
Configuration Files
How to Reproduce
Steps to reproduce the behavior:
Error and Debug Output