On Nov 24, 2021, at 4:03 AM, Staniforth, Paul <P.Staniforth@leedsbeckett.ac.uk> wrote:

Hi Gervais,

              The engine doesn't need to be able to ping the IP address, just needs to know what it is so adding them to the /etc/hosts file should work.

Also, I would check ovirt1, is it mounting the brick, what does "systemctl status glusterd" show, what are the logs in /var/log/gluster ?

Regards,

Paul S.

---

From: Gervais de Montbrun <gervais@demontbrun.com>
Sent: 24 November 2021 01:16
To: Staniforth, Paul <P.Staniforth@leedsbeckett.ac.uk>
Cc: Vojtech Juranek <vjuranek@redhat.com>; users@ovirt.org <users@ovirt.org>
Subject: Re: [ovirt-users] How to debug "Non Operational" host

 

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 Paul,

I don't quite get what you mean by this:

assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses

The storage network is on 10GB network cards and plugged into a stand-alone switch. The hosted-engine is not on the same network at all and can not ping the IP's associated with those cards. Are you saying that it needs access to that network, or that is needs to be able to resolve the IP's. I can add them to the /etc/hosts file on the ovirt-engine or do I need to reconfigure my setup? It was working as it currently configured before applying the update.

I have no idea why the ovirt1 server is not showing up with the fqdn. I set up all the servers the same way. It's been like that since I set things up. I have looked for where this might be corrected, but can't find it. Ideas?

The yellow bricks... I can force start them (and I have in the past), but now it turns green for a few minutes and then returns to red.

Cheers,
Gervais

On Nov 23, 2021, at 12:57 PM, Staniforth, Paul <P.Staniforth@leedsbeckett.ac.uk> wrote:

Hello Gervais,

           is the brick mounted on ovirt1 ?  can you mount it using the settings in /etc/fstab ?

The hostname is not using a FQDN for ovirt1

assuming you have a storage network for the gluster nodes the engine needs to resolve be able to resolve the host addresses

ovirt1-storage.dgi
ovirt2-storage.dgi
ovirt3-storage.dgi

So that it can assign them to the correct network.

When the volume is showing yellow you can force restart them again from the GUI.

Regards,

Paul S.

---

From: Gervais de Montbrun <gervais@demontbrun.com>
Sent: 23 November 2021 13:42
To: Vojtech Juranek <vjuranek@redhat.com>
Cc: users@ovirt.org <users@ovirt.org>
Subject: [ovirt-users] Re: How to debug "Non Operational" host

 

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:

<PastedGraphic-2.png>

<PastedGraphic-3.png>

<PastedGraphic-4.png>

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/

To view the terms under which this email is distributed, please go to:- 
https://leedsbeckett.ac.uk/disclaimer/email

_______________________________________________
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/4YYEHIXZCSQCNRUU3WO5KS4ILTGBMUTD/

To view the terms under which this email is distributed, please go to:- 
https://leedsbeckett.ac.uk/disclaimer/email

_______________________________________________
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/H7SLDPRW6FJ5S4SBNICGFLHVKVD3F6OP/