Node displayed twice in kubernetes cluster

I’ve installed Rancher2/Kubernetes on a 6-node cluster and a separate rancher2 server on virtualbox. Each vm has 2GB of ram and the Rancher2 server has 3GB.
I restarted the vm several times, I deleted node 5 and 6, then I tried to reinstall node 5, but it didn’t work - it showed as registering but nothing came of it, although all the docker containers within the node seem to have been installed - so it’s past the rancher-agent stage.
node 1, 2, 3 have plane controlller and etcd, nodes 4-6 were workers (now there’s only node 4 as a worker).
Anyway, the problem is that Rancher displays node 2 twice, as you can see in the picture:

I’m using Rancher 2.1.6 on Ubuntu 16.04 Virtualbox machines (with vagrant, if that’s relevant) with docker 17.03.2 on all VMs.