On Tue, Mar 7, 2017 at 9:50 PM Bill James <bill.james@j2.com> 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.

How do I tell why ovirt thinks the host is not available?

Anything different on the VM's configuration?
If some VMs do run on it, look like the issue is with the VM configuration. Can you provide full logs?
Y.
 

Attached is output from "vdsClient -s ovirt4.test.j2noc.com getVdsStats"


vdsm-4.19.4-1.el7.centos.x86_64
ovirt-engine-4.1.0.4-1.el7.centos.noarch


engine.log:
2017-03-07 11:06:49,269-08 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ForkJo
inPool-1-worker-0) [] EVENT_ID: USER_RUN_VM_ON_NON_DEFAULT_VDS(152),
Correlation ID: 81490f5b-3029-44d4-b223-df
6bb506efb3, Job ID: 76900dc9-ed9a-4fda-a17a-31825aa515c9, Call Stack:
null, Custom Event ID: -1, Message: Guest
  billj4 started on Host ovirt7.test.j2noc.com. (Default Host parameter
was ignored - assigned Host was not available).


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users