well, upgrading to ovirt 4.1.0.4-1 did not fix the problem.
This cluster has 7 hardware nodes plus a management server, all ruining
4.1.0.4-1.
For some reason ovirt thinks 5 out of the 7 nodes are not available,
even though they have VMs running on them.
The 2 nodes that do deploy VM fine I just rebooted today. All nodes were
rebooted 2 days ago for the 4.1 upgrade.
My test was to take the same VM and specify host to deploy to, for each
of the 7 nodes.
hostId='e8c7567b-7ccb-4d82-8aea-beb1cbf05bf6' = ovirt2 (ok)
hostId='b6db5aa3-55f5-4424-9222-d69199ffd59d' = ovirt7 (ok)
the rest all fail:
hostId='4b3c7000-fe36-4b5a-97ab-b3cf28a238a0' = ovirt1
hostId='6ed53fd2-f552-4dd2-b42c-c0e8401b6aa8' = ovirt3
hostId='64a663bb-148b-4d3f-8e9c-3db27bc7eee7' = ovirt4
hostId='d15998e3-7801-4a66-9f4e-6978c747d6bb' = ovirt5
hostId='70213e88-5c85-4931-8781-64841e7a6a19' = ovirt6
2017-03-20 15:56:05,761-07 WARN
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(DefaultQu
artzScheduler1) [519095c3-83ed-4478-8dd4-f432db6db140] EVENT_ID:
USER_RUN_VM_ON_NON_DEFAULT_VDS(152), Correlation
ID: 11ec1687-30f1-4543-b5a3-4760a19071ae, Job ID:
4cca04b8-e7e5-45b3-853f-d69cb56d8e7c, Call Stack: null, Custom E
vent ID: -1, Message: Guest billj4 started on Host
ovirt7.test.j2noc.com. (Default Host parameter was ignored - as
signed Host was not available).
How do I determine why ovirt thinks the host is not available?
attached is engine log and picture of host tab, and snippets of engine
log where the error occurs.
libvirt-client-2.0.0-10.el7_3.5.x86_64
ovirt-engine-tools-4.1.0.4-1.el7.centos.noarch
vdsm-4.19.4-1.el7.centos.x86_64
On 03/14/2017 11:29 AM, Bill James wrote:
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....
Thanks.
On 03/14/2017 02:41 AM, Bill James wrote:
> 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 still running ovirt 3.6.4.
>
>
> On 3/12/17 11:57 PM, Bill James wrote:
>> only thing different on the VM config is that I says Deploy to host
>> ovirt4.test, which ovirt then ignores because "host is not available".
>>
>> I attached logs from ovirt engine and ovirt4.test.
>> VM I tried to start is called "billj4-2".
>> I also tried to migrate another VM that is suppose to run on ovirt4
>> called "billj4".
>> This time it successfully migrated and is running on ovrit4.test.
>>
>> Thank you for your help!
>>
>>
>> [root@ovirt4 test vdsm]# virsh -r list --all
>> Id Name State
>> ----------------------------------------------------
>> 2 billj4 running
>>
>>
>> On 3/12/17 6:16 AM, Yaniv Kaul wrote:
>>>
>>>
>>> On Tue, Mar 7, 2017 at 9:50 PM Bill James <bill.james(a)j2.com
>>> <mailto: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
>>> <
http://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
>>> <
http://ovirt7.test.j2noc.com>. (Default Host parameter
>>> was ignored - assigned Host was not available).
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org <mailto:Users@ovirt.org>
>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>
>>
>