We found if we move the rebuilt host to a new cluster setup for 4.1
compatibility it could startup VMs just fine.
So we are guessing its just a 3.6 compat mode issue.
I'll try upgrading the rest of the nodes to 4.1 and change compat mode.
Hopefully all will just work then.
We'll see this weekend.
I'm not sure if its related or not but I noticed 3 other hosts are doing
similar things.
They all have in common that they are earlier hardware nodes from the
other 3 nodes in the cluster.
All are HP DL360's, but that later 3 have 256 GB ram, older ones have
128GB ram.
The other 3 nodes are sti
On Tue, Mar 7, 2017 at 9:50 PM Bill James wrote:
> I have a hardware node that I recently upgraded from 3.6.4 to 4.1.0.4-1.
> It is having issues that certain VMs I cannot deploy to it because ovirt
> says host is not available.
> However that host is status up and has 14 running VMs on it.
>
> H
We have tried re-kickstarting the server, and removing it from ovirt and
reinstalling it.
Ovirt still thinks its not available to run VMs.
I even tried calling it by a different name, still no luck.
Starting a VM using "run-once" will deploy to the host just fine.
WHY?
I thought when host is in
I have a hardware node that I recently upgraded from 3.6.4 to 4.1.0.4-1.
It is having issues that certain VMs I cannot deploy to it because ovirt
says host is not available.
However that host is status up and has 14 running VMs on it.
How do I tell why ovirt thinks the host is not available?
A
5 matches
Mail list logo