This message was deleted.
# harvester
This message was deleted.
I guess you only have one Harvester node ?
Is that an issue ?
Oh so replication can’t work
got it
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 ?
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
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)
Can you try
dd if=/dev/zero of=/tmp/test bs=512 count=1000000
on your VM ?
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
The credentials depends of the image VM you've chosen
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
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
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
I set up DHCP and now it works Thanks