I created vm network and was able to select it in the node t rancher-users #harvester

Title

lively-zoo-40381

03/21/2023, 10:48 AM

I created vm network and was able to select it in the node template. However I’m facing this issue: I’m creating a new cluster, (1 master 1 worker) and selecting the corresponding node templates Then I see the cluster provisioning, 2 new vms are created, and they are in running state. However they never complete and register to the cluster… the cluster hangs in “Provisioning” I then noticed that the Storage of the vms is in “degraded” state. Any Advise on that ?

flat-finland-50817

03/21/2023, 10:51 AM

I guess you only have one Harvester node ?

lively-zoo-40381

03/21/2023, 10:51 AM

yes

Is that an issue ?

Oh so replication can’t work

got it

flat-finland-50817

03/21/2023, 10:52 AM

It is not supposed to be an issue, but it sure cause a lot of problems... One of it is that the default Longhorn triple-replication can't work

But this is not the issue per se

As you've seen the VMs seems to work fine as they don't need the triple replication to work correctly in order to boot. However Longhorn or Harvester seems to put a huge strain on the disk (for trying to achieve replication or whatever), which make the cluster provisioning fail (as it is trying to write a lot at once on the already busy disk). I'm facing the same issue and I'm trying to solve it. Can you try to create a single VM and test the disk performance ?

lively-zoo-40381

03/21/2023, 10:57 AM

Will try, b.t.w I’m using SSD

b.t.w cloud provider should be None, correct ?

I don’t see any issue with disks

that is during provisioning

flat-finland-50817

03/21/2023, 11:03 AM

b.t.w cloud provider should be None, correct ?

Yes, if you're using the good cloud credential you should be good (if your VMs are creating on Harvester the issue should not be there)

lively-zoo-40381

03/21/2023, 11:03 AM

image.png

flat-finland-50817

03/21/2023, 11:04 AM

Can you try

dd if=/dev/zero of=/tmp/test bs=512 count=1000000

on your VM ?

lively-zoo-40381

03/21/2023, 11:04 AM

are default credentials to login from the console ?

I’m using bridge mode so I guess I can’t SSH directly to the hosts as they don’t have an IP

which could be the issue as well, maybe this is a network issue

flat-finland-50817

03/21/2023, 11:06 AM

The credentials depends of the image VM you've chosen

lively-zoo-40381

03/21/2023, 11:06 AM

image.png

flat-finland-50817

03/21/2023, 11:07 AM

With an ubuntu cloud you should inject some credentials with cloud-init, either an ssh key if you can access it from outside or a password if you can only access it via the Harvester console, user is ubuntu

lively-zoo-40381

03/21/2023, 11:08 AM

yea, with current config I have no way to login

will add password + SSH to cloud init later

I’m suspecting network issue, How can I know this is actually working?

I think this is network issue, can you share how you configured it on your side ?

for example if I’m manually creating vm, what settings should I use, considering I only have a single management network on harvester

Waiting for node to get IP This is probably the issue…

Please see logs from the vm attached, something is not working with network

virt-launcher-nj-prd-master1-zdj29_undefined.log

flat-finland-50817

03/21/2023, 12:30 PM

Why do you think there is a network problem ? Because the ip is not displayed in the VMs panel ?

If you've configured another network than the management one, you should make sure that this network is correctly configured (i.e. with dhcp or static mapping enabled somewhere). Sometimes the ip don't come up on the interface because harvester is using qemu-agent to get the ip and if it's not installed correctly in the VM it can fail. You can check up the dhcp logs to find the ip of your VM and try to ssh into it

lively-zoo-40381

03/22/2023, 9:46 AM

I set up DHCP and now it works Thanks

✅ 1

5 Views