# Rancher DigitalOcean node provisioning extremely unstable **URL:** \ **Category:** SUSE Rancher Prime\ **Created:** [June 9, 2023, 6:18am UTC](https://forums.suse.com/t/rancher-digitalocean-node-provisioning-extremely-unstable/40885 "2023-06-09T06:18:56Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![SebManGK](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@SebManGK](https://forums.suse.com/u/SebManGK)\ **Post date:** [June 9, 2023, 6:18am UTC](https://forums.suse.com/t/rancher-digitalocean-node-provisioning-extremely-unstable/40885/1 "2023-06-09T06:18:56Z")
Trying to provision nodes on Downstream-clusters with HA-Rancher v2.5.9 and v2.7.1 and its built-in node-driver for Digital Ocean, we observe a very unstable behavior with following errors: `Error creating machine: Error running "sudo apt-get update": ssh command error: command: sudo apt-get update err: exit status 100 output: Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease` `[ERROR] handler node-controller: Error creating machine: Error installing Docker: , requeuing` `[ERROR] handler node-controller: Error creating machine: Error running "sudo apt-get update": ssh command error: command: sudo apt-get update err: exit status 100 output: Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB], requeuing` Tested with **Upstream Rancher v2.5.9 on RKE v1.20.11 and Downstream RKE v1.20.11** and **Upstream Rancher v2.7.1 on RKE v1.24.4 and Downstream RKE v1.24.13** with different Ubuntu versions. With Rancher v2.5.9 nearly every 3rd provisioning-try fails, with Rancher v2.7.1 it became much worse again: ![2023-06-09_08-15](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/d/d59ad8771e9d26a162f3dc6deba1a7e63785e673.png) Does anyone have an idea wether this is a topic on Digital Ocean or Rancher side? Or are there other ways to debug the problem besides looking into the Rancher-debug-logs?