Caution External Mail: Do not click any links or open any attachments unless you trust the sender and know that the content is safe.

Hi Vojta,

Thanks for the help.

I tried to activate my server this morning and captured the logs from vdsm.log and engine.log. They are attached.

Something went awry with my gluster (I think) as it is showing that the bricks on the affected server (ovirt1) are not mounted:

The networking looks fine.

Cheers,
Gervais

> On Nov 23, 2021, at 3:37 AM, Vojtech Juranek <vjuranek@redhat.com> wrote:
>
> On Tuesday, 23 November 2021 03:36:07 CET Gervais de Montbrun wrote:
>> Hi Folks,
>>
>> I did a minor upgrade on the first host in my cluster and now it is
>> reporting "Non Operational"
>>
>> This is what yum showed as updatable. However, I did the update through the
>> ovirt-engine web interface.
>>
>> ovirt-node-ng-image-update.noarch                                          
>>                       4.4.9-1.el8                                        
>>            ovirt-4.4 Obsoleting Packages
>> ovirt-node-ng-image-update.noarch                                          
>>                       4.4.9-1.el8                                        
>>            ovirt-4.4 ovirt-node-ng-image-update.noarch                   
>>                                          4.4.8.3-1.el8                   
>>                               @System ovirt-node-ng-image-update.noarch  
>>                                                               4.4.9-1.el8
>>                                                    ovirt-4.4
>> ovirt-node-ng-image-update-placeholder.noarch                             
>>                    4.4.8.3-1.el8                                         
>>         @System
>>
>> How do I start to debug this issue?
>
> Check engine log in /var/log/ovirt-engine/engine.log on the machine where
> engine runs
>
>>
>>
>> Also, it looks like the vmstore brick is not mounting on that host. I only
>> see the engine mounted.
>
>
> Could you also attach relevant part of vdsm log (/var/log/vdsm/vdsm.log) from
> the machine where mount failed? You should see some mount related error there.
> This could be also a reason why hosts become non-operational.
>
> Thanks
> Vojta
>
>> Broken server:
>> root@ovirt1.dgi log]# mount | grep storage
>> ovirt1-storage.dgi:/engine on
>> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>> fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> 131072) Working server:
>> [root@ovirt2.dgi ~]# mount | grep storage
>> ovirt1-storage.dgi:/engine on
>> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
>> fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> 131072) ovirt1-storage.dgi:/vmstore on
>> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type
>> fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
>> 131072)
>>
>>
>> I tried putting the server into maintenance mode and running a reinstall on
>> it. No change. I'de really appreciate some help sorting this our.
>>
>> Cheers,
>> Gervais
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/S6C7R6LUTJXFMG7WIODA53VEU4O7ZNHJ/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AWSWTXS6CEAYSAC3DUDNUTUZKPA7237E/