Ok, understood.
Once I set correct host_id on both hosts how to take changes in force? With
minimal downtime? Or i need reboot both hosts anyway?
Regards,
Artem
19 февр. 2018 г. 18:18 пользователь "Simone Tiraboschi"
<stirabos(a)redhat.com>
написал:
On Mon, Feb 19, 2018 at 4:12 PM, Artem Tambovskiy <
artem.tambovskiy(a)gmail.com> wrote:
>
> Thanks a lot, Simone!
>
> This is clearly shows a problem:
>
> [root@ov-eng ovirt-engine]# sudo -u postgres psql -d engine -c 'select
> vds_name, vds_spm_id from vds'
> vds_name | vds_spm_id
> -----------------+------------
> ovirt1.local | 2
> ovirt2.local | 1
> (2 rows)
>
> While hosted-engine.conf on ovirt1.local have host_id=1, and
> ovirt2.local host_id=2. So totally opposite values.
> So how to get this fixed in the simple way? Update the engine DB?
>
I'd suggest to manually fix /etc/ovirt-hosted-engine/hosted-engine.conf
on both the hosts
>
> Regards,
> Artem
>
> On Mon, Feb 19, 2018 at 5:37 PM, Simone Tiraboschi <stirabos(a)redhat.com>
> wrote:
>
>>
>>
>> On Mon, Feb 19, 2018 at 12:13 PM, Artem Tambovskiy <
>> artem.tambovskiy(a)gmail.com> wrote:
>>
>>> Hello,
>>>
>>> Last weekend my cluster suffered form a massive power outage due to
>>> human mistake.
>>> I'm using SHE setup with Gluster, I managed to bring the cluster up
>>> quickly, but once again I have a problem with duplicated host_id (
>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1543988) on second host
>>> and due to this second host is not capable to run HE.
>>>
>>> I manually updated file hosted_engine.conf with correct host_id and
>>> restarted agent & broker - no effect. Than I rebooted the host itself -
>>> still no changes. How to fix this issue?
>>>
>>
>> I'd suggest to run this command on the engine VM:
>> sudo -u postgres scl enable rh-postgresql95 -- psql -d engine -c
>> 'select vds_name, vds_spm_id from vds'
>> (just sudo -u postgres psql -d engine -c 'select vds_name, vds_spm_id
>> from vds' if still on 4.1) and check
/etc/ovirt-hosted-engine/hosted-engine.conf
>> on all the involved host.
>> Maybe you can also have a leftover configuration file on undeployed host.
>>
>> When you find a conflict you should manually bring down sanlock
>> In doubt a reboot of both the hosts will solve for sure.
>>
>>
>>
>>>
>>> Regards,
>>> Artem
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>