Re: [ovirt-users] assigned Host was not available
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 status UP its available.
How do I find out why ovirt thinks its not available for VMs even though
it marked it as up?
On 3/7/17 11:45 AM, 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.
How do I tell why ovirt thinks the host is not available?
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).
Attachments:
- vdsClient.out.gz (application/x-gzip — 4.3 KB)