[ovirt-users] Is there any way to get the PDF files of the oVirt user docs such as Administrator Guide ?

2021-07-08 Thread tommy 
Thanks!

 

 

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/D32KK5QMWFAAKGT7R4YZJLZJCTI4Q6XU/

[ovirt-users] Re: change host IP

2021-07-08 Thread Strahil Nikolov via Users 
* gluster peer detach
 
 
  On Fri, Jul 9, 2021 at 6:38, Strahil Nikolov via Users 
wrote:   ___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IYRZ3BOAXB2VGCZ44NO7IDHQE3R535ZN/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/5CPY5WD5QLSPVXB5DJSQ7DFR4GAU6FM7/

[ovirt-users] Re: change host IP

2021-07-08 Thread Strahil Nikolov via Users 
I think the best is:Remove the host from oVirt, remove-brick the brick on the 
host, peet detatch, reinstall, add-brick in gluster, add in ovirt

Best Regards,Strahil Nikolov
 
 
  On Wed, Jul 7, 2021 at 17:20, 
radchenko.anato...@gmail.com wrote:   Hi guys,
what's the right way to change IP ( or FQDN ) on the host in replica 1 and 3 
configuration?
Thanks in advance.
Best regards.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/RAL25CO4D2KWQK5GLSETWESJS6W3LDLN/
  
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IYRZ3BOAXB2VGCZ44NO7IDHQE3R535ZN/

[ovirt-users] Re: Q: Node Upgrade Path

2021-07-08 Thread matthew.st...@fujitsu.com 
You need to go in steps.

https://www.ovirt.org/documentation/upgrade_guide/

-Original Message-
From: Andrei Verovski  
Sent: Thursday, July 8, 2021 2:52 PM
To: users@ovirt.org
Cc: Stier, Matthew 
Subject: Re: [ovirt-users] Q: Node Upgrade Path

Hi,

OK, thanks for the tip.
I always upgraded nodes via oVirt web interface, which is now 4.4.7, and I 
assume it can't update node 4.2 -> 4.3, because 4.3 is too old. Please correct 
if I'm wrong here.

May I use these commands to safely upgrade nodes manually?

yum check-update
yum clean all
yum update
yum remove ovirt-release42
yum install
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm

On 7/8/21 8:41 PM, matthew.st...@fujitsu.com wrote:
> If the hardware is old, and won't support EL8, the best option is to update 
> to oVirt 4.3.10 and update CentOS to 7u9.
>
> Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
> stopped supporting, and all the variant have followed suit.
>
> I have tried the Elrepo DUD's to work around the problem, but my results (in 
> the 4.4.1/4.4.2 timeframe) were not satisfactory.
>
> -Original Message-
> From: Andrei Verovski 
> Sent: Thursday, July 8, 2021 6:42 AM
> To: users@ovirt.org
> Subject: [ovirt-users] Q: Node Upgrade Path
>
> Hi,
>
>
> I have 2 oVirt nodes still running on CentOS 7.6.
> rpm -qa | grep ovirt - results in version 4.2.
>
> Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
> Node sw, or just leave for a couple of years till hardware will be trashed?
> I’m always keep oVirt Engine up to date, so my only concern if at any point 
> it will stop support old Node sw.
>
> Thanks in advance for any suggestion.
> Andrei
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/6SCBZF3N
> ASM5UIABKRANHI6UUHXCWG4Y/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/L4FIM6TJDOHC3FWHGMM7AKNLCIOHG4J3/

[ovirt-users] Re: export VM from oVirt engine 3.5

2021-07-08 Thread Alex K 
On Thu, Jul 8, 2021, 20:19  wrote:

> Hello,
> I am trying to export a bunch o VM from  oVirt version 3.5
> The problem is that there is no OVA support for exporting them. I also
> tryed to export VMs into OVA format using ovirtsdk4 which anyway won't work
> on oVirt 3.5.
> I can successfully export to a NFS partition but for each VM there are
> several qcow v2 files which I suppose to be the VM image and its snapshots.
> How to identify the correct file to represent the current VM status ?
>
When exporting you should get only one image file with the current status
of the vm.

If you want to hack with the vm images, you can commit all the chain of the
snapshot files to your own single qcow2 copy using qemu-img commands.

> You can easily get the disk ID of the current active snapshot (vm ->
snapshots) then you can view the full chain with:
qemu-img info --backing-chain $FILENAME
You need to know what you are doing though to avoid any data loss.

If I delete all the snapshots, will I end up with only one valid qcow v2
> image that I can use ?
>
Yes, you should. You can try if the snapshots are not needed.

> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/FCCK7HSIVMXAH2D7F2DWLHR4J2XSSTPP/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4J3HIIWUCVHJBMCL5TP7VR46J42MO2ED/

[ovirt-users] Re: Clear task after export to ova unfinisced

2021-07-08 Thread Anatoliy Radchenko 
more info.

Il giorno gio 8 lug 2021 alle ore 22:07 Anatoliy Radchenko <
radchenko.anato...@gmail.com> ha scritto:

> After read some links a have found the empty description of disk vm
> problem. But now i cannot add it bacouse disk is obviously locked.
>
> Il giorno gio 8 lug 2021 alle ore 21:05  ha
> scritto:
>
>> Hi all,
>> after  succesfully done ova export of 120gb VM i launched export ova of
>> 250gb vm but it is not finished. The time of task must be about 20 minuts.
>> Now i have one unfinished task and locked vm.
>> I know that it is complex task indluding a series of steps and clean db
>> of task manually is not resolved it.
>> Some info:
>>
>> Gluster replica 3 hiperconverged configuration
>>
>> [root@cluster23 ~]# vdsm-client Host getAllTasksInfo
>> {}
>>
>> tail -f engine.log
>> 2021-07-08 20:55:13,187+02 INFO
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45)
>> [0b76403b-c111-4eca-ab6f-d0f72705be4b] Command 'CreateOva' (id:
>> 'b9edc8f6-c3b2-4e9a-be01-5ef15b64eb68') waiting on child command id:
>> 'b10835e3-b5fd-4d08-b499-5fdb309ae18b' type:'AnsiblePackOva' to complete
>> 2021-07-08 20:55:15,215+02 INFO
>> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
>> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-21)
>> [0b76403b-c111-4eca-ab6f-d0f72705be4b] Command 'ExportVmToOva' (id:
>> '25dea23a-ac1e-4258-a71e-90e696c16c27') waiting on child command id:
>> 'b9edc8f6-c3b2-4e9a-be01-5ef15b64eb68' type:'CreateOva' to complete
>>
>> Any suggestions?
>>
>> Thanks in advance.
>> Best regards.
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/6PAIOXPFJ3APMWY33XSBN44OGMAEYCO2/
>>
>
>
> --
> _
>
> Radchenko Anatolii
> via Manoppello, 83 - 00132 Roma
> tel.   06 96044328
> cel.  329 6030076
>
> Nota di riservatezza : ai sensi e per gli effetti della Legge sulla Tutela
> della Riservatezza Personale (Legge 196/03) si precisa che il presente
> messaggio, corredato dei relativi allegati, contiene informazioni da
> considerarsi strettamente riservate, ed è destinato esclusivamente al
> destinatario sopra indicato, il quale è l'unico autorizzato ad usarlo,
> copiarlo e, sotto la propria responsabilità, diffonderlo. Chiunque
> ricevesse questo messaggio per errore o comunque lo leggesse senza esserne
> legittimato è avvertito che trattenerlo, copiarlo, divulgarlo, distribuirlo
> a persone diverse dal destinatario è severamente proibito,ed è pregato di
> rinviarlo al mittente.
>


-- 
_

Radchenko Anatolii
via Manoppello, 83 - 00132 Roma
tel.   06 96044328
cel.  329 6030076

Nota di riservatezza : ai sensi e per gli effetti della Legge sulla Tutela
della Riservatezza Personale (Legge 196/03) si precisa che il presente
messaggio, corredato dei relativi allegati, contiene informazioni da
considerarsi strettamente riservate, ed è destinato esclusivamente al
destinatario sopra indicato, il quale è l'unico autorizzato ad usarlo,
copiarlo e, sotto la propria responsabilità, diffonderlo. Chiunque
ricevesse questo messaggio per errore o comunque lo leggesse senza esserne
legittimato è avvertito che trattenerlo, copiarlo, divulgarlo, distribuirlo
a persone diverse dal destinatario è severamente proibito,ed è pregato di
rinviarlo al mittente.
2021-07-08 17:21:02 CEST - TASK [python-ver-detect : Run import yaml on py3] **
2021-07-08 17:21:02 CEST - changed: [cluster23.libracluster.net]
2021-07-08 17:21:02 CEST - {
  "status" : "OK",
  "msg" : "",
  "data" : {
"uuid" : "9067e4da-fca7-476a-88f5-4a56e8fd858e",
"counter" : 5,
"stdout" : "changed: [cluster23.libracluster.net]",
"start_line" : 4,
"end_line" : 5,
"runner_ident" : "1a8d3172-e000-11eb-b764-00163e69c933",
"event" : "runner_on_ok",
"pid" : 7168,
"created" : "2021-07-08T15:21:02.492469",
"parent_uuid" : "00163e69-c933-0d09-115d-0010",
"event_data" : {
  "playbook" : "ovirt-ova-export.yml",
  "playbook_uuid" : "3da287f3-73b3-4c4e-801d-50ff380e1935",
  "play" : "all",
  "play_uuid" : "00163e69-c933-0d09-115d-0008",
  "play_pattern" : "all",
  "task" : "Run import yaml on py3",
  "task_uuid" : "00163e69-c933-0d09-115d-0010",
  "task_action" : "command",
  "task_args" : "",
  "task_path" : "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/python-ver-detect/tasks/main.yml:2",
  "role" : "python-ver-detect",
  "host" : "cluster23.libracluster.net",
  "remote_addr" :

[ovirt-users] Re: Clear task after export to ova unfinisced

2021-07-08 Thread Anatoliy Radchenko 
After read some links a have found the empty description of disk vm
problem. But now i cannot add it bacouse disk is obviously locked.

Il giorno gio 8 lug 2021 alle ore 21:05  ha
scritto:

> Hi all,
> after  succesfully done ova export of 120gb VM i launched export ova of
> 250gb vm but it is not finished. The time of task must be about 20 minuts.
> Now i have one unfinished task and locked vm.
> I know that it is complex task indluding a series of steps and clean db of
> task manually is not resolved it.
> Some info:
>
> Gluster replica 3 hiperconverged configuration
>
> [root@cluster23 ~]# vdsm-client Host getAllTasksInfo
> {}
>
> tail -f engine.log
> 2021-07-08 20:55:13,187+02 INFO
> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45)
> [0b76403b-c111-4eca-ab6f-d0f72705be4b] Command 'CreateOva' (id:
> 'b9edc8f6-c3b2-4e9a-be01-5ef15b64eb68') waiting on child command id:
> 'b10835e3-b5fd-4d08-b499-5fdb309ae18b' type:'AnsiblePackOva' to complete
> 2021-07-08 20:55:15,215+02 INFO
> [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-21)
> [0b76403b-c111-4eca-ab6f-d0f72705be4b] Command 'ExportVmToOva' (id:
> '25dea23a-ac1e-4258-a71e-90e696c16c27') waiting on child command id:
> 'b9edc8f6-c3b2-4e9a-be01-5ef15b64eb68' type:'CreateOva' to complete
>
> Any suggestions?
>
> Thanks in advance.
> Best regards.
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/6PAIOXPFJ3APMWY33XSBN44OGMAEYCO2/
>


-- 
_

Radchenko Anatolii
via Manoppello, 83 - 00132 Roma
tel.   06 96044328
cel.  329 6030076

Nota di riservatezza : ai sensi e per gli effetti della Legge sulla Tutela
della Riservatezza Personale (Legge 196/03) si precisa che il presente
messaggio, corredato dei relativi allegati, contiene informazioni da
considerarsi strettamente riservate, ed è destinato esclusivamente al
destinatario sopra indicato, il quale è l'unico autorizzato ad usarlo,
copiarlo e, sotto la propria responsabilità, diffonderlo. Chiunque
ricevesse questo messaggio per errore o comunque lo leggesse senza esserne
legittimato è avvertito che trattenerlo, copiarlo, divulgarlo, distribuirlo
a persone diverse dal destinatario è severamente proibito,ed è pregato di
rinviarlo al mittente.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VKZGGABZIQX7GEBXJUL7XOTUY5KYOEJW/

[ovirt-users] Re: Q: Node Upgrade Path

2021-07-08 Thread Andrei Verovski 

Hi,

OK, thanks for the tip.
I always upgraded nodes via oVirt web interface, which is now 4.4.7, and 
I assume it can't update node 4.2 -> 4.3, because 4.3 is too old. Please 
correct if I'm wrong here.


May I use these commands to safely upgrade nodes manually?

yum check-update
yum clean all
yum update
yum remove ovirt-release42
yum install 
https://resources.ovirt.org/pub/ovirt-4.3/rpm/el7/noarch/ovirt-node-ng-image-update-4.3.0-1.el7.noarch.rpm


On 7/8/21 8:41 PM, matthew.st...@fujitsu.com wrote:

If the hardware is old, and won't support EL8, the best option is to update to 
oVirt 4.3.10 and update CentOS to 7u9.

Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
stopped supporting, and all the variant have followed suit.

I have tried the Elrepo DUD's to work around the problem, but my results (in 
the 4.4.1/4.4.2 timeframe) were not satisfactory.

-Original Message-
From: Andrei Verovski 
Sent: Thursday, July 8, 2021 6:42 AM
To: users@ovirt.org
Subject: [ovirt-users] Q: Node Upgrade Path

Hi,


I have 2 oVirt nodes still running on CentOS 7.6.
rpm -qa | grep ovirt - results in version 4.2.

Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
Node sw, or just leave for a couple of years till hardware will be trashed?
I’m always keep oVirt Engine up to date, so my only concern if at any point it 
will stop support old Node sw.

Thanks in advance for any suggestion.
Andrei
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6SCBZF3NASM5UIABKRANHI6UUHXCWG4Y/

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/VOS566YFYNL6VNL24I5V6L5PF7EEJRGY/

[ovirt-users] Clear task after export to ova unfinisced

2021-07-08 Thread radchenko . anatoliy 
Hi all,
after  succesfully done ova export of 120gb VM i launched export ova of 250gb 
vm but it is not finished. The time of task must be about 20 minuts. Now i have 
one unfinished task and locked vm.
I know that it is complex task indluding a series of steps and clean db of task 
manually is not resolved it.
Some info:

Gluster replica 3 hiperconverged configuration 

[root@cluster23 ~]# vdsm-client Host getAllTasksInfo
{}

tail -f engine.log
2021-07-08 20:55:13,187+02 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45) 
[0b76403b-c111-4eca-ab6f-d0f72705be4b] Command 'CreateOva' (id: 
'b9edc8f6-c3b2-4e9a-be01-5ef15b64eb68') waiting on child command id: 
'b10835e3-b5fd-4d08-b499-5fdb309ae18b' type:'AnsiblePackOva' to complete
2021-07-08 20:55:15,215+02 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-21) 
[0b76403b-c111-4eca-ab6f-d0f72705be4b] Command 'ExportVmToOva' (id: 
'25dea23a-ac1e-4258-a71e-90e696c16c27') waiting on child command id: 
'b9edc8f6-c3b2-4e9a-be01-5ef15b64eb68' type:'CreateOva' to complete

Any suggestions?

Thanks in advance.
Best regards.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6PAIOXPFJ3APMWY33XSBN44OGMAEYCO2/

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

2021-07-08 Thread Christoph Timm 

Hi Tomáš,

sorry for the late reply and for my the missing information.

Am 08.07.21 um 16:50 schrieb Tomáš Golembiovský:

On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:

Hi list,

I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have
issues to report the performance information via the guest agent.

The performance info is provided by libvirt and not by guest agent.
Could you be more specific about which information is missing?
Sorry I did not mean the performance information like Memory, CPU and 
Network. These are available. The missing information are IP Addresses 
and FQDN.


What is the version of vdsm and libvirt on the host?

All hosts are running:libvirt-7.0.0-14.1.el8



I see the following message on the VMs: The latest guest agent needs to be
installed and running on the guest


This is probably unrelated to the above. But still, what is the exact
version of the guest agent?

I have tried already different versions.
For example:
qemu-guest-agent.x86_64 15:4.2.0-48.module_el8.4.0+783+f8734d30 
@@commandline

qemu-guest-agent.x86_64 15:2.12.0-88.module_el8.1.0+248+298dec18 @AppStream




The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).

Any advice how to troubleshoot this?

I can see the stats will be presented in the GUI, if I migrate the VM to a
different host.

Same here, could you provide version of vdsm and libvirt on the host
where your VM is working fine?

KVM Version: 5.2.0 - 16.el8
LIBVIRT Version: libvirt-7.0.0-14.1.el8
VDSM Version: vdsm-4.40.70.6-1.el8

My 4 hosts are running the same versions on CentOS 8.
As I said I can migrate the VM to another host and the exclamation mark 
is gone and the information IPs and FQDNs are displayed.


 Tomas


Best regards
Christoph

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4F5X6BK5OYACFSPSLIHWYE2NXQROS5R3/


___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KT6FNKUQXQ5HGELZRZNGZX57MHOH4SFV/

[ovirt-users] Re: Q: Node Upgrade Path

2021-07-08 Thread matthew.st...@fujitsu.com 
Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
stopped supporting "under EL8", and all the variants have followed suit.

-Original Message-
From: matthew.st...@fujitsu.com  
Sent: Thursday, July 8, 2021 12:42 PM
To: Andrei Verovski ; users@ovirt.org
Subject: [ovirt-users] Re: Q: Node Upgrade Path

If the hardware is old, and won't support EL8, the best option is to update to 
oVirt 4.3.10 and update CentOS to 7u9.

Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
stopped supporting, and all the variant have followed suit.

I have tried the Elrepo DUD's to work around the problem, but my results (in 
the 4.4.1/4.4.2 timeframe) were not satisfactory.

-Original Message-
From: Andrei Verovski  
Sent: Thursday, July 8, 2021 6:42 AM
To: users@ovirt.org
Subject: [ovirt-users] Q: Node Upgrade Path

Hi, 


I have 2 oVirt nodes still running on CentOS 7.6.
rpm -qa | grep ovirt - results in version 4.2.

Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
Node sw, or just leave for a couple of years till hardware will be trashed?
I’m always keep oVirt Engine up to date, so my only concern if at any point it 
will stop support old Node sw.

Thanks in advance for any suggestion.
Andrei
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6SCBZF3NASM5UIABKRANHI6UUHXCWG4Y/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/MJQW32RA6OOCF2VGRRU4CQ6HLEWJMD27/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/CIC37BGT4A44GVCEX2XJ4JJPTICKBVYG/

[ovirt-users] Re: Q: Node Upgrade Path

2021-07-08 Thread matthew.st...@fujitsu.com 
If the hardware is old, and won't support EL8, the best option is to update to 
oVirt 4.3.10 and update CentOS to 7u9.

Some of my systems have megaraid sas2 raid controllers, which Red Hat have 
stopped supporting, and all the variant have followed suit.

I have tried the Elrepo DUD's to work around the problem, but my results (in 
the 4.4.1/4.4.2 timeframe) were not satisfactory.

-Original Message-
From: Andrei Verovski  
Sent: Thursday, July 8, 2021 6:42 AM
To: users@ovirt.org
Subject: [ovirt-users] Q: Node Upgrade Path

Hi, 


I have 2 oVirt nodes still running on CentOS 7.6.
rpm -qa | grep ovirt - results in version 4.2.

Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
Node sw, or just leave for a couple of years till hardware will be trashed?
I’m always keep oVirt Engine up to date, so my only concern if at any point it 
will stop support old Node sw.

Thanks in advance for any suggestion.
Andrei
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6SCBZF3NASM5UIABKRANHI6UUHXCWG4Y/
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/MJQW32RA6OOCF2VGRRU4CQ6HLEWJMD27/

[ovirt-users] export VM from oVirt engine 3.5

2021-07-08 Thread fddi 
Hello,
I am trying to export a bunch o VM from  oVirt version 3.5
The problem is that there is no OVA support for exporting them. I also tryed to 
export VMs into OVA format using ovirtsdk4 which anyway won't work on oVirt 3.5.
I can successfully export to a NFS partition but for each VM there are several 
qcow v2 files which I suppose to be the VM image and its snapshots.
How to identify the correct file to represent the current VM status ?
If I delete all the snapshots, will I end up with only one valid qcow v2 image 
that I can use ?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/FCCK7HSIVMXAH2D7F2DWLHR4J2XSSTPP/

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

2021-07-08 Thread Tomáš Golembiovský 
On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:
> Hi list,
> 
> I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have
> issues to report the performance information via the guest agent.

The performance info is provided by libvirt and not by guest agent.
Could you be more specific about which information is missing?

What is the version of vdsm and libvirt on the host?

> 
> I see the following message on the VMs: The latest guest agent needs to be
> installed and running on the guest
> 

This is probably unrelated to the above. But still, what is the exact
version of the guest agent?

> The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).
> 
> Any advice how to troubleshoot this?
> 
> I can see the stats will be presented in the GUI, if I migrate the VM to a
> different host.

Same here, could you provide version of vdsm and libvirt on the host
where your VM is working fine?

Tomas

> 
> Best regards
> Christoph
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/4F5X6BK5OYACFSPSLIHWYE2NXQROS5R3/

-- 
Tomáš Golembiovský 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/KSL3TZMWGTGLN7FDBA6IUSDEER2ZGENI/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-08 Thread Milan Zamazal 
Sandro Bonazzola  writes:

> Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
> sbona...@redhat.com> ha scritto:
>
>> +Milan Zamazal  , +Arik Hadas  , 
>> +Michal
>> Skrivanek  any hint?
>>
>
> I found https://metacpan.org/pod/Ovirt::Display but I think there should be
> an easier way within the engine to configure this.
>
>
>
>>
>> Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 
>> ha scritto:
>>
>>> Good day to all,
>>>
>>> I have a question about the console configuration of the VMs:
>>>
>>> By default, for each console connection to a VM, a password is set for
>>> 120 seconds, after that you can't use it again. We currently have the
>>> following concern:
>>>
>>> We want to access and control the VMs via the VNC/Spice of the Ovirt
>>> host. We have already tried to use the password from the console.vv for
>>> the connection and that works so far. Unfortunately we have to do this
>>> every 2 minutes when we want to connect again. We are currently building
>>> an automatic test pipeline and for this we need to access the VMs
>>> remotely before OS start and we want to be independent of a VNC server
>>> on the guest. This is only possible if we could connect to the VNC/Spice
>>> server from the Ovirt host.
>>>
>>> My question: would it be possible to fix the password or read it out via
>>> api every time you want to connect?

A one time password is set every time the console is opened, for those
120 seconds.  Unfortunately, the 120 seconds limit seems to be hardwired
in Engine sources.  So apparently the only chance would be to set the
password directly on the host using VM.updateDevice VDSM API call.  It
looks like this normally:

  VM.updateDevice(params={'deviceType': 'graphics', 'password': '', 
'disconnectAction': 'NONE', 'params': {'vncUsername': 
'vnc-630b9cae-a983-4ab0-a9ac-6b8728f8014d', 'fips': 'false', 'userName': 
'admin', 'userId': 'fd2c5e14-a8c3-11eb-951c-2a9574de53b6'}, 'ttl': 120, 
'graphicsType': 'spice'})

This way it's possible to set a password and its lifetime (`ttl'
parameter).  Of course, it's needed to find out the host the VM runs on,
a way to call the API (running vdsm-client directly on the host may be
the easiest way), how to make/use the *.vv ticket (you can use the same
password all the time) and to accept collisions with different settings
if someone opens the console from the web UI.

In the end result, using the Perl library mentioned by Sandro above may
be an easier solution.

Or another option is to submit a patch to Engine to make the timeout
configurable (look for TICKET_VALIDITY_SECONDS in the sources).

Regards,
Milan

>>> I would appreciate a reply very much!
>>>
>>> Best regards
>>> Merlin Timm
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/
>>>
>>
>>
>> --
>>
>> Sandro Bonazzola
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>>
>> Red Hat EMEA 
>>
>> sbona...@redhat.com
>> 
>>
>> *Red Hat respects your work life balance. Therefore there is no need to
>> answer this email out of your office hours.
>> *
>>
>>
>>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/PYSQ6UWTTUZBZBE3TNOGVU674M3PC55S/

[ovirt-users] [4.4.7] The latest guest agent needs to be installed and running on the guest

2021-07-08 Thread Christoph Timm 

Hi list,

I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs 
have issues to report the performance information via the guest agent.


I see the following message on the VMs: The latest guest agent needs to 
be installed and running on the guest


The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).

Any advice how to troubleshoot this?

I can see the stats will be presented in the GUI, if I migrate the VM to 
a different host.


Best regards
Christoph

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/4F5X6BK5OYACFSPSLIHWYE2NXQROS5R3/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-08 Thread Sandro Bonazzola 
Il giorno gio 8 lug 2021 alle ore 13:38 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:

> +Milan Zamazal  , +Arik Hadas  , 
> +Michal
> Skrivanek  any hint?
>

I found https://metacpan.org/pod/Ovirt::Display but I think there should be
an easier way within the engine to configure this.



>
> Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 
> ha scritto:
>
>> Good day to all,
>>
>> I have a question about the console configuration of the VMs:
>>
>> By default, for each console connection to a VM, a password is set for
>> 120 seconds, after that you can't use it again. We currently have the
>> following concern:
>>
>> We want to access and control the VMs via the VNC/Spice of the Ovirt
>> host. We have already tried to use the password from the console.vv for
>> the connection and that works so far. Unfortunately we have to do this
>> every 2 minutes when we want to connect again. We are currently building
>> an automatic test pipeline and for this we need to access the VMs
>> remotely before OS start and we want to be independent of a VNC server
>> on the guest. This is only possible if we could connect to the VNC/Spice
>> server from the Ovirt host.
>>
>> My question: would it be possible to fix the password or read it out via
>> api every time you want to connect?
>>
>> I would appreciate a reply very much!
>>
>> Best regards
>> Merlin Timm
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> 
>
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
> *
>
>
>

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/IGVALKUVDLA32JG3RC4KAW33EWMG2BUM/

[ovirt-users] Q: Node Upgrade Path

2021-07-08 Thread Andrei Verovski 
Hi, 


I have 2 oVirt nodes still running on CentOS 7.6.
rpm -qa | grep ovirt - results in version 4.2.

Does it makes sense to upgrade CentOS 7.6 to Stream, and then upgrade oVirt 
Node sw, or just leave for a couple of years till hardware will be trashed?
I’m always keep oVirt Engine up to date, so my only concern if at any point it 
will stop support old Node sw.

Thanks in advance for any suggestion.
Andrei
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/6SCBZF3NASM5UIABKRANHI6UUHXCWG4Y/

[ovirt-users] Re: Set fixed VNC/Spice Password for VMs.

2021-07-08 Thread Sandro Bonazzola 
+Milan Zamazal  , +Arik Hadas 
, +Michal
Skrivanek  any hint?

Il giorno mar 6 lug 2021 alle ore 14:01 Merlin Timm 
ha scritto:

> Good day to all,
>
> I have a question about the console configuration of the VMs:
>
> By default, for each console connection to a VM, a password is set for
> 120 seconds, after that you can't use it again. We currently have the
> following concern:
>
> We want to access and control the VMs via the VNC/Spice of the Ovirt
> host. We have already tried to use the password from the console.vv for
> the connection and that works so far. Unfortunately we have to do this
> every 2 minutes when we want to connect again. We are currently building
> an automatic test pipeline and for this we need to access the VMs
> remotely before OS start and we want to be independent of a VNC server
> on the guest. This is only possible if we could connect to the VNC/Spice
> server from the Ovirt host.
>
> My question: would it be possible to fix the password or read it out via
> api every time you want to connect?
>
> I would appreciate a reply very much!
>
> Best regards
> Merlin Timm
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/BDPGLBQ4DWE64NATDDFDUB2TZLAHS6SV/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/ZGXNZ2EN445REVD4YW7WXOXIEO2MPCGJ/

[ovirt-users] Re: glusterfs health-check failed, (brick) going down

2021-07-08 Thread Jayme 
I have observed this behaviour recently and in the past on 4.3 and 4.4, and
in my case it’s almost always following an ovirt upgrade. After upgrade
(especially upgrades involving glusterfs) I’d have bricks randomly go down
like your describing for about a week or so after upgrade and I’d have to
manually start them. At some point it just corrects itself and is stable
again. I really have no idea why it occurs and what’s happening that
eventually stops it from happening.

On Wed, Jul 7, 2021 at 4:10 PM Jiří Sléžka  wrote:

> Hello,
>
> I have 3 node HCI cluster with oVirt 4.4.6 and CentOS8.
>
> For time to time (I belive) random brick on random host goes down
> because health-check. It looks like
>
> [root@ovirt-hci02 ~]# grep "posix_health_check"
> /var/log/glusterfs/bricks/*
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 07:13:37.408184] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 07:13:37.408407] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still
> alive! -> SIGTERM
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 16:11:14.518971] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 16:11:14.519200] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still
> alive! -> SIGTERM
>
> on other host
>
> [root@ovirt-hci01 ~]# grep "posix_health_check"
> /var/log/glusterfs/bricks/*
> /var/log/glusterfs/bricks/gluster_bricks-engine-engine.log:[2021-07-05
> 13:15:51.983327] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-engine-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-engine-engine.log:[2021-07-05
> 13:15:51.983728] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-engine-posix:
> still alive! -> SIGTERM
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-05
> 01:53:35.769129] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-05
> 01:53:35.769819] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still
> alive! -> SIGTERM
>
> I cannot link these errors to any storage/fs issue (in dmesg or
> /var/log/messages), brick devices looks healthy (smartd).
>
> I can force start brick with
>
> gluster volume start vms|engine force
>
> and after some healing all works fine for few days
>
> Did anybody observe this behavior?
>
> vms volume has this structure (two bricks per host, each is separate
> JBOD ssd disk), engine volume has one brick on each host...
>
> gluster volume info vms
>
> Volume Name: vms
> Type: Distributed-Replicate
> Volume ID: 52032ec6-99d4-4210-8fb8-ffbd7a1e0bf7
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 2 x 3 = 6
> Transport-type: tcp
> Bricks:
> Brick1: 10.0.4.11:/gluster_bricks/vms/vms
> Brick2: 10.0.4.13:/gluster_bricks/vms/vms
> Brick3: 10.0.4.12:/gluster_bricks/vms/vms
> Brick4: 10.0.4.11:/gluster_bricks/vms2/vms2
> Brick5: 10.0.4.13:/gluster_bricks/vms2/vms2
> Brick6: 10.0.4.12:/gluster_bricks/vms2/vms2
> Options Reconfigured:
> cluster.granular-entry-heal: enable
> performance.stat-prefetch: off
> cluster.eager-lock: enable
> performance.io-cache: off
> performance.read-ahead: off
> performance.quick-read: off
> user.cifs: off
> network.ping-timeout: 30
> network.remote-dio: off
> performance.strict-o-direct: on
> performance.low-prio-threads: 32
> features.shard: on
> storage.owner-gid: 36
> storage.owner-uid: 36
> transport.address-family: inet
> storage.fips-mode-rchecksum: on
> nfs.disable: on
> performance.client-io-threads: off
>
> Cheers,
>
> Jiri
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/BPXG53NG34QKCABYJ35UYIWPNNWTKXW4/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BZRONK53OGWSOPUSGQ76GIXUM7J6HHMJ/

[ovirt-users] Re: Updates failing

2021-07-08 Thread Konstantin Shalygin 
You should put your host to maintaince mode before install updates


Cheers,
k

Sent from my iPhone

> On 6 Jul 2021, at 23:42, Gary Pedretty  wrote:
> 
> Getting errors trying to run dnf/yum update due to a vdsm issue.
> 
> 
> yum update
> Last metadata expiration check: 0:17:33 ago on Tue 06 Jul 2021 11:17:05 AM 
> AKDT.
> Error: Running QEMU processes found, cannot upgrade Vdsm.
> 
> Current running version of vdsm is
> 
> 
> vdsm-4.40.60.7-1.el8
> 
> 
> CentOS Stream
> RHEL - 8.5 - 3.el8
> 
> kernel
> 4.18.0 - 310.el8.x86_64
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/S5IWT7Z67YPXLE6P6IGER6F4RFGQTCHS/

[ovirt-users] Re: glusterfs health-check failed, (brick) going down

2021-07-08 Thread Sandro Bonazzola 
I would recommend asking also on glusterfs users mailing list about this.

Il giorno mer 7 lug 2021 alle ore 21:09 Jiří Sléžka  ha
scritto:

> Hello,
>
> I have 3 node HCI cluster with oVirt 4.4.6 and CentOS8.
>
> For time to time (I belive) random brick on random host goes down
> because health-check. It looks like
>
> [root@ovirt-hci02 ~]# grep "posix_health_check"
> /var/log/glusterfs/bricks/*
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 07:13:37.408184] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 07:13:37.408407] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still
> alive! -> SIGTERM
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 16:11:14.518971] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-07
> 16:11:14.519200] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still
> alive! -> SIGTERM
>
> on other host
>
> [root@ovirt-hci01 ~]# grep "posix_health_check"
> /var/log/glusterfs/bricks/*
> /var/log/glusterfs/bricks/gluster_bricks-engine-engine.log:[2021-07-05
> 13:15:51.983327] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-engine-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-engine-engine.log:[2021-07-05
> 13:15:51.983728] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-engine-posix:
> still alive! -> SIGTERM
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-05
> 01:53:35.769129] M [MSGID: 113075]
> [posix-helpers.c:2214:posix_health_check_thread_proc] 0-vms-posix:
> health-check failed, going down
> /var/log/glusterfs/bricks/gluster_bricks-vms2-vms2.log:[2021-07-05
> 01:53:35.769819] M [MSGID: 113075]
> [posix-helpers.c:2232:posix_health_check_thread_proc] 0-vms-posix: still
> alive! -> SIGTERM
>
> I cannot link these errors to any storage/fs issue (in dmesg or
> /var/log/messages), brick devices looks healthy (smartd).
>
> I can force start brick with
>
> gluster volume start vms|engine force
>
> and after some healing all works fine for few days
>
> Did anybody observe this behavior?
>
> vms volume has this structure (two bricks per host, each is separate
> JBOD ssd disk), engine volume has one brick on each host...
>
> gluster volume info vms
>
> Volume Name: vms
> Type: Distributed-Replicate
> Volume ID: 52032ec6-99d4-4210-8fb8-ffbd7a1e0bf7
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 2 x 3 = 6
> Transport-type: tcp
> Bricks:
> Brick1: 10.0.4.11:/gluster_bricks/vms/vms
> Brick2: 10.0.4.13:/gluster_bricks/vms/vms
> Brick3: 10.0.4.12:/gluster_bricks/vms/vms
> Brick4: 10.0.4.11:/gluster_bricks/vms2/vms2
> Brick5: 10.0.4.13:/gluster_bricks/vms2/vms2
> Brick6: 10.0.4.12:/gluster_bricks/vms2/vms2
> Options Reconfigured:
> cluster.granular-entry-heal: enable
> performance.stat-prefetch: off
> cluster.eager-lock: enable
> performance.io-cache: off
> performance.read-ahead: off
> performance.quick-read: off
> user.cifs: off
> network.ping-timeout: 30
> network.remote-dio: off
> performance.strict-o-direct: on
> performance.low-prio-threads: 32
> features.shard: on
> storage.owner-gid: 36
> storage.owner-uid: 36
> transport.address-family: inet
> storage.fips-mode-rchecksum: on
> nfs.disable: on
> performance.client-io-threads: off
>
> Cheers,
>
> Jiri
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@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/BPXG53NG34QKCABYJ35UYIWPNNWTKXW4/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/BMIRJBLFWAVSTKFERBXKLV6KDD4UIZSD/