[ovirt-users] Re: Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Aries Ahito
ok i will try that. ive been using ovirt since 3.4 and we are using san storage, and we have hosted engine with nfs. this is my first time using gluster. On Wed, 16 Dec 2020, 12:42 Parth Dhanjal, wrote: > Hey! > > Storage connection: 10.33.50.33/VOL1 > Do check if this mount point is correct.

[ovirt-users] Re: Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Parth Dhanjal
Hey! Storage connection: 10.33.50.33/VOL1 Do check if this mount point is correct. You can look for mount points through your server terminal Mount Option:backup-volfile-servers=<> In case you don't have a 3rd host, I'll recommend adding one to the cluster. Having a replica 2 volume can cause a

[ovirt-users] Re: Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Aries Ahito
nope i didnt since i dont know what parameters i will input.. could you help me so i have this gluster with replica 2 configuration 10.33.50.33:/VOL1VOL1 10.33.50.34:/VOL1/VOL1 thanks On Wed, Dec 16, 2020 at 12:09 PM Parth Dhanjal wrote: > Hey! > > Did you input a mount point? > It seems

[ovirt-users] Re: Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Parth Dhanjal
Hey! Did you input a mount point? It seems from the error message that either the mount point was missing or was wrong. On Wed, Dec 16, 2020 at 6:07 AM Ariez Ahito wrote: > HI guys, i have installed ovirt 4.4 hosted engine and a separate glusterfs > storage. > now during hosted engine

[ovirt-users] Cannot connect Glusterfs storage to Ovirt

2020-12-15 Thread Ariez Ahito
HI guys, i have installed ovirt 4.4 hosted engine and a separate glusterfs storage. now during hosted engine deployment when i try do choose STORAGE TYPE: gluster Storage connection: 10.33.50.33/VOL1 Mount Option: when i try to connect this gives me an error: [ ERROR ] ovirtsdk4.Error: Fault

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lionel Caignec
Ok it's done bugzilla 1907973, i found this message "Guest CPU doesn't match specification: missing features: tsx-ctrl (migration:294)" it's seems you're theory is good. De: "Arik Hadas" À: "Lionel Caignec" Cc: "users" Envoyé: Mardi 15 Décembre 2020 15:50:26 Objet: Re: [ovirt-users]

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Arik Hadas
On Tue, Dec 15, 2020 at 4:41 PM Lionel Caignec wrote: > Hi Arik, > > Yes, my problem about cpu type, seems linked to the fact i've upgraded a > host in 8.3 before ugprade ovirt in 4.3... > > I've done another test, for my problem of vm migration. > I start a guest directly on the 8.3 nodes then

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lionel Caignec
Hi Arik, Yes, my problem about cpu type, seems linked to the fact i've upgraded a host in 8.3 before ugprade ovirt in 4.3... I've done another test, for my problem of vm migration. I start a guest directly on the 8.3 nodes then it can be migrate from/to 8.2/83. I've also tried to force it

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Arik Hadas
On Tue, Dec 15, 2020 at 3:29 PM Lionel Caignec wrote: > Hi > > thank you it's work now. All my host 8.2/8.3 are up and running. During > reactivation of 8.2 host i saw the log line "updating cluster CPU..." > Good to see that it works for you now (the credit to Lucia). So the cluster

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lionel Caignec
Hi thank you it's work now. All my host 8.2/8.3 are up and running. During reactivation of 8.2 host i saw the log line "updating cluster CPU..." I tried to move guest from 8.2 host to 8.3 one but it failed. Engine.log : ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lucia Jelinkova
Hi Lionel, if you managed to remove the host (or move it to a different cluster) so that all hosts in your cluster are UP - you could try to put one of your running hosts to the maintenance and then back to active - the cluster settings should be updated on the host activation. You can look for

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Martin Perina
On Tue, Dec 15, 2020 at 12:59 PM Alex K wrote: > > > On Tue, Dec 15, 2020 at 1:43 PM emesika wrote: > >> The problem is that the custom fencing configuration is not defined well >> >> Please follow [1] and retry >> >> [1] >>

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Alex K
On Tue, Dec 15, 2020 at 1:43 PM emesika wrote: > The problem is that the custom fencing configuration is not defined well > > Please follow [1] and retry > > [1] > https://www.ovirt.org/develop/developer-guide/engine/custom-fencing.html > Yes, I followed that. I cannot see what I am missing:

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lionel Caignec
Thank you i understand now. I double checked all my 8.2 host about cababilities and they seems ok. I think i foudn the source of this "bug". For this time i've updated one host in 8.3 (the non operative one), and then i update engine and run engine-setup (with all host up and activated

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread emesika
The problem is that the custom fencing configuration is not defined well Please follow [1] and retry [1] https://www.ovirt.org/develop/developer-guide/engine/custom-fencing.html On Tue, Dec 15, 2020 at 12:56 PM Alex K wrote: > > > On Tue, Dec 15, 2020 at 12:34 PM Martin Perina wrote: > >>

[ovirt-users] Re: How to unlock disk images?

2020-12-15 Thread thomas
Unlocked the snapshot, deleted the VM... done! That was easiser than I thought. Thanks for your help in any case! ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement:

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Alex K
On Tue, Dec 15, 2020 at 12:34 PM Martin Perina wrote: > > > On Tue, Dec 15, 2020 at 11:18 AM Alex K wrote: > >> >> >> On Tue, Dec 15, 2020 at 11:59 AM Martin Perina >> wrote: >> >>> Hi, >>> >>> could you please provide engine.log? And also vdsm.log from a host which >>> was acting as a fence

[ovirt-users] Re: How to unlock disk images?

2020-12-15 Thread thomas
And I should have guessed, that this is only how trouble starts =:-O I immediately removed the locked snapshot image (actually they pretty much seemed to disappear by themselves as delete operations might have been pending) but the VM that was doing the snapshot, is still there, even if the

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Martin Perina
On Tue, Dec 15, 2020 at 11:18 AM Alex K wrote: > > > On Tue, Dec 15, 2020 at 11:59 AM Martin Perina wrote: > >> Hi, >> >> could you please provide engine.log? And also vdsm.log from a host which >> was acting as a fence proxy? >> > > At proxy host (kvm1) I see the following vdsm.log: > >

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lucia Jelinkova
Hi Lionel, in oVirt 4.4.2 the Secure Intel Cascadelake Server Family was configured to use the Cascadelake-Server libvirt/qemu CPU. In oVirt 4.4.3, this has been changed to Cascadelake-Server-noTSX libvirt/qemu CPU (since the TSX was dropped in 8.3). The problem you're facing is caused by this

[ovirt-users] Re: How to unlock disk images?

2020-12-15 Thread thomas
Thanks Shani, I had just found that myself and even managed to unlock and remove the images. Somehow the reference to https://ovirt.org/develop/developer-guide/ seems to not be available from the ovirt site navigation but now I have discovered it via another post here and found a treasure

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Alex K
On Tue, Dec 15, 2020 at 11:59 AM Martin Perina wrote: > Hi, > > could you please provide engine.log? And also vdsm.log from a host which > was acting as a fence proxy? > At proxy host (kvm1) I see the following vdsm.log: 2020-12-15 10:13:03,933+ INFO (jsonrpc/0) [jsonrpc.JsonRpcServer]

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lionel Caignec
Hi All, and thanks for helping me So if i does not mistakte, we cannot use anymore cascadelake Server in centos 8.3? Cluster configuration is Secure CascadeLake Server Family Here is output of the sql query : name | cpu_name | cpu_flags | cpu_verb

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Martin Perina
Hi, could you please provide engine.log? And also vdsm.log from a host which was acting as a fence proxy? Thanks, Martin On Tue, Dec 15, 2020 at 10:23 AM Alex K wrote: > > > On Tue, Dec 15, 2020 at 11:07 AM Alex K wrote: > >> >> >> On Mon, Dec 14, 2020 at 8:59 PM Strahil Nikolov >> wrote:

[ovirt-users] Re: illegal disk status

2020-12-15 Thread Benny Zlotnik
you can use: $ vdsm-client Volume delete (you can use --help to see the params) After this you'll need to remove the corresponding image manually from the database images table, mark the parent image as active, remove the snapshot from the snapshots table and fix the parent snapshot Be sure to

[ovirt-users] Re: How to unlock disk images?

2020-12-15 Thread Shani Leviim
Hi Thomas, You can use unlock_entity.sh[1] to list the unlock entities and remove them. [1] https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities.html *Regards,* *Shani Leviim* On Tue, Dec 15, 2020 at 10:45 AM wrote: > On one oVirt 4.3 farm I have three locked images I'd

[ovirt-users] Re: Nodes install Python3 every day

2020-12-15 Thread Sandro Bonazzola
Il giorno mar 15 dic 2020 alle ore 10:16 jb ha scritto: > > Am 15.12.20 um 09:06 schrieb Dana Elfassy: > > Yes, I'll edit the title. > > Jonathan, you can see in the log you pasted: > *'task': 'Install Python3 for CentOS/RHEL8 hosts'*, 'task_uuid': > '00163e33-f845-ee64-acee-0013',

[ovirt-users] Re: Bad CPU TYPE after Centos 8.3

2020-12-15 Thread Lucia Jelinkova
Hi Lionel, Thank you for the output from the virsh command. The interesting part is this: Cascadelake-Server-noTSX Cascadelake-Server The Cascadelake-Server is not usable any more in 8.3 [1] yet that is what the cluster is probably configured with. Could you please run the following query for

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Alex K
On Tue, Dec 15, 2020 at 11:07 AM Alex K wrote: > > > On Mon, Dec 14, 2020 at 8:59 PM Strahil Nikolov > wrote: > >> Fence_xvm requires a key is deployed on both the Host and the VMs in >> order to succeed. What is happening when you use the cli on any of the VMs ? >> Also, the VMs require an

[ovirt-users] Re: Nodes install Python3 every day

2020-12-15 Thread jb
Am 15.12.20 um 09:06 schrieb Dana Elfassy: Yes, I'll edit the title. Jonathan, you can see in the log you pasted: *'task': 'Install Python3 for CentOS/RHEL8 hosts'*, 'task_uuid': '00163e33-f845-ee64-acee-0013', 'task_action': 'yum', 'task_args': '', 'task_path':

[ovirt-users] Re: fence_xvm for testing

2020-12-15 Thread Alex K
On Mon, Dec 14, 2020 at 8:59 PM Strahil Nikolov wrote: > Fence_xvm requires a key is deployed on both the Host and the VMs in order > to succeed. What is happening when you use the cli on any of the VMs ? > Also, the VMs require an open tcp port to receive the necessary output of > each

[ovirt-users] How to unlock disk images?

2020-12-15 Thread thomas
On one oVirt 4.3 farm I have three locked images I'd like to clear out. One is an ISO image, that somehow never completed the transfer due to a slow network. It's occupying little space, except in the GUI where it sticks out and irritates. I guess it would just be an update somewhere on the

[ovirt-users] Re: CentOS 8 is dead

2020-12-15 Thread thomas
I am glad you think so and it works for you. But I'd also guess that you put more than a partial FTE to the project. I got attracted via the HCI angle they started pushing as a result of Nutanix creating a bit of a stir. The ability to use discarded production boxes for a lab with the

[ovirt-users] Re: CentOS 8 is dead

2020-12-15 Thread James Loker-Steele via Users
Also we have begun using OLVM based on tests we conducted with ovirt a while ago. Only issue is olvm is currently stuck on 4.3.6 and waiting for oracle to release updates is a slow process. Personally I would have liked to use ovirt but apparently using oracle is better for the Databases.

[ovirt-users] Re: Nodes install Python3 every day

2020-12-15 Thread Dana Elfassy
Yes, I'll edit the title. Jonathan, you can see in the log you pasted: *'task': 'Install Python3 for CentOS/RHEL8 hosts'*, 'task_uuid': '00163e33-f845-ee64-acee-0013', 'task_action': 'yum', 'task_args': '', 'task_path':

[ovirt-users] Re: CentOS 8 is dead

2020-12-15 Thread thomas
Hi Strahil, OpenVZ is winding down, unfortunately. They haven't gone near CentOS8 yet any I don't see that happen either. It's very unfortunate, because I really loved that project and I always preferred its container abstraction as well as the resource management tools, because scale-in is

[ovirt-users] Re: CentOS 8 is dead

2020-12-15 Thread James Loker-Steele via Users
This is what we are planning to do. We made a decision a while ago to start using oracle Linux as we are already an oracle db house. We have centos machines and are slowly ditching Ubuntu and Debian. Moving to OEL is the logical choice. ___ Users