[ovirt-users] Re: oVirt over gluster: Replacing a dead host

2022-07-23 Thread Gilboa Davara
Hello,

Many thanks for your reply.
So not only did I need to remove the broken brick
(office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick), I should have also remove
the active arbiter (office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick)?

Thanks again,
Gilboa

On Fri, Jul 22, 2022 at 10:09 PM Strahil Nikolov 
wrote:

> There is no need to stop the volume, the operation can be done online.
>
> gluster volume remove-brick GV2Data repica 1
> office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick
> office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick force
>
> replica 1 -> remaining copies ( only Brick 2 remains)
>
> When you got a replacement brick define the brick first and the arbiter
> second (don't forget to define the replica 3 arbiter 1 change /I think this
> notation is still valid/ ).
>
>
> Best Regards,
> Strahil Nikolov
>
>
> On Thu, Jul 21, 2022 at 14:09, Gilboa Davara
>  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/K4UVL3LQCTOFW2MIPYE5OFAIJNJSRJEQ/
>
>
___
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/6LOFWLT7HX3KNJ7FTOPBN6LWVTEXHMBH/


[ovirt-users] ovirt-aaa-jdbc-tool and Keycloak

2022-07-22 Thread Gilboa Davara
Hello all,

I have a number of oVirt clusters that  were recently upgraded to v.4.5.1.
As far as I can see, once keycloak is enabled, local users can no longer
login. (only admin@ovirt works).
Assuming I need to continue using local AAA users (created using
ovirt-aaa-jdbc-tool), should I disable keycloak support? How do I do it?
(engine-setup?).

- Gilboa
___
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/WMLL5SMG4RDPSO6LDTQWBFNUXLLK64SV/


[ovirt-users] Re: oVirt over gluster: Replacing a dead host

2022-07-21 Thread Gilboa Davara
Hello,


$ gluster volume info GV2Data
 Volume Name: GV2Data
Type: Replicate
Volume ID: c1946fc2-ed94-4b9f-9da3-f0f1ee90f303
Status: Stopped
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick  <-- This is the
dead host.
Brick2: office-wx-hv2-lab-gfs:/mnt/LogGFSData/brick
Brick3: office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick (arbiter)

I tried to remove the dead brick, and failed.
*$ gluster volume remove-brick GV2Data replica 1
office-wx-hv1-lab-gfs:/mnt/**LogGFSData/brick force*
...volume remove-brick start: failed: need 2(xN) bricks for reducing
replica count of the volume from 3 to 1

What was I doing wrong?
(Assuming my original configuration, 2 + 1, was acceptable).

- Gilboa

On Wed, Jul 20, 2022 at 7:14 PM Strahil Nikolov 
wrote:

> The remove-brick expects the bricks that have to be removed.
> Yet, you specified 1 brick, so 2 are left in the volume -> yet you
> specified 'replica 1'.
> Define both the data brick and the arbiter brick.
>
> Best Regards,
> Strahil Nikolov
>
> On Wed, Jul 20, 2022 at 13:34, Gilboa Davara
>  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/I2S247DEVERX7NPBNGJOU26QSNXMPPTO/
>
>
___
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/K4UVL3LQCTOFW2MIPYE5OFAIJNJSRJEQ/


[ovirt-users] Re: oVirt over gluster: Replacing a dead host

2022-07-20 Thread Gilboa Davara
Hello,

Tried it:
*$ gluster volume remove-brick GV2Data replica 1
office-wx-hv1-lab-gfs:/mnt/**LogGFSData/brick force*
Running remove-brick with cluster.force-migration enabled can result in
data corruption. It is safer to disable this option so that files that
receive writes during migration are not migrated.
Files that are not migrated can then be manually copied after the
remove-brick commit operation.
Do you want to continue with your current cluster.force-migration settings?
(y/n) y
volume remove-brick start: failed: need 2(xN) bricks for reducing replica
count of the volume from 3 to 1

- Gilboa


On Tue, Jul 19, 2022 at 11:36 PM Strahil Nikolov 
wrote:

> Replacing a dead brick in a 2+1 scenario (2 data + 1 arbiter brick)
> requires to reduce the replica to 1 by removing the dead brick and the
> arbiter.
> Use the force option as you are not using a distributed-replicated volume .
>
> Best Regards,
> Strahil Nikolov
>
> On Mon, Jul 18, 2022 at 11:36, Patrick Hibbs
>  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/XIA6UN3ULXCN55PPVNGV5KVFNGZSRBLV/
>
>
___
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/I2S247DEVERX7NPBNGJOU26QSNXMPPTO/


[ovirt-users] Re: oVirt over gluster: Replacing a dead host

2022-07-17 Thread Gilboa Davara
Hello,

Many thanks for your email.
I should add that this is a test environment we set up in preparation for a
planned CentOS 7 / oVirt 4.3 upgrade to CentOS 8 Streams / oVirt 4.5
upgrade in one of our old(er) oVirt clusters.
In this case, we blew up the software RAID during the OS replacement
(CentOS 7 -> 8) so have a host, but no storage.
And as an added bonus, the FS locations are a bit different. (due MD
changes we made during the blowup).

So, essentially the host is alive, but we need to create a new brick using
a known good brick.
A couple of questions:
Assuming I have a known good brick to copy but the FS location is different
and given the fact I cannot simply remove/add brick, how do I change the
brick path?
Old location:
office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick
New location:
office-wx-hv1-lab-gfs.localdomain:/gluster/brick/data/brick
Thanks again,
Gilboa

On Mon, Jul 18, 2022 at 1:32 AM Patrick Hibbs 
wrote:

> What you are missing is the fact that gluster requires more than one set
> of bricks to recover from a dead host. I.e. In your set up, you'd need 6
> hosts. 4x replicas and 2x arbiters with at least one set (2x replicas and
> 1x arbiter) operational bare minimum.
> Automated commands to fix the volume do not exist otherwise. (It's a
> Gluster limitation.) This can be fixed manually however.
>
> Standard Disclaimer: Back up your data first! Fixing this issue requires
> manual intervention. Reader assumes all responsiblity for any action
> resulting from the instructions below. Etc.
>
> If it's just a dead brick, (i.e. the host is still functional), all you
> really need to do is replace the underlying storage:
>
> 1. Take the gluster volume offline.
> 2. Remove the bad storage device, and attach the replacement.
> 3. rsync / scp / etc. the data from a known good brick (be sure to include
> hidden files / preserve file times and ownership / SELinux labels / etc. ).
> 4. Restart the gluster volume.
>
> Gluster *might* still need to heal everything after all of that, but it
> should start the volume and get it running again.
>
> If the host itself is dead, (and the underlying storage is still
> functional), you can just move the underlying storage over to the new host:
>
> 1. Take the gluster volume offline.
> 2. Attach the old storage.
> 3. Fix up the ids on the volume file. (
> https://serverfault.com/questions/631365/rename-a-glusterfs-peer)
> 4. Restart the gluster volume.
>
> If both the host and underlying storage are dead, you'll need to do both
> tasks:
>
> 1. Take the gluster volume offline.
> 2. Attach the new storage.
> 3. rsync / scp / etc. the data from a known good brick (be sure to
> include hidden files / preserve file times and ownership / SELinux labels /
> etc. ).
> 4. Fix up the ids on the volume file.
> 5. Restart the gluster volume.
>
> Keep in mind one thing however: If the gluster host you are replacing is
> used by oVirt to connect to the volume (I.e. It's the host named in the
> volume config in the Admin portal). The new host will need to retain the
> old hostname / IP, or you'll need to update oVirt's config. Otherwise the
> VM hosts will wind up in Unassigned / Non-functional status.
>
> - Patrick Hibbs
>
> On Sun, 2022-07-17 at 22:15 +0300, Gilboa Davara wrote:
>
> Hello all,
>
> I'm attempting to replace a dead host in a replica 2 + arbiter gluster
> setup and replace it with a new host.
> I've already set up a new host (same hostname..localdomain) and got into
> the cluster.
>
> $ gluster peer status
> Number of Peers: 2
>
> Hostname: office-wx-hv3-lab-gfs
> Uuid: 4e13f796-b818-4e07-8523-d84eb0faa4f9
> State: Peer in Cluster (Connected)
>
> Hostname: office-wx-hv1-lab-gfs.localdomain <-- This is a new host.
> Uuid: eee17c74-0d93-4f92-b81d-87f6b9c2204d
> State: Peer in Cluster (Connected)
>
> $ gluster volume info GV2Data
>  Volume Name: GV2Data
> Type: Replicate
> Volume ID: c1946fc2-ed94-4b9f-9da3-f0f1ee90f303
> Status: Stopped
> Snapshot Count: 0
> Number of Bricks: 1 x (2 + 1) = 3
> Transport-type: tcp
> Bricks:
> Brick1: office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick  <-- This is the
> dead host.
> Brick2: office-wx-hv2-lab-gfs:/mnt/LogGFSData/brick
> Brick3: office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick (arbiter)
> ...
>
> Looking at the docs, it seems that I need to remove the dead brick.
>
> $ gluster volume remove-brick GV2Data
> office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start
> Running remove-brick with cluster.force-migration enabled can result in
> data corruption. It is safer to disable this option so that files that
> receive writes during migration are not migrated.
> Files that are not migrated can then be manually copied after the
> remove-bri

[ovirt-users] oVirt over gluster: Replacing a dead host

2022-07-17 Thread Gilboa Davara
Hello all,

I'm attempting to replace a dead host in a replica 2 + arbiter gluster
setup and replace it with a new host.
I've already set up a new host (same hostname..localdomain) and got into
the cluster.

$ gluster peer status
Number of Peers: 2

Hostname: office-wx-hv3-lab-gfs
Uuid: 4e13f796-b818-4e07-8523-d84eb0faa4f9
State: Peer in Cluster (Connected)

Hostname: office-wx-hv1-lab-gfs.localdomain <-- This is a new host.
Uuid: eee17c74-0d93-4f92-b81d-87f6b9c2204d
State: Peer in Cluster (Connected)

$ gluster volume info GV2Data
 Volume Name: GV2Data
Type: Replicate
Volume ID: c1946fc2-ed94-4b9f-9da3-f0f1ee90f303
Status: Stopped
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick  <-- This is the
dead host.
Brick2: office-wx-hv2-lab-gfs:/mnt/LogGFSData/brick
Brick3: office-wx-hv3-lab-gfs:/mnt/LogGFSData/brick (arbiter)
...

Looking at the docs, it seems that I need to remove the dead brick.

$ gluster volume remove-brick GV2Data
office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start
Running remove-brick with cluster.force-migration enabled can result in
data corruption. It is safer to disable this option so that files that
receive writes during migration are not migrated.
Files that are not migrated can then be manually copied after the
remove-brick commit operation.
Do you want to continue with your current cluster.force-migration settings?
(y/n) y
volume remove-brick start: failed: Removing bricks from replicate
configuration is not allowed without reducing replica count explicitly

So I guess I need to drop from replica 2 + arbiter to replica 1 + arbiter
(?).

$ gluster volume remove-brick GV2Data replica 1
office-wx-hv1-lab-gfs:/mnt/LogGFSData/brick start
Running remove-brick with cluster.force-migration enabled can result in
data corruption. It is safer to disable this option so that files that
receive writes during migration are not migrated.
Files that are not migrated can then be manually copied after the
remove-brick commit operation.
Do you want to continue with your current cluster.force-migration settings?
(y/n) y
volume remove-brick start: failed: need 2(xN) bricks for reducing replica
count of the volume from 3 to 1

... What am I missing?

- Gilboa
___
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/OIXTFTJREUAHGP3WUW7DFL3VJNEMFJLF/


[ovirt-users] Re: gluster heal success but a directory doesn't heal

2022-06-28 Thread Gilboa Davara
Have you tried using the gluster ML?
https://lists.gluster.org/mailman/listinfo/gluster-users

- Gilboa

On Tue, Jun 28, 2022 at 11:20 AM Diego Ercolani 
wrote:

> I've done something but the problem remain:
> [root@ovirt-node2 ~]# gluster volume heal glen info
> Brick ovirt-node2.ovirt:/brickhe/glen
> /3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks
> Status: Connected
> Number of entries: 1
>
> Brick ovirt-node3.ovirt:/brickhe/glen
> /3577c21e-f757-4405-97d1-0f827c9b4e22/images
> Status: Connected
> Number of entries: 1
>
> Brick ovirt-node4.ovirt:/dati/glen
> /3577c21e-f757-4405-97d1-0f827c9b4e22/master/tasks
> /3577c21e-f757-4405-97d1-0f827c9b4e22/images
> Status: Connected
> Number of entries: 2
>
> And I cannot invoke healing:
> [root@ovirt-node2 ~]# gluster volume heal glen full
> Launching heal operation to perform full self heal on volume glen has been
> successful
> Use heal info commands to check status.
> [root@ovirt-node2 ~]# gluster volume heal glen split-brain source-brick
> ovirt-node3.ovirt:/brickhe/glen
> 'source-brick' option used on a directory
> (gfid:95e5075e-720b-4bc0-affe-81d1792e09a6). Performing conservative merge.
> Healing gfid:95e5075e-720b-4bc0-affe-81d1792e09a6 failed:Is a directory.
> Lookup failed on gfid:75441538-fc18-4da3-9da7-e1c59a84d950:No such file or
> directory.
> Status: Connected
> Number of healed entries: 0
>
> ___
> 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/YN3TOB45KTKXAMZNGNEAMPUM7ML2I6W3/
>
___
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/7K5QQLWIPOBQTP5C7UA75D5TTHAWDGTD/


[ovirt-users] Re: Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
Done.
https://bugzilla.redhat.com/show_bug.cgi?id=2100194

Thanks again!
- Gilboa

On Wed, Jun 22, 2022 at 8:01 PM Benny Zlotnik  wrote:

> > Regarding the BZ#, which component should I choose?
> ovirt-engine-ui-extensions
>
> > Wouldn't the bug get auto-closed, as I'm still using 4.4.10?
> Well, it still exists in 4.5 so it shouldn't auto-close
>
>
___
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/JCSRRG7C3SWWRDVJRZQIKAXZDZ7POFPS/


[ovirt-users] Re: Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
$ psql engine
select original_template_id engine-# from vm_static engine-# where vm_guid
= '16b5df4b-c3b5-4899-b5b1-336c3462494c';
 original_template_id
--
 (1 row)
update vm_static set original_template_id =
'----' where vm_guid =
'16b5df4b-c3b5-4899-b5b1-336c3462494c';
UPDATE 1
select original_template_id from vm_static where vm_guid =
'16b5df4b-c3b5-4899-b5b1-336c3462494c';
 original_template_id
--
 ----
(1 row)

Now export works as advertised. Thanks.

Regarding the BZ#, which component should I choose?
Wouldn't the bug get auto-closed, as I'm still using 4.4.10?

- Gilboa


On Wed, Jun 22, 2022 at 7:05 PM Benny Zlotnik  wrote:

> Can you submit a bug? Looks like we may need to change this validation
>
> For a workaround, verify in the database that the original_template_id is
> null
>
> select original_template_id
> from vm_static
> where vm_guid = '16b5df4b-c3b5-4899-b5b1-336c3462494c';
>
> if it indeed is you can set it to ----:
> update vm_static
> set original_template_id = '----'
> where vm_guid = '16b5df4b-c3b5-4899-b5b1-336c3462494c';
>
> On Wed, Jun 22, 2022 at 6:47 PM Gilboa Davara  wrote:
> >
> > Works, thanks!
> >
> > Pretty large json, but there's no original_template field. (See
> attached).
> >
> > - Gilboa
> >
> > On Wed, Jun 22, 2022 at 6:40 PM Benny Zlotnik 
> wrote:
> >>
> >> can you try with user@internal?
> >>
> >>
> >>
> >> On Wed, Jun 22, 2022 at 6:10 PM Gilboa Davara 
> wrote:
> >> >
> >> > Thanks for the prompt reply.
> >> > How can I authenticate?
> >> >
> >> > No matter what user / password combo I use (including the full fqdn,
> user@internal-authz) I get the following error:
> >> > access_denied: Cannot authenticate user 'XXX': No valid profile found
> in credentials..
> >> >
> >> > - Gilboa
> >> >
> >> > On Wed, Jun 22, 2022 at 5:49 PM Benny Zlotnik 
> wrote:
> >> >>
> >> >> Seems like the issue is in this line[1], can you send an API request
> >> >> manually to: https://ovirt-fqdn/ovirt-engine/api/vms/
> >> >> and check the original_template field?
> >> >> Should look like this:
> >> >>  >> >>
> href="/ovirt-engine/api/templates/e9dbb5c0-19b6-46ea-b80f-8813758adaa1"
> >> >> id="e9dbb5c0-19b6-46ea-b80f-8813758adaa1"/>
> >> >>
> >> >>
> >> >> [1]
> https://github.com/oVirt/ovirt-engine-ui-extensions/blob/a85d47d644d5785483fc81e2eae8bdc51d559aef/src/modals/vm-export/VmExportDataProvider.js#L43
> >> >>
> >> >> On Wed, Jun 22, 2022 at 5:30 PM Gilboa Davara 
> wrote:
> >> >> >
> >> >> > Hello,
> >> >> >
> >> >> > On Wed, Jun 22, 2022 at 4:56 PM Benny Zlotnik 
> wrote:
> >> >> >>
> >> >> >> can you check the dev console for messages? (F12 in
> chrome/firefox)
> >> >> >
> >> >> >
> >> >> >  error  export problem: TypeError: o.original_template is undefined
> >> >> > Sa VmExportDataProvider.js:43
> >> >> > Sa VmExportDataProvider.js:58
> >> >> > onClick VmExportModal.js:45
> >> >> > React 9
> >> >> > unstable_runWithPriority scheduler.production.min.js:20
> >> >> > React 3
> >> >> > VmExportModal.js:49:14
> >> >> >
> >> >> > - Gilboa
> >> >> >
> >> >> >>
> >> >> >> On Wed, Jun 22, 2022 at 4:53 PM Gilboa Davara 
> wrote:
> >> >> >> >
> >> >> >> > P.S. I have no issues exporting this VM using the deprecated
> "export domain" method.
> >> >> >> >
> >> >> >> > - Gilboa
> >> >> >> >
> >> >> >> > On Wed, Jun 22, 2022 at 4:48 PM Gilboa Davara <
> gilb...@gmail.com> wrote:
> >> >> >> >>
> >> >> >> >> Hello,
> >> >> >> >>
> >> >> >> >> 4.4.10 Gluster based cluster w/ 3 nodes.
> >> >> >> >> I'm backing up all VMs before upgrading the setup to 4.5.
> (Hopefully done right before 4.5.1 w/ Gluster

[ovirt-users] Re: Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
Works, thanks!

Pretty large json, but there's no original_template field. (See attached).

- Gilboa

On Wed, Jun 22, 2022 at 6:40 PM Benny Zlotnik  wrote:

> can you try with user@internal?
>
>
>
> On Wed, Jun 22, 2022 at 6:10 PM Gilboa Davara  wrote:
> >
> > Thanks for the prompt reply.
> > How can I authenticate?
> >
> > No matter what user / password combo I use (including the full fqdn,
> user@internal-authz) I get the following error:
> > access_denied: Cannot authenticate user 'XXX': No valid profile found in
> credentials..
> >
> > - Gilboa
> >
> > On Wed, Jun 22, 2022 at 5:49 PM Benny Zlotnik 
> wrote:
> >>
> >> Seems like the issue is in this line[1], can you send an API request
> >> manually to: https://ovirt-fqdn/ovirt-engine/api/vms/
> >> and check the original_template field?
> >> Should look like this:
> >>  >> href="/ovirt-engine/api/templates/e9dbb5c0-19b6-46ea-b80f-8813758adaa1"
> >> id="e9dbb5c0-19b6-46ea-b80f-8813758adaa1"/>
> >>
> >>
> >> [1]
> https://github.com/oVirt/ovirt-engine-ui-extensions/blob/a85d47d644d5785483fc81e2eae8bdc51d559aef/src/modals/vm-export/VmExportDataProvider.js#L43
> >>
> >> On Wed, Jun 22, 2022 at 5:30 PM Gilboa Davara 
> wrote:
> >> >
> >> > Hello,
> >> >
> >> > On Wed, Jun 22, 2022 at 4:56 PM Benny Zlotnik 
> wrote:
> >> >>
> >> >> can you check the dev console for messages? (F12 in chrome/firefox)
> >> >
> >> >
> >> >  error  export problem: TypeError: o.original_template is undefined
> >> > Sa VmExportDataProvider.js:43
> >> > Sa VmExportDataProvider.js:58
> >> > onClick VmExportModal.js:45
> >> > React 9
> >> >     unstable_runWithPriority scheduler.production.min.js:20
> >> > React 3
> >> > VmExportModal.js:49:14
> >> >
> >> > - Gilboa
> >> >
> >> >>
> >> >> On Wed, Jun 22, 2022 at 4:53 PM Gilboa Davara 
> wrote:
> >> >> >
> >> >> > P.S. I have no issues exporting this VM using the deprecated
> "export domain" method.
> >> >> >
> >> >> > - Gilboa
> >> >> >
> >> >> > On Wed, Jun 22, 2022 at 4:48 PM Gilboa Davara 
> wrote:
> >> >> >>
> >> >> >> Hello,
> >> >> >>
> >> >> >> 4.4.10 Gluster based cluster w/ 3 nodes.
> >> >> >> I'm backing up all VMs before upgrading the setup to 4.5.
> (Hopefully done right before 4.5.1 w/ Gluster fix is released).
> >> >> >> When trying to export a VM to another data domain, several VMs
> show the following error: "Export VM Failed. o.original_template is
> undefined".
> >> >> >>
> >> >> >> Engine log looks clean (I see nothing about the failed upgrade).
> >> >> >>
> >> >> >> Any idea what's broken?
> >> >> >> - Gilboa
> >> >> >
> >> >> > ___
> >> >> > 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/SAGZ57R74SWS5VTLSIY74TDXB4YSBGEN/
> >> >>
> >>
>
>


16b5df4b-c3b5-4899-b5b1-336c3462494c.json
Description: application/json
___
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/QFL3EIGQLWQDRCLSXJ7HOWEPKHM3ARV2/


[ovirt-users] Re: Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
Thanks for the prompt reply.
How can I authenticate?

No matter what user / password combo I use (including the full fqdn,
user@internal-authz) I get the following error:
access_denied: Cannot authenticate user 'XXX': No valid profile found in
credentials..

- Gilboa

On Wed, Jun 22, 2022 at 5:49 PM Benny Zlotnik  wrote:

> Seems like the issue is in this line[1], can you send an API request
> manually to: https://ovirt-fqdn/ovirt-engine/api/vms/
> and check the original_template field?
> Should look like this:
>  href="/ovirt-engine/api/templates/e9dbb5c0-19b6-46ea-b80f-8813758adaa1"
> id="e9dbb5c0-19b6-46ea-b80f-8813758adaa1"/>
>
>
> [1]
> https://github.com/oVirt/ovirt-engine-ui-extensions/blob/a85d47d644d5785483fc81e2eae8bdc51d559aef/src/modals/vm-export/VmExportDataProvider.js#L43
>
> On Wed, Jun 22, 2022 at 5:30 PM Gilboa Davara  wrote:
> >
> > Hello,
> >
> > On Wed, Jun 22, 2022 at 4:56 PM Benny Zlotnik 
> wrote:
> >>
> >> can you check the dev console for messages? (F12 in chrome/firefox)
> >
> >
> >  error  export problem: TypeError: o.original_template is undefined
> > Sa VmExportDataProvider.js:43
> > Sa VmExportDataProvider.js:58
> > onClick VmExportModal.js:45
> > React 9
> > unstable_runWithPriority scheduler.production.min.js:20
> > React 3
> > VmExportModal.js:49:14
> >
> > - Gilboa
> >
> >>
> >> On Wed, Jun 22, 2022 at 4:53 PM Gilboa Davara 
> wrote:
> >> >
> >> > P.S. I have no issues exporting this VM using the deprecated "export
> domain" method.
> >> >
> >> > - Gilboa
> >> >
> >> > On Wed, Jun 22, 2022 at 4:48 PM Gilboa Davara 
> wrote:
> >> >>
> >> >> Hello,
> >> >>
> >> >> 4.4.10 Gluster based cluster w/ 3 nodes.
> >> >> I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully
> done right before 4.5.1 w/ Gluster fix is released).
> >> >> When trying to export a VM to another data domain, several VMs show
> the following error: "Export VM Failed. o.original_template is undefined".
> >> >>
> >> >> Engine log looks clean (I see nothing about the failed upgrade).
> >> >>
> >> >> Any idea what's broken?
> >> >> - Gilboa
> >> >
> >> > ___
> >> > 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/SAGZ57R74SWS5VTLSIY74TDXB4YSBGEN/
> >>
>
>
___
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/M5IWCT44GMQF6LRINY46XAO3DW6AQNGF/


[ovirt-users] Re: Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
Hello,

On Wed, Jun 22, 2022 at 4:56 PM Benny Zlotnik  wrote:

> can you check the dev console for messages? (F12 in chrome/firefox)
>

 error  export problem: TypeError: o.original_template is undefined
Sa VmExportDataProvider.js:43
Sa VmExportDataProvider.js:58
onClick VmExportModal.js:45
React 9
unstable_runWithPriority scheduler.production.min.js:20
React 3
VmExportModal.js:49:14

- Gilboa


> On Wed, Jun 22, 2022 at 4:53 PM Gilboa Davara  wrote:
> >
> > P.S. I have no issues exporting this VM using the deprecated "export
> domain" method.
> >
> > - Gilboa
> >
> > On Wed, Jun 22, 2022 at 4:48 PM Gilboa Davara  wrote:
> >>
> >> Hello,
> >>
> >> 4.4.10 Gluster based cluster w/ 3 nodes.
> >> I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully
> done right before 4.5.1 w/ Gluster fix is released).
> >> When trying to export a VM to another data domain, several VMs show the
> following error: "Export VM Failed. o.original_template is undefined".
> >>
> >> Engine log looks clean (I see nothing about the failed upgrade).
> >>
> >> Any idea what's broken?
> >> - Gilboa
> >
> > ___
> > 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/SAGZ57R74SWS5VTLSIY74TDXB4YSBGEN/
>
>
___
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/I2KABSE4BTKKNTFF5LTCD43ZKMTT7LQI/


[ovirt-users] Re: Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
P.S. I have no issues exporting this VM using the deprecated "export
domain" method.

- Gilboa

On Wed, Jun 22, 2022 at 4:48 PM Gilboa Davara  wrote:

> Hello,
>
> 4.4.10 Gluster based cluster w/ 3 nodes.
> I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully done
> right before 4.5.1 w/ Gluster fix is released).
> When trying to export a VM to another data domain, several VMs show the
> following error: "Export VM Failed. o.original_template is undefined".
>
> Engine log looks clean (I see nothing about the failed upgrade).
>
> Any idea what's broken?
> - Gilboa
>
___
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/SAGZ57R74SWS5VTLSIY74TDXB4YSBGEN/


[ovirt-users] Cannot export VM to another data domain. "o.original_template is undefined"

2022-06-22 Thread Gilboa Davara
Hello,

4.4.10 Gluster based cluster w/ 3 nodes.
I'm backing up all VMs before upgrading the setup to 4.5. (Hopefully done
right before 4.5.1 w/ Gluster fix is released).
When trying to export a VM to another data domain, several VMs show the
following error: "Export VM Failed. o.original_template is undefined".

Engine log looks clean (I see nothing about the failed upgrade).

Any idea what's broken?
- Gilboa
___
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/TDSIKM33Z7NA4UDLJ3VMEZ46VUE5YYNJ/


[ovirt-users] Re: Preferred RHEL Based Distro For oVirt

2022-06-21 Thread Gilboa Davara
On Tue, Jun 21, 2022 at 5:12 PM Neal Gompa  wrote:

> On Tue, Jun 21, 2022 at 9:58 AM Clint Boggio 
> wrote:
> >
> > Good Day All;
> >
> > i am inquiring about which RHEL based distros are currently preferred
> and which ones are currently supported. I know the oVirt project is a RH
> entity and so RHEL and CentOS-Stream are the base offering. Would it, or is
> it, feasible for Rocky 8.X, or Alma 8.X to be the base OS for an oVirt
> deployment seeing as though they both RHEL clones ?
> >
> > How confident is the user community in the stability of CentOS-Stream in
> terms of production use as compared to Alma or Rocky ?
>
> I'm pretty happy with my experience with CentOS Stream in production.
> I've been using it for the past couple of years with no issues, and
> getting fixes as they are made in the code makes it a lot easier for
> my systems to be continually improving while remaining stable.
>
> That said, I've also had decent experience with AlmaLinux as a RHEL clone.
>
> From an oVirt-specific perspective, the project is actively developing
> and testing against CentOS Stream, so you're likely to have a pretty
> good experience on it, and if there are issues, the oVirt project and
> the CentOS Virtualization SIG can respond pretty quickly to resolve
> them in the distro itself as needed.
>
>
Same as above.
Using CentOS 8 stream on multiple production (and testing) setup, ranging
from low-end single hosts test setups to large clusters.
Near-zero issues.

- Gilboa


>
>
> --
> 真実はいつも一つ!/ Always, there's only one truth!
> ___
> 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/6F6TFRTLAQXFY3Y4CQA4YEBG62A6U6IT/
>
___
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/JF4W3TTRQ7FJ55D7R4SZOMOGDGPGFTJF/


[ovirt-users] Re: 4.4.10 -> 4.5 upgrade on gluster based setups

2022-06-14 Thread Gilboa Davara
On Tue, Jun 14, 2022 at 12:36 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno mar 14 giu 2022 alle ore 11:29 Gilboa Davara 
> ha scritto:
>
>> Hello all,
>>
>> I've more or less finished upgrading all my "small" oVirt setups (single
>> hosts, multiple hosts + NFS, etc) and I'm now ready to start upgrading my
>> main production setups. (All using 3 x nodes / gluster setup).
>> A couple of questions:
>> 1. Should I use the normal sequence, as in: engine, hosts, hosts, hosts?
>>
>
> Yes
>
>
>> 2. Was the gluster bug below still open in the latest oVirt 4.5 release?
>>
>> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4LGBUOEBV7YNESM7N2TJSXOC4ERN3W23/
>>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2078569 is fixed in upcoming
> 4.5.1,
> https://lists.ovirt.org/archives/list/annou...@ovirt.org/thread/73TLVS6E77SDZL3JEJBI765W67VXRSBD/
> We are expecting to release early next week if nothing critical shows up
> from 4.5.1 RC testing.
>
>
Many thanks!

- Gilboa


>
>
>>
>> Thanks,
>> Gilboa
>> ___
>> 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/K5OLDQ7KEX7DCGMFOB6KNOTXMGSEJ2QN/
>>
>
>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA <https://www.redhat.com/>
>
> sbona...@redhat.com
> <https://www.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/A3RWSHYAXWHJJZPKU5WPUAXKUABDZ7D2/


[ovirt-users] 4.4.10 -> 4.5 upgrade on gluster based setups

2022-06-14 Thread Gilboa Davara
Hello all,

I've more or less finished upgrading all my "small" oVirt setups (single
hosts, multiple hosts + NFS, etc) and I'm now ready to start upgrading my
main production setups. (All using 3 x nodes / gluster setup).
A couple of questions:
1. Should I use the normal sequence, as in: engine, hosts, hosts, hosts?
2. Was the gluster bug below still open in the latest oVirt 4.5 release?
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/4LGBUOEBV7YNESM7N2TJSXOC4ERN3W23/

Thanks,
Gilboa
___
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/K5OLDQ7KEX7DCGMFOB6KNOTXMGSEJ2QN/


[ovirt-users] Re: Local Disk Usage

2022-05-26 Thread Gilboa Davara
Hello,

On Sat, May 21, 2022 at 9:01 AM mert tuncsav 
wrote:
>
>
> Hello All,
>
> We have performance issues about i/o for some system on oVirt. Disk type
is a nfs for shared datacenter. We need to use local disk as a secondary
data-domain to deploy vm in shared datacenter. Is there a any chance
configure that ? We couldn't find any solutions. Do you have suggestions
about it ?
>
> Regards

As far as I know, you can either export the full device (via host-devices /
scsi) or use NFS.
We usually use NFS (performance is near native when using loopback).

- Gilboa

>
>
> ___
> 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/VQIK7W5YJGZX6Z2GXQLUBX3TAJHJLDFD/
___
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/2FECIBPTASIH5OFL2INPMHY6UAKJLB2H/


[ovirt-users] Re: How can I set the host to maintenance mode?

2022-05-12 Thread Gilboa Davara
On Thu, May 12, 2022 at 12:14 PM  wrote:

> Set the maintenance mode on the host and add GPU on a single cluster host
>

> Error performing operation: unable to switch the host to maintenance mode.
>
> There is no host that can run the engine virtual machine.
>
> How can I set the host to maintenance mode?
>


You cannot use the WebUI to get a single host into maintenance mode.
What you can do is put the cluster in global maintenance mode, and shut
down the hosted-engine.

>From the host:
$ hosted-engine --set-maintenance --mode=global
$ hosted-engine --vm-shutdown

When you are done:
$ hosted-engine --set-maintenance --mode=none
$ hosted-engine --vm-startup

- Gilboa


> ___
> 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/LPMWMUDZ2QISC4COFTQLAHZPKG2J423Q/
>
___
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/KTN5VXNVHERSKJBVP3ZDY72IC23W37VT/


[ovirt-users] Re: AMD Ryzen 5600G unsupported?

2022-04-25 Thread Gilboa Davara
On Mon, Apr 25, 2022 at 12:17 PM  wrote:

> Please remember to enable tha AMD-V support in the bios, every time you
> upgrade bios they normally reset to "disabled".
> You can find this issue when in logs appears something like:
>

> Apr 20 11:45:11 ovirt-node3 journal[2011]: Unable to open /dev/kvm: No
> such file or directory
>
> to resolve remember to launch the command:
> virt-host-validate
> it checks the host environment to verify qemu support
>

I would add that if AMD-SVM is disabled, you should see "KVM is disabled in
the BIOS" message in the kernel log. (This is what I saw before the reset).

- Gilboa


>
> ___
> 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/WRBSFTMFYUEW3URJUOXFOTAZJY7YO2DV/
>
___
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/FJRY7ZD62MAEYQHCOG44JMQMSZFABNWK/


[ovirt-users] Re: AMD Ryzen 5600G unsupported?

2022-04-25 Thread Gilboa Davara
... Thanks.

Same here. Worked in the end following a BIOS reset.

- Gilboa

On Mon, Apr 25, 2022 at 10:30 AM  wrote:

> In my system is correctly recognized:
> Manufacturer:
> Gigabyte Technology Co., Ltd.
> Family:
> B550 MB
> Product Name:
> B550 AORUS ELITE V2
> Version:
> Default string
> UUID:
> 03C00218-044D-05AE-3406-0D0700080009
> Serial Number:
> Default string
> CPU Model Name:
> AMD Ryzen 7 5700G with Radeon Graphics
> Tipo CPU:
> Secure AMD EPYC
> CPU Sockets:
> 1
> CPU Cores per Socket:
> 8
> CPU Threads per Core:
> 2 (SMT Abilitato)
> TSC Frequency:
> 3819092000 (scaling enabled)
>
>
> (ovirt-engine: 4.5.0.4-1.el8, ovirt-node: 4.5.0)
> ___
> 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/NN7QLJJ6ZGQAHYQBKIQWVYDKW7GOGSEK/
>
___
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/GZS7X6OVZIO7ZSEOITOUBJCBGXQZ26C6/


[ovirt-users] Re: AMD Ryzen 5600G unsupported?

2022-04-24 Thread Gilboa Davara
Hello,

Seems to be related to broken BIOS defaults.
Cleared the BIOS, reconfigured the board, and the host now joins the
cluster without a problem.

- Gilboa

On Wed, Apr 20, 2022 at 8:45 PM Gilboa Davara  wrote:

> Hello all,
>
> I'm building adding a Ryzen 5 5600G workstation to an existing AMD
> Threadripper cluster (The existing machine use the 3960X CPU) and the
> cluster rejects the new host as it fails to recognize the host CPU as
> either "Secure AMD Epyc" or "AMD Epyc".
> All hosts are using a fully updated CentOS 8 Streams.
> I assume the 5XXX family has yet to be supported by oVirt.
>
> Can I somehow force oVirt / HE to recognize the new host?
>
> - Gilboa
>
>
___
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/EWQAD233XVUGY4WFYVITMDQ2HDC5PQ5G/


[ovirt-users] AMD Ryzen 5600G unsupported?

2022-04-20 Thread Gilboa Davara
Hello all,

I'm building adding a Ryzen 5 5600G workstation to an existing AMD
Threadripper cluster (The existing machine use the 3960X CPU) and the
cluster rejects the new host as it fails to recognize the host CPU as
either "Secure AMD Epyc" or "AMD Epyc".
All hosts are using a fully updated CentOS 8 Streams.
I assume the 5XXX family has yet to be supported by oVirt.

Can I somehow force oVirt / HE to recognize the new host?

- Gilboa
___
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/UVUURUEJDQPWQIGHXTNDQFVHI7H452PA/


[ovirt-users] Re: The connection between the Engine and the hosts has been broken

2022-03-20 Thread Gilboa Davara
Hello,

On Sun, Mar 20, 2022 at 8:42 AM Mikhail Po  wrote:

> In the very beginning it was incorrect. The hosts are not actually in the
> "NonResponsive" state, but in the "Unassigned" state.


I had a similar situation and ended up manually replacing the host's
certificates (See ML link below), which more or less got everything working
again (virt-viewer didn't work).
Alternatively, if you have a recent backup, you can simply redeploy the HE.

- Gilboa


>
> ___
> 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/EHDOHN576GZJ5CEUC6X75IUCXOL2ZD3H/
>
___
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/7D6ONGAO6VEGFM2KORYWXNXUHYMR2ENK/


[ovirt-users] Re: The connection between the Engine and the hosts has been broken

2022-03-19 Thread Gilboa Davara
Hello,

On Sat, Mar 19, 2022 at 6:51 PM  wrote:

> The connection between the Engine and the hosts has been broken. On the
> Engine side, all hosts are in the "NonResponsive" state, and on the hosts
> "ERROR ssl handshake".
> oVirt 4.4.4.7-1.el8
>

Your certificates have expired. I had the same issue on multiple setups
(single machine, gluster cluster, etc).
You'll need to renew the certificates on the hosted engine  (From the
hosted engine using engine-setup --offline).
Once the hosted engine certificates gets renewed, depending on how
lucky you are, you may be able to enrol new certificates (via installation
-> enrol certificates) and you may be less lucky (like I was on two
different setups) and you'll need to renew and copy the certificates by
hand (1).

- Gilboa
(1)
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/YCGZS2EFS2VH2SSS2OTZHJT2J7HOFTL3/#2GAQH44QD6KTS4RHXQBDWL6PNI6OKCS3



> ___
> 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/5HAEPFAFODRMW4MYHYFYZTUVW7R2EWH7/
>
___
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/HGDJOW2LV7XHAZRUYC267SP3XF27SZVZ/


[ovirt-users] Re: mdadm vs. JBOD

2022-03-19 Thread Gilboa Davara
On Tue, Mar 15, 2022 at 7:43 AM Jonas Liechti  wrote:

> Thank you for the confirmation Strahil!
>
> As our current environment is more or less the same (except the Hardware
> RAID, which is not possible with NVMe disks), we planned to use Gluster. I
> guess we will proceed as we originally planned as we are satisfied with the
> performance.
>
Sorry for being late to the party.

Two items to consider:
A. If you have more than two drives, consider using MDRAID 10 on NVME drives
We have been using it for a while now and getting *very* good performance
(more or less in-line with a single NVME drive).
As an added bonus, we managed to survive a single drive failure without
fault.
B .If possible use a 40GbE network between the nodes instead of using
10GbE. It makes a huge impact. (SSDs or even a large HDD array can
easily saturate a single 10GbE link).

- Gilboa



> On 3/11/22 07:08, Strahil Nikolov via Users wrote:
>
> Red Hat Gluster Storage is discontinued, but the Gluster (upstream) is
> pretty active and as Sandro Bonazzola (RH) confirmed -> there are no plans
> to remove support for Gluster.
> I think it's still a good choice, especially if you don't have SAN/
> Higly-Available NFS.
>
> Also, storage migration is transparent for the VMs, so you can add SAN on
> a later stage and move all VMs from Gluster to SAN without disruption* .
>
> Keep in mind that Gluster is a tier2 storage and if you really need a lot
> of IOPS, CEPH might be suitable.
>
>
> Best Regards,
> Strahil Nikolov
>
> *: Note that this is valid if the FUSE client is used. Other oVirt users
> report huge performance increase when using libgfapi interface, but it has
> drawbacks like storage migration can happen only when you switch off
> libgfapi, power off the VM (on a scheduled basis), power on the VM, live
> migrate the VM to other storage type, enable libgfapi again for the rest of
> the VMs.
>
>
>
> Thanks to Nikolov and Strahil for the valuable input! I was off for a few
> weeks, so I would like to apologize if I'm potentially reviving a zombie
> thread.
>
> I am a bit confused about where to go with this environment after the
> discontinuation of the hyperconverged setup. What alternative options are
> there for us? Or do you think going the Gluster way would still be
> advisable, even though it seems as it is being discontinued over time?
>
> Thanks for any input on this!
>
> Best regards,
> Jonas
> On 1/22/22 14:31, Strahil Nikolov via Users wrote:
>
> Using the wizzard is utilizing the Gluster Andible roles.
> I would highly recommend using it, unless you know what you are doing (for
> example storage alignment when using Hardware raid).
>
> Keep in mind that the DHT xlator (the logic in distributed volumes) is
> shard aware, so your shards are spread between subvolumes and additional
> performance can be gained.So using replicated-distributed volumes have
> their benefits.
>
> If you decide to avoid the software raid, use only replica3 volumes as
> with SSDs/NVMEs usually the failures are not physical, but logical (maximum
> writes reached -> predictive failure -> total failure).
>
> Also, consider mounting via noatime/relatime and
> context="system_u:object_r:glusterd_brick_t:s0" for your gluster bricks.
>
> Best Regards,
> Strahil Nikolov
>
> On Fri, Jan 21, 2022 at 11:00, Gilboa Davara
>   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/U2ZEWLRF5D6FENQEI5QXL77CMWB7XF32/
>
> ___
> 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/26AHNDSOJSIVTGYOEUFOY444YYBZCAIW/
>
> ___
> 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/JFFS2T25TIIHFEQMS2Y3BU4DARSIDE3U/
>
___
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/DWLJDJ5VO2CV6DNYLMVOWSUXKCQQLPUW/


[ovirt-users] Re: OVIRT INSTALLATION IN SAS RAID

2022-03-17 Thread Gilboa Davara
Hello,

On Wed, Mar 16, 2022 at 11:18 PM Strahil Nikolov via Users 
wrote:

> Check the perl script from https://forums.centos.org/viewtopic.php?t=73634
>
> According to http://elrepo.org/tiki/DeviceIDs you should run "lspci -n |
> grep '03:00.0' " and then search for the vendor:device ID pair .
>
>
> http://elrepoproject.blogspot.com/2019/08/rhel-80-and-support-for-removed-adapters.html?m=1
> there are instructions (and link to video) about dud and how to use it.
> A link to the dud images: https://elrepo.org/linux/dud/el8/x86_64/
>
> As previously mentioned you might need
> https://elrepo.org/linux/dud/el8/x86_64/dd-megaraid_sas-07.717.02.00-1.el8_5.elrepo.iso
>
>
>
> Best Regards,
> Strahil Nikolov
>

In my case the DUD files didn't work (due to kernel version mismatch) on a
couple of R710 (megaraid) and Generic-Intel-Xeon (isci SATA).
As such, I use the manual path:
- On a machine (or VM) running the latest CentOS 8 kernel:
* Download the relevant DUD source RPMs (
https://elrepo.org/linux/elrepo/el8/SRPMS/) and unpack them. (E.g.
https://elrepo.org/linux/elrepo/el8/SRPMS/kmod-megaraid_sas-07.717.02.00-1.el8_5.elrepo.src.rpm
)
* From the module directory, manually build the missing kernel drivers by
hand. (if you don't know what to do, follow the commands in the %build
segment in the DUD spec file) and save the resulting .ko kernel modules
(E.g. megaraid_sas.ko, isci.ko, etc).
- Start the machine(s) using the CentOS8 stream installation USB. Wait for
the first screen but *don't* do anything.
- Switch to a console (Ctrl-Alt-F1).
- Start the network and scp the newly built kernel modules into
/lib/modules/$(uname -r)/extra
- Load the newly copied kernel module using insmod. (E.g. insmod
/lib/modules/$(uname -r)/extra/megaraid_sas.ko)
- Check the kernel log (via dmesg) and make sure the storage controller has
initialized correctly.
- Switch back to the anaconda installer (Ctrl-Alt-F6 or F7).
- Continue installation as usual. *
(* I think I had to manually copy the kernel module to the newly installed
machine, and dracut -f to get it included in the initramfs image, but I'm
not certain).

- Gilboa
___
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/G42PQAK7V34TWOTGCSMXTZYRFMM26AVU/


[ovirt-users] Re: [ANN] Schedule for oVirt 4.5.0

2022-02-25 Thread Gilboa Davara
On Thu, Feb 24, 2022 at 8:51 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno mer 23 feb 2022 alle ore 19:23 Gilboa Davara 
> ha scritto:
>
>> On Wed, Feb 23, 2022 at 12:46 PM Sandro Bonazzola 
>> wrote:
>>
>>> Il giorno mer 23 feb 2022 alle ore 11:36 Gilboa Davara
>>>  ha scritto:
>>> >
>>> > Hello,
>>> >
>>> > Gluster is still mentioned in the release page.
>>> > Will it be supported as a storage backend in 4.5?
>>>
>>>
>>> As RHGS is going end of life in 2024 it is being deprecated for RHV.
>>> The upstream Gluster project has no plan for going end of life as far
>>> as I know so there is no reason to remove the possibility of using
>>> gluster as storage backend in oVirt.
>>> There's no plan to completely remove support for Gluster as a storage
>>> backend.
>>>
>>
>> Manys thanks for the prompt response.
>> Does it include hosted engine storage domain support (read: hosted-engine
>> --deploy support)?
>>
>
> Yes, no plan to remove the code for handling gluster on hosted-engine
> --deploy.
>

Good to hear. Thanks.

- Gilboa


>
>
>
>>
>> - Gilboa
>>
>>
>>>
>>> >
>>> >
>>> > - Gilboa
>>> >
>>> >
>>> > On Tue, Feb 22, 2022 at 4:57 PM Sandro Bonazzola 
>>> wrote:
>>> >>
>>> >> The oVirt development team leads are pleased to inform that the
>>> >> schedule for oVirt 4.5.0 has been finalized.
>>> >>
>>> >> The key dates follows:
>>> >>
>>> >> * Feature Freeze - String Freeze - Alpha release: 2022-03-15
>>> >> * Alpha release test day: 2022-03-17
>>> >> * Code freeze - Beta release: 2022-03-29
>>> >> * Beta release test day: 2022-03-31
>>> >> * General Availability release: 2022-04-12
>>> >>
>>> >> A release management draft page has been created at:
>>> >> https://www.ovirt.org/release/4.5.0/
>>> >>
>>> >> If you're willing to help testing the release during the test days
>>> >> please join the oVirt development mailing list at
>>> >> https://lists.ovirt.org/archives/list/de...@ovirt.org/ and report
>>> your
>>> >> feedback there.
>>> >> Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for
>>> >> testing will be added to the release page
>>> >> https://www.ovirt.org/release/4.5.0/ when the corresponding version
>>> >> will be released.
>>> >>
>>> >> Professional Services, Integrators and Backup vendors: please plan a
>>> >> test session against your additional services, integrated solutions,
>>> >> downstream rebuilds, backup solution accordingly.
>>> >> If you're not listed here:
>>> >> https://ovirt.org/community/user-stories/users-and-providers.html
>>> >> consider adding your company there.
>>> >>
>>> >> If you're willing to help updating the localization for oVirt 4.5.0
>>> >> please follow https://ovirt.org/develop/localization.html
>>> >>
>>> >> If you're willing to help promoting the oVirt 4.5.0 release you can
>>> >> submit your banner proposals for the oVirt home page and for the
>>> >> social media advertising at
>>> https://github.com/oVirt/ovirt-site/issues
>>> >> As an alternative please consider submitting a case study as in
>>> >> https://ovirt.org/community/user-stories/user-stories.html
>>> >>
>>> >> Feature owners: please start planning a presentation of your feature
>>> >> for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject
>>> >>
>>> >> Do you want to contribute to getting ready for this release?
>>> >> Read more about oVirt community at https://ovirt.org/community/ and
>>> >> join the oVirt developers https://ovirt.org/develop/
>>> >>
>>> >> Thanks,
>>> >> --
>>> >>
>>> >> 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.
>>> >> __

[ovirt-users] Re: [ANN] Schedule for oVirt 4.5.0

2022-02-23 Thread Gilboa Davara
On Wed, Feb 23, 2022 at 12:46 PM Sandro Bonazzola 
wrote:

> Il giorno mer 23 feb 2022 alle ore 11:36 Gilboa Davara
>  ha scritto:
> >
> > Hello,
> >
> > Gluster is still mentioned in the release page.
> > Will it be supported as a storage backend in 4.5?
>
>
> As RHGS is going end of life in 2024 it is being deprecated for RHV.
> The upstream Gluster project has no plan for going end of life as far
> as I know so there is no reason to remove the possibility of using
> gluster as storage backend in oVirt.
> There's no plan to completely remove support for Gluster as a storage
> backend.
>

Manys thanks for the prompt response.
Does it include hosted engine storage domain support (read: hosted-engine
--deploy support)?

- Gilboa


>
> >
> >
> > - Gilboa
> >
> >
> > On Tue, Feb 22, 2022 at 4:57 PM Sandro Bonazzola 
> wrote:
> >>
> >> The oVirt development team leads are pleased to inform that the
> >> schedule for oVirt 4.5.0 has been finalized.
> >>
> >> The key dates follows:
> >>
> >> * Feature Freeze - String Freeze - Alpha release: 2022-03-15
> >> * Alpha release test day: 2022-03-17
> >> * Code freeze - Beta release: 2022-03-29
> >> * Beta release test day: 2022-03-31
> >> * General Availability release: 2022-04-12
> >>
> >> A release management draft page has been created at:
> >> https://www.ovirt.org/release/4.5.0/
> >>
> >> If you're willing to help testing the release during the test days
> >> please join the oVirt development mailing list at
> >> https://lists.ovirt.org/archives/list/de...@ovirt.org/ and report your
> >> feedback there.
> >> Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for
> >> testing will be added to the release page
> >> https://www.ovirt.org/release/4.5.0/ when the corresponding version
> >> will be released.
> >>
> >> Professional Services, Integrators and Backup vendors: please plan a
> >> test session against your additional services, integrated solutions,
> >> downstream rebuilds, backup solution accordingly.
> >> If you're not listed here:
> >> https://ovirt.org/community/user-stories/users-and-providers.html
> >> consider adding your company there.
> >>
> >> If you're willing to help updating the localization for oVirt 4.5.0
> >> please follow https://ovirt.org/develop/localization.html
> >>
> >> If you're willing to help promoting the oVirt 4.5.0 release you can
> >> submit your banner proposals for the oVirt home page and for the
> >> social media advertising at https://github.com/oVirt/ovirt-site/issues
> >> As an alternative please consider submitting a case study as in
> >> https://ovirt.org/community/user-stories/user-stories.html
> >>
> >> Feature owners: please start planning a presentation of your feature
> >> for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject
> >>
> >> Do you want to contribute to getting ready for this release?
> >> Read more about oVirt community at https://ovirt.org/community/ and
> >> join the oVirt developers https://ovirt.org/develop/
> >>
> >> Thanks,
> >> --
> >>
> >> 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/7646LEQIHL76HIJTAZWCXWAHT3M6V47C/
>
>
>
> --
>
> 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/AF5TNUS3B4IY666QLXCS6242OLKU/


[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED

2022-02-23 Thread Gilboa Davara
On Mon, Feb 21, 2022 at 12:07 PM Strahil Nikolov 
wrote:

> You can blacklist packages in dnf with specific version, and thus you
> don't need to blacklist from repo.
>
> Best Regards,
> Strahil Nikolov
>
>
Hello,

Understood.
Perr your qemu 6.2 question, how can I test it? Is it packaged in some
testing repo?

- Gilboa


> On Mon, Feb 21, 2022 at 10:33, Gilboa Davara
>  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/SJZNIGOZXWC44RMUGO73BO5BIWFGELHT/
>
>
___
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/ZF3X276Y2WS34RVF7DZ3FLH5UCYUBDZN/


[ovirt-users] Re: [ANN] Schedule for oVirt 4.5.0

2022-02-23 Thread Gilboa Davara
Hello,

Gluster is still mentioned in the release page.
Will it be supported as a storage backend in 4.5?

- Gilboa


On Tue, Feb 22, 2022 at 4:57 PM Sandro Bonazzola 
wrote:

> The oVirt development team leads are pleased to inform that the
> schedule for oVirt 4.5.0 has been finalized.
>
> The key dates follows:
>
> * Feature Freeze - String Freeze - Alpha release: 2022-03-15
> * Alpha release test day: 2022-03-17
> * Code freeze - Beta release: 2022-03-29
> * Beta release test day: 2022-03-31
> * General Availability release: 2022-04-12
>
> A release management draft page has been created at:
> https://www.ovirt.org/release/4.5.0/
>
> If you're willing to help testing the release during the test days
> please join the oVirt development mailing list at
> https://lists.ovirt.org/archives/list/de...@ovirt.org/ and report your
> feedback there.
> Instructions for installing oVirt 4.5.0 Alpha and oVirt 4.5.0 Beta for
> testing will be added to the release page
> https://www.ovirt.org/release/4.5.0/ when the corresponding version
> will be released.
>
> Professional Services, Integrators and Backup vendors: please plan a
> test session against your additional services, integrated solutions,
> downstream rebuilds, backup solution accordingly.
> If you're not listed here:
> https://ovirt.org/community/user-stories/users-and-providers.html
> consider adding your company there.
>
> If you're willing to help updating the localization for oVirt 4.5.0
> please follow https://ovirt.org/develop/localization.html
>
> If you're willing to help promoting the oVirt 4.5.0 release you can
> submit your banner proposals for the oVirt home page and for the
> social media advertising at https://github.com/oVirt/ovirt-site/issues
> As an alternative please consider submitting a case study as in
> https://ovirt.org/community/user-stories/user-stories.html
>
> Feature owners: please start planning a presentation of your feature
> for oVirt Youtube channel: https://www.youtube.com/c/ovirtproject
>
> Do you want to contribute to getting ready for this release?
> Read more about oVirt community at https://ovirt.org/community/ and
> join the oVirt developers https://ovirt.org/develop/
>
> Thanks,
> --
>
> 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/7646LEQIHL76HIJTAZWCXWAHT3M6V47C/
>
___
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/XOUR7ME5EGYPJKL6YK3QEBX2AOLGCREP/


[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED

2022-02-21 Thread Gilboa Davara
Hello,

I somehow missed your reply (and was AFK nearly two weeks).
How can I test qemu 6.2? Is it available in some repo?

- Gilboa

On Thu, Feb 10, 2022 at 4:31 PM Strahil Nikolov 
wrote:

> I ment blacklisting only the broken qemu packages .
> Something like:
> exclude=qemu*6.1.0-4.module_el8.6.0+983+a7505f3f.x86_64
>
> or even more explicit -> full package names qith version & arch
>
> New packages would not match the filter.
>
>
> By the way, did anyone check qemu 6.2.0 ?
>
>
> Best Regards,
> Strahil Nikolov
>
> On Thu, Feb 10, 2022 at 6:15, Gilboa Davara
>  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/WYUFB55GKFXI7UDTHZLEZNFYVDVQEEDW/
>
>
___
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/SJZNIGOZXWC44RMUGO73BO5BIWFGELHT/


[ovirt-users] Re: dnf update fails with oVirt 4.4 on centos 8 stream due to ansible package conflicts.

2022-02-20 Thread Gilboa Davara
I managed to upgrade a couple of 8-streams based clusters w/ --nobest, and
thus far, I've yet to experience any issues (knocks wood feaviously).

- Gilboa

On Sat, Feb 19, 2022 at 3:21 PM Daniel McCoshen 
wrote:

> Hey all,
> I'm running ovirt 4.4 in production (4.4.5-11-1.el8), and I'm attempting
> to update the OS on my hosts. The hosts are all centos 8 stream, and dnf
> update is failing on all of them with the following output:
>
> [root@ovirthost ~]# dnf update
> Last metadata expiration check: 1:36:32 ago on Thu 17 Feb 2022 12:01:25 PM
> CST.
> Error:
>  Problem: package cockpit-ovirt-dashboard-0.15.1-1.el8.noarch requires
> ansible, but none of the providers can be installed
>   - package ansible-2.9.27-2.el8.noarch conflicts with ansible-core >
> 2.11.0 provided by ansible-core-2.12.2-2.el8.x86_64
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.27-2.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.27-1.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.17-1.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.18-2.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.20-2.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.21-2.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.23-2.el8.noarch
>   - package ansible-core-2.12.2-2.el8.x86_64 obsoletes ansible < 2.10.0
> provided by ansible-2.9.24-2.el8.noarch
>   - cannot install the best update candidate for package
> cockpit-ovirt-dashboard-0.15.1-1.el8.noarch
>   - cannot install the best update candidate for package
> ansible-2.9.27-2.el8.noarch
>   - package ansible-2.9.20-1.el8.noarch is filtered out by exclude
> filtering
>   - package ansible-2.9.16-1.el8.noarch is filtered out by exclude
> filtering
>   - package ansible-2.9.19-1.el8.noarch is filtered out by exclude
> filtering
>   - package ansible-2.9.23-1.el8.noarch is filtered out by exclude
> filtering
> (try to add '--allowerasing' to command line to replace conflicting
> packages or '--skip-broken' to skip uninstallable packages or '--nobest' to
> use not only best candidate packages)
>
> cockpit-ovirt-dashboard.noarch is at 0.15.1-1.el8, and it looks like that
> conflicting ansible-core package was added to the 8-stream repo two days
> ago. That's when I first noticed the issue, but I it might be older. When
> the eariler issues with the centos 8 deprecation happened, I had swapped
> out the repos on some of these hosts for the new ones, and have since added
> new hosts as well, using the updated repos. Both hosts that had been moved
> from the old repos, and ones created with the new repos are experienceing
> this issue.
>
> ansible-core is being pulled from the centos 8 stream AppStream repo, and
> the ansible package that cockpit-ovirt-dashboard.noarch is trying to use as
> a dependency is comming from ovirt-4.4-centos-ovirt44
>
> I'm tempted to blacklist ansible-core in my dnf conf, but that seems like
> a hacky work-around and not the actual fix here.
> Thanks,
> Dan
> ___
> 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/3N4ZO6LXNOQNQU5HHDGNOZHDSO4IBGFF/
>
___
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/YJ336275NTG4M4AUOBTJNBZ3RD2L6HXA/


[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED

2022-02-09 Thread Gilboa Davara
On Wed, Feb 9, 2022, 21:33 Nir Soffer  wrote:

> On Wed, Feb 9, 2022 at 5:06 PM Gilboa Davara  wrote:
> >
> >
> > On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer  wrote:
> >>
> >> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara 
> wrote:
> >> >
> >> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov 
> wrote:
> >> >>
> >> >> Or just add an exclude in /etc/dnf/dnf.conf
> >> >
> >> >
> >> > I personally added and exclusion to
> /etc/yum.repos.d/CentOS-Stream-AppStream.repo
> >> > exclude=qemu*
> >> > It allows ovirt-4.4* repos to push a new qemu release, without
> letting CentOS stream break things...
> >>
> >> But new libvirt versions may require a newer qemu version, and oVirt
> itself
> >> may require a new libvirt version.
> >>
> >> These kind of excludes are fragile and need constant maintenance.
> >>
> >> Nir
> >
> >
> > The previous poster proposed a global qemu exclusion.
> > I propose a partial qemu exclusion (on centos-streams only), with the
> assumption that ovirt-required qemu will be pushed directly via the ovirt
> repo.
> > In both cases, this is a temporary measure needed to avoid using the
> broken qemu pushed by streams.
> > In both cases libvirt update from appstreams will get blocked - assuming
> it requires the broken qemu release.
> >
> > Do you advise we simply --exclude=qemu* everything we run dnf? I would
> imagine it's far more dangerous and will block libvirt update just as well.
>
> I don't have a better solution, I just wanted to warn about these excludes.
>
> Nir
>

Ok, understood,  thanks.

Gilboa

>
___
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/WYUFB55GKFXI7UDTHZLEZNFYVDVQEEDW/


[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED

2022-02-09 Thread Gilboa Davara
On Wed, Feb 9, 2022 at 3:35 PM Nir Soffer  wrote:

> On Wed, Feb 9, 2022 at 12:47 PM Gilboa Davara  wrote:
> >
> > On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov 
> wrote:
> >>
> >> Or just add an exclude in /etc/dnf/dnf.conf
> >
> >
> > I personally added and exclusion to
> /etc/yum.repos.d/CentOS-Stream-AppStream.repo
> > exclude=qemu*
> > It allows ovirt-4.4* repos to push a new qemu release, without letting
> CentOS stream break things...
>
> But new libvirt versions may require a newer qemu version, and oVirt itself
> may require a new libvirt version.
>
> These kind of excludes are fragile and need constant maintenance.
>
> Nir
>

The previous poster proposed a global qemu exclusion.
I propose a partial qemu exclusion (on centos-streams only), with the
assumption that ovirt-required qemu will be pushed directly via the ovirt
repo.
In both cases, this is a temporary measure needed to avoid using the broken
qemu pushed by streams.
In both cases libvirt update from appstreams will get blocked - assuming it
requires the broken qemu release.

Do you advise we simply --exclude=qemu* everything we run dnf? I would
imagine it's far more dangerous and will block libvirt update just as well.

... Unless I'm missing something?
- Gilboa
___
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/F7XJJERVVZY2NC5BR7Y46KJUQFHANWRB/


[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED

2022-02-09 Thread Gilboa Davara
On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov 
wrote:

> Or just add an exclude in /etc/dnf/dnf.conf


I personally added and exclusion to
/etc/yum.repos.d/CentOS-Stream-AppStream.repo
exclude=qemu*
It allows ovirt-4.4* repos to push a new qemu release, without letting
CentOS stream break things...

- Gilboa



>
> On Tue, Feb 8, 2022 at 18:32, Gilboa Davara
>  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/AMWN33K6BELU6VXBGVMTUEDHR2YKTIC5/
>
>
___
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/J4IMOXBMP3NFOK6FLV3OISA76TEUA5DG/


[ovirt-users] Post SSL certificate expiration recovery, openvswitch certificates are still expired. Bug?

2022-02-09 Thread Gilboa Davara
Hello all,

Seems the engine-setup fails to update the openvswitch certificate on the
HE itself.

$ openssl x509 -in /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer
-noout -dates
notBefore=Dec 26 16:25:04 2020 GMT
notAfter=Jan 29 16:25:04 2022 GMT
$ engine-setup

[ INFO  ] Stage: Termination
[ INFO  ] Execution of setup completed successfully
$ openssl x509 -in /etc/pki/ovirt-engine/certs/ovirt-provider-ovn.cer
-noout -dates
notBefore=Dec 26 16:25:04 2020 GMT
notAfter=Jan 29 16:25:04 2022 GMT

$ cat /var/log/messages | grep ovsdb-server
...
Feb  9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22660|jsonrpc|WARN|ssl:[:::192.168.2.22]:57924: receive err
or: Protocol error
Feb  9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22661|reconnect|WARN|ssl:[:::192.168.2.22]:57924: connectio
n dropped (Protocol error)
Feb  9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22662|stream_ssl|WARN|SSL_accept: error:14094415:SSL routines:s
sl3_read_bytes:sslv3 alert certificate expired
Feb  9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22663|jsonrpc|WARN|ssl:[:::192.168.2.22]:57928: receive err
or: Protocol error
Feb  9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22664|reconnect|WARN|ssl:[:::192.168.2.22]:57928: connection
dropped (Protocol error)

@RH people. Is it a bug?

- Gilboa
___
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/4WAWTWLTTQYTOQPNL4CQKZJGZY3T7KQH/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-09 Thread Gilboa Davara
On Wed, Feb 9, 2022 at 9:20 AM Gilboa Davara  wrote:

>
>
> On Wed, Feb 9, 2022 at 7:52 AM Patrick Hibbs 
> wrote:
>
>> The certificates used in SPICE connections are stored on the VM hosts. By
>> default they are at /etc/pki/vdsm/libvirt-spice, and configured by VDSM in
>> /etc/libvirt/qemu.conf. Their default names are ca-cert.pem,
>> server-cert.pem, and server-key.pem. Using openssl x509 -noout -text -in
>>  should show you the certificate's expiration info.
>>
>> Note: Don't try to change anything, it will be overwritten by VDSM on the
>> next host update / reinstall.
>>
>> As for remote-viewer, if you run it manually from the console with
>> "remote-viewer --debug " or "remote-viewer --verbose
>> "  it will print log information about the connection
>> it's trying to establish.
>>
>> -Patrick Hibbs
>>
>>
> Hello,
>
> You must have missed my answer above. (Understandable, given the length of
> this thread...)
> I replaced and verified /etc/pki/vdsm/libvirt-spice/server-cert.pem
> Restarted all the services on the host.
>
> $ openssl x509 -in /etc/pki/vdsm/libvirt-spice/server-cert.pem -noout
> -dates
> notBefore=Feb  7 13:59:14 2022 GMT
> notAfter=Feb  7 13:59:14 2027 GMT
> $ openssl x509 -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -noout -dates
> notBefore=Dec 26 16:25:01 2020 GMT
> notAfter=Dec 25 16:25:01 2030 GMT
>
> However, remote-viewer still fails:
> $ remote-viewer --debug console.vv
> ...
> (remote-viewer:14874): Spice-WARNING **: 18:14:33.500:
> ../subprojects/spice-common/common/ssl_verify.c:506:openssl
> _verify: ssl: subject 'O=localdomain,CN=gilboa-wx-srv.localdomain'
> verification failed
>
> The main problem here is that while we assume the problem is expired
> certificates, it can be something else (Subject, CN, etc).
> The error is not informative..
>
> - Gilboa.
>
>
>
Seems that openvswitch is also using the old certificates.
Feb  9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22660|jsonrpc|WARN|ssl:[:::192.168.2.22]:57924: receive err
or: Protocol error
Feb  9 09:56:32 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22661|reconnect|WARN|ssl:[:::192.168.2.22]:57924: connectio
n dropped (Protocol error)
Feb  9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22662|stream_ssl|WARN|SSL_accept: error:14094415:SSL routines:s
sl3_read_bytes:sslv3 alert certificate expired
Feb  9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22663|jsonrpc|WARN|ssl:[:::192.168.2.22]:57928: receive err
or: Protocol error
Feb  9 09:56:40 gilboa-wx-vmsrv ovsdb-server[9874]:
ovs|22664|reconnect|WARN|ssl:[:::192.168.2.22]:57928: connection
dropped (Protocol error)

Seems that https://access.redhat.com/solutions/3532921 is missing a couple
of certificates..
(I don't even see it in
https://www.ovirt.org/develop/release-management/features/infra/pki.html).

- Gilboa


>
>
>> On Wed, 2022-02-09 at 06:58 +0200, Gilboa Davara wrote:
>>
>>
>>
>> On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov 
>> wrote:
>>
>> I have no clue , but I would give vdsm.service a restart.
>>
>>
>> Thanks again for the prompt response.
>> Tried that, restarted all services and the all the VMS, didn't work.
>>
>> Any idea how I can verify the certificate information actually being used
>> by qemu for the spice console?
>> remote-viewer just fails, without giving any meaningful error message.
>>
>> - Gilboa
>>
>>
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On Tue, Feb 8, 2022 at 18:19, Gilboa Davara
>>  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/2GAQH44QD6KTS4RHXQBDWL6PNI6OKCS3/
>>
>> ___
>> 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/OG57VT2XGDTY2MFOJFFUCZAMXS22W4OG/
>>
>>
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy 

[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-08 Thread Gilboa Davara
On Wed, Feb 9, 2022 at 7:52 AM Patrick Hibbs  wrote:

> The certificates used in SPICE connections are stored on the VM hosts. By
> default they are at /etc/pki/vdsm/libvirt-spice, and configured by VDSM in
> /etc/libvirt/qemu.conf. Their default names are ca-cert.pem,
> server-cert.pem, and server-key.pem. Using openssl x509 -noout -text -in
>  should show you the certificate's expiration info.
>
> Note: Don't try to change anything, it will be overwritten by VDSM on the
> next host update / reinstall.
>
> As for remote-viewer, if you run it manually from the console with
> "remote-viewer --debug " or "remote-viewer --verbose
> "  it will print log information about the connection
> it's trying to establish.
>
> -Patrick Hibbs
>
>
Hello,

You must have missed my answer above. (Understandable, given the length of
this thread...)
I replaced and verified /etc/pki/vdsm/libvirt-spice/server-cert.pem
Restarted all the services on the host.

$ openssl x509 -in /etc/pki/vdsm/libvirt-spice/server-cert.pem -noout
-dates
notBefore=Feb  7 13:59:14 2022 GMT
notAfter=Feb  7 13:59:14 2027 GMT
$ openssl x509 -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -noout -dates
notBefore=Dec 26 16:25:01 2020 GMT
notAfter=Dec 25 16:25:01 2030 GMT

However, remote-viewer still fails:
$ remote-viewer --debug console.vv
...
(remote-viewer:14874): Spice-WARNING **: 18:14:33.500:
../subprojects/spice-common/common/ssl_verify.c:506:openssl
_verify: ssl: subject 'O=localdomain,CN=gilboa-wx-srv.localdomain'
verification failed

The main problem here is that while we assume the problem is expired
certificates, it can be something else (Subject, CN, etc).
The error is not informative..

- Gilboa.




> On Wed, 2022-02-09 at 06:58 +0200, Gilboa Davara wrote:
>
>
>
> On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov 
> wrote:
>
> I have no clue , but I would give vdsm.service a restart.
>
>
> Thanks again for the prompt response.
> Tried that, restarted all services and the all the VMS, didn't work.
>
> Any idea how I can verify the certificate information actually being used
> by qemu for the spice console?
> remote-viewer just fails, without giving any meaningful error message.
>
> - Gilboa
>
>
>
> Best Regards,
> Strahil Nikolov
>
> On Tue, Feb 8, 2022 at 18:19, Gilboa Davara
>  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/2GAQH44QD6KTS4RHXQBDWL6PNI6OKCS3/
>
> ___
> 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/OG57VT2XGDTY2MFOJFFUCZAMXS22W4OG/
>
>
> ___
> 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/AKQVBARD4EWIS3PCQYLX7AH575XRDYAD/
>
___
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/5FFDOORY2QJ6QGWT3RNVVYE2DIVTB4KL/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-08 Thread Gilboa Davara
On Wed, Feb 9, 2022 at 1:05 AM Strahil Nikolov 
wrote:

> I have no clue , but I would give vdsm.service a restart.
>

Thanks again for the prompt response.
Tried that, restarted all services and the all the VMS, didn't work.

Any idea how I can verify the certificate information actually being used
by qemu for the spice console?
remote-viewer just fails, without giving any meaningful error message.

- Gilboa


>
> Best Regards,
> Strahil Nikolov
>
> On Tue, Feb 8, 2022 at 18:19, Gilboa Davara
>  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/2GAQH44QD6KTS4RHXQBDWL6PNI6OKCS3/
>
>
___
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/OG57VT2XGDTY2MFOJFFUCZAMXS22W4OG/


[ovirt-users] Re: hosted engine deployment (v4.4.10) - TASK Check engine VM health - fatal FAILED

2022-02-08 Thread Gilboa Davara
>
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if Engine IP is
> different from engine's he_fqdn resolved IP]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
> "Engine VM IP address is while the engine's he_fqdn
> ovirt-engine.mgmt.pss.local resolves to 10.210.1.101. If you are using
> DHCP, check your DHCP reservation configuration"}
>
>
Hello,

It's a known issue (Yesterday it took me 4 cups of coffee and ~4-5 of lost
sleep to remember this fact...)
The Latest qemu update (6.1) is broken, and fails during --deploy.
Make sure you run 'dnf downgrade qemu*' a couple of times on the first
host, until you get qemu-6.0.
Once done, try deploying again.

- Gilboa
___
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/AMWN33K6BELU6VXBGVMTUEDHR2YKTIC5/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-08 Thread Gilboa Davara
Hello,

On Tue, Feb 8, 2022 at 5:39 PM Strahil Nikolov 
wrote:

> From the web UI there is an option to to regenerate the certificate
> Compute -> Hosts -> Management -> Maintenance -> Installation -> Enroll
> certificate
>
> Also, if you have RH dev subscription , you can check
> https://access.redhat.com/solutions/3532921 for the manual approach.
>
> Best Regards,
> Strahil Nikolov
>

Thanks for the prompt response.
Sadly enough as luck would have it, it hit this issues on one of the
single-host setups - which cannot go into maintenance.
Soon after sending this email, I managed to find the RHV solution, which
got VDSM working again.
However, I cannot seem to get vmconsole working - trying to get spice
console connected still uses the old certificates, even though I replaced
and verified /etc/pki/vdsm/libvirt-spice/server-cert.pem

$ openssl x509 -in /etc/pki/vdsm/libvirt-spice/server-cert.pem -noout
-dates
notBefore=Feb  7 13:59:14 2022 GMT
notAfter=Feb  7 13:59:14 2027 GMT
$ openssl x509 -in /etc/pki/vdsm/libvirt-spice/ca-cert.pem -noout -dates
notBefore=Dec 26 16:25:01 2020 GMT
notAfter=Dec 25 16:25:01 2030 GMT
$ remote-viewer console.vv
...
(remote-viewer:14874): Spice-WARNING **: 18:14:33.500:
../subprojects/spice-common/common/ssl_verify.c:506:openssl
_verify: ssl: subject 'O=localdomain,CN=gilboa-wx-srv.localdomain'
verification failed

Any idea what I'm missing?

- Gilboa





>
> On Tue, Feb 8, 2022 at 12:13, Gilboa Davara
>  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/DQOEYXG2XNM5TFZJHNDNPPKL3OIQI4SO/
>
>
___
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/2GAQH44QD6KTS4RHXQBDWL6PNI6OKCS3/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-08 Thread Gilboa Davara
Hello,

On Mon, Feb 7, 2022 at 4:14 PM Martin Perina  wrote:

>
>> I don't know how, but the only errors I saw in the WebUI were update
>> related (failed to check updates on host).
>>
>
> That is not related to certificates errors used for engine <-> VDSM
> communication
>
> There was an error in engine-setup, but at this stage it was far, far too
>> late.
>>
>
> The warning/alerts mentioned above are stored in engine's audit log, which
> can be viewed within Events tab in webadmin, where you should see something
> like:
>
> Host ${VdsName} certification is about to expire at ${ExpirationDate}.
> Please renew the host's certification.
>
> or
>
> Engine's certification is about to expire at ${ExpirationDate}. Please
> renew the engine's certification.
>
>>
>>

Hello,

I just lost at least two more setups, while (slowly) upgrading it to
-streams.
Zero warning on the UI (verified twice).
Zero warning in the vdsm log (verified before I started the upgrade).
Once I upgraded the hosted engine to streams (engine-setup --offline,
distro sync, engine-setup), the VDSM's services stopped working on all
hosts (sadly enough, at least two setups are single host setups).
Tried restarting the VDSM service, and now they are spewing SSL handshake
errors.
E.g. ERROR ssl handshake: SSLError, address: :::127.0.0.1

So, given the fact that I have a working HE on all machines, how can I
renew the vdsm certificates?
I assume I cannot simply restart the HE service and try to enroll new
certificates?

- Gilboa
___
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/DQOEYXG2XNM5TFZJHNDNPPKL3OIQI4SO/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-07 Thread Gilboa Davara
On Mon, Feb 7, 2022 at 4:03 PM Martin Perina  wrote:

>
>
> On Mon, Feb 7, 2022 at 12:33 PM Gilboa Davara  wrote:
>
>> Hello,
>>
>> On Mon, Feb 7, 2022 at 8:45 AM Yedidyah Bar David 
>> wrote:
>>
>>> On Sun, Feb 6, 2022 at 5:09 PM Gilboa Davara  wrote:
>>> >
>>> > Unlike my predecessor, I not only lost my vmengine, I also lost the
>>> vdsm services on all hosts.
>>> > All seem to be hitting the same issue - read, the certs under
>>> /etc/pki/vdsm/certs and /etc/pki/ovirt* all expired a couple of days ago.
>>> > As such, the hosted engine cannot go into global maintenance mode,
>>>
>>> What do you mean by that? What happens if you 'hosted-engine
>>> --set-maintenance --mode=global'?
>>>
>>
>> Failed, stating the cluster is not in global maintenance mode.
>> (Understandable, given two of 3 hosts were offline due to certificate
>> issues...)
>>
>>
>>
>>>
>>> > preventing engine-setup --offline from running.
>>>
>>> Actually just a few days ago I pushed a patch for:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1700460
>>>
>>> But:
>>>
>>> If you really have a problem that you can't set global maintenance,
>>> using this is a risk - HA might intervene in the middle and shutdown
>>> the VM. So either make sure global maintenance does work, or stop
>>> all HA services on all hosts.
>>>
>>> > Two questions:
>>> > 1. Is there any automated method to renew the vdsm certificates?
>>>
>>> You mean, without an engine?
>>>
>>> I think that if you have a functional engine one way or another,
>>> you can automate this somehow, didn't check. Try checking e.g. the
>>> python sdk examples - there might be there something you can base
>>> on.
>>>
>>> > 2. Assuming the previous answer is "no", assuming I'm somewhat versed
>>> in using openssl, how can I manually renew them?
>>>
>>> I'd rather not try to invent from memory how this is supposed to work,
>>> and doing this methodically and verifying before replying is quite
>>> an effort.
>>>
>>> If this is really what you want, I suggest something like:
>>>
>>> 1. Set up a test env with an engine and one host
>>> 2. Backup (or use git on) /etc on both
>>> 3. Renew the host cert from the UI
>>> 4. Check what changed
>>>
>>> You should find, IMO, that the key(s) on the host didn't
>>> change. I guess you might also find CSRs on one or both of them.
>>> So basically it should be something like:
>>> 1. Create a CSR on the host for the existing key (one or more,
>>> not sure).
>>> 2. Copy and sign this on the engine using pki-enroll-request.sh
>>> (I think you can find examples for it scattered around, perhaps
>>> even in the main guides)
>>> 3. Copy back the generated certs to the host
>>> 4. Perhaps restart one or more services there (vdsm, imageio?,
>>> ovn, etc.)
>>>
>>> You can check the code in
>>> /usr/share/ovirt-engine/ansible-runner-service-project/project
>>> to see how it's done when initiated from the UI.
>>>
>>> Good luck and best regards,
>>>
>>
>> I more of less found a document stating the above somewhere in the middle
>> of the night.
>> Tried it.
>> Got the WebUI working again.
>> However, for the life of me I couldn't get the hosts to work to talk to
>> the engine. (Even though I could use openssl s_client -showcerts -connect
>> host and got valid certs).
>> In the end, @around ~4am, I decided to take the brute force route, clean
>> the hosts, upgrade them to -streams, and redeploy the engine again (3'rd
>> attempt, after sufficient amount of coffee reminded me the qemu-6.1 is
>> broken, and needed to be downgraded before trying to deploy the HE...).
>> Either way, when I finish importing the VMs, I'll open a RFE to add
>> BIG-WARNING-IN-BOLD-LETTERS in the WebUI to notify the admin that the
>> certificates are about to expire.
>>
>
> We already have quite a lot of warnings/alters about certificates which
> are going to expire soon:
>
>
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/TMJVAJMH5MKUVRTSZG2BB46QKXYI6M2D/
>
> So what exactly are you missing here?
>

I don't know how, but the only errors I saw in the WebUI were update
related (failed to check updates on host).
There was an error in engine-setup,

[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-07 Thread Gilboa Davara
Hello,

On Mon, Feb 7, 2022 at 2:25 PM Yedidyah Bar David  wrote:

> On Mon, Feb 7, 2022 at 1:27 PM Gilboa Davara  wrote:
> >
> > Hello,
> >
> > On Mon, Feb 7, 2022 at 8:45 AM Yedidyah Bar David 
> wrote:
> >>
> >> On Sun, Feb 6, 2022 at 5:09 PM Gilboa Davara  wrote:
> >> >
> >> > Unlike my predecessor, I not only lost my vmengine, I also lost the
> vdsm services on all hosts.
> >> > All seem to be hitting the same issue - read, the certs under
> /etc/pki/vdsm/certs and /etc/pki/ovirt* all expired a couple of days ago.
> >> > As such, the hosted engine cannot go into global maintenance mode,
> >>
> >> What do you mean by that? What happens if you 'hosted-engine
> >> --set-maintenance --mode=global'?
> >
> >
> > Failed, stating the cluster is not in global maintenance mode.
>
> Please clarify, and/or share relevant logs, if you have them.
>

Sadly enough, no.
When I zapped the old vmegine and hosts configuration, I forgot to save the
logs.
(In my defense, it was 4am...)

That said, the fix proposed in BZ#1700460 (Let the user skip the global
maintenance check) might have saved my cluster.


>
> You had a semi-working existing HE cluster.
> You ran engine-backup on it, took a backup, while it was _not_ in
> global maintenance.
>

It was rather odd.
One of the hosts was still active and running the HE engine.
After I updated the apache certs, I could connect to the WebUI, but the
WebUI failed to access the nodes, spewing SSL handshake errors.
I then processed to replace the hosts certs, which seems to work, (E.g.
vdsm-client Host getCapabilities worked), hosted-engine --vm-status worked
and I could see all 3 hosts, but the engine failed to communicate with the
hosts, hence, even though I had a working cluster and engine, and I could
get the cluster into global maintenance mode, engine-setup --offline
continued to spew "not-in-global-maintenance-mode' errors.
At this stage I decided to simply zap the hosted engine and
ovirt-hosted-engine-cleanup the hosts.

As my brain was half dead, I decided to do a fresh deployment, and not use
the daily backup.



> That's ok and expected.
>
> Then you took one of the hosts and evacuated it (or just a new one),
> (re)installed the OS (or somehow cleaned it up), and ran
> 'hosted-engine --deploy --import-from-file' with the backup you took.
> This failed? Where exactly and with what error?
>

Didn't use the backup.
Clean hosted-engine --deploy failed due to qemu-6.1 failure. (I believe
it's a known BZ#).
Once I remembered to downgrade it to 6.0, everything worked as advertised
(minus one export domain, see another email).


>
> If it's the engine-setup running inside the engine VM, with the same
> error as when running 'engine-setup' (perhaps with --offline) manually,
> then this shouldn't happen at this point:
> - engine-backup --mode=restore sets vdc option in the db 'DbJustRestored'
> - engine-setup checks this and sets its own env[JUST_RESTORED] accordingly
>
> > (Understandable, given two of 3 hosts were offline due to certificate
> issues...)
> >
> >
> >>
> >>
> >> > preventing engine-setup --offline from running.
> >>
> >> Actually just a few days ago I pushed a patch for:
> >>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1700460
> >>
> >> But:
> >>
> >> If you really have a problem that you can't set global maintenance,
> >> using this is a risk - HA might intervene in the middle and shutdown
> >> the VM. So either make sure global maintenance does work, or stop
> >> all HA services on all hosts.
> >>
> >> > Two questions:
> >> > 1. Is there any automated method to renew the vdsm certificates?
> >>
> >> You mean, without an engine?
> >>
> >> I think that if you have a functional engine one way or another,
> >> you can automate this somehow, didn't check. Try checking e.g. the
> >> python sdk examples - there might be there something you can base
> >> on.
> >>
> >> > 2. Assuming the previous answer is "no", assuming I'm somewhat versed
> in using openssl, how can I manually renew them?
> >>
> >> I'd rather not try to invent from memory how this is supposed to work,
> >> and doing this methodically and verifying before replying is quite
> >> an effort.
> >>
> >> If this is really what you want, I suggest something like:
> >>
> >> 1. Set up a test env with an engine and one host
> >> 2. Backup (or use git on) /etc on both
> >> 3. Renew the host cert from the UI
> >> 4. Check wha

[ovirt-users] Importing export storage domain after redeploy failing, stating export domain still connected.

2022-02-07 Thread Gilboa Davara
Hello all,

I'm rebuilding one of my gluster clusters after it blew up following an
unfortunate expired certificate issue.
After I finally remembered to downgrade qemu (g...) and started
importing the hold gluster storage domains, one of the export domains
failed to import due to "connected to another domain" issue.
How can I force detach it from the previous cluster?
(I remember something about deleting the lease file - but I'm too brain
dead to find it in DDG...).

Engine errors:
$ cat engine.log | grep c3abcfe6-1062-48e2-8ca4-924b96b8c497
2022-02-07 13:31:24,729+02 INFO
 [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Lock Acquired to
object
'EngineLock:{exclusiveLocks='[22eec6d4-f0be-47db-b5d5-678bd84f47c6=STORAGE]',
sharedLocks=''}'
2022-02-07 13:31:24,747+02 INFO
 [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Running command:
AttachStorageDomainToPoolCommand internal: false. Entities affected :  ID:
22eec6d4-f0be-47db-b5d5-678bd84f47c6 Type: StorageAction group
MANIPULATE_STORAGE_DOMAIN with role type ADMIN,  ID:
257a27cc-87ec-11ec-bc62-00163e3fe79d Type: StoragePoolAction group
MANIPULATE_STORAGE_DOMAIN with role type ADMIN
2022-02-07 13:31:24,782+02 INFO
 [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] START,
AttachStorageDomainVDSCommand(
AttachStorageDomainVDSCommandParameters:{storagePoolId='257a27cc-87ec-11ec-bc62-00163e3fe79d',
ignoreFailoverLimit='false',
storageDomainId='22eec6d4-f0be-47db-b5d5-678bd84f47c6'}), log id: 777adb39
2022-02-07 13:31:48,281+02 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] EVENT_ID:
IRS_BROKER_COMMAND_FAILURE(10,803), VDSM command AttachStorageDomainVDS
failed: Storage domain already attached to pool:
'domain=22eec6d4-f0be-47db-b5d5-678bd84f47c6,
pool=2cb812a0-4a95-11eb-b3bc-00163e6a0a7c'
2022-02-07 13:31:48,281+02 ERROR
[org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Command
'AttachStorageDomainVDSCommand(
AttachStorageDomainVDSCommandParameters:{storagePoolId='257a27cc-87ec-11ec-bc62-00163e3fe79d',
ignoreFailoverLimit='false',
storageDomainId='22eec6d4-f0be-47db-b5d5-678bd84f47c6'})' execution failed:
IRSGenericException: IRSErrorException: Storage domain already attached to
pool: 'domain=22eec6d4-f0be-47db-b5d5-678bd84f47c6,
pool=2cb812a0-4a95-11eb-b3bc-00163e6a0a7c'
2022-02-07 13:31:48,281+02 INFO
 [org.ovirt.engine.core.vdsbroker.irsbroker.AttachStorageDomainVDSCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] FINISH,
AttachStorageDomainVDSCommand, return: , log id: 777adb39
2022-02-07 13:31:48,281+02 ERROR
[org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Command
'org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand'
failed: EngineException:
org.ovirt.engine.core.vdsbroker.irsbroker.IrsOperationFailedNoFailoverException:
IRSGenericException: IRSErrorException: Storage domain already attached to
pool: 'domain=22eec6d4-f0be-47db-b5d5-678bd84f47c6,
pool=2cb812a0-4a95-11eb-b3bc-00163e6a0a7c' (Failed with error
StorageDomainAlreadyAttached and code 380)
2022-02-07 13:31:48,283+02 INFO
 [org.ovirt.engine.core.bll.CommandCompensator] (default task-27)
[c3abcfe6-1062-48e2-8ca4-924b96b8c497] Command
[id=ec43c2c1-3441-4d91-9bd2-98280e9c0eaa]: Compensating NEW_ENTITY_ID of
org.ovirt.engine.core.common.businessentities.StoragePoolIsoMap; snapshot:
StoragePoolIsoMapId:{storagePoolId='257a27cc-87ec-11ec-bc62-00163e3fe79d',
storageId='22eec6d4-f0be-47db-b5d5-678bd84f47c6'}.
2022-02-07 13:31:48,290+02 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] EVENT_ID:
USER_ATTACH_STORAGE_DOMAIN_TO_POOL_FAILED(963), Failed to attach Storage
Domain local_export_storage_1 to Data Center Default. (User:
gilboa@internal-authz)
2022-02-07 13:31:48,294+02 INFO
 [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-27) [c3abcfe6-1062-48e2-8ca4-924b96b8c497] Lock freed to
object
'EngineLock:{exclusiveLocks='[22eec6d4-f0be-47db-b5d5-678bd84f47c6=STORAGE]',
sharedLocks=''}'

Thanks,
Gilboa
___
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/RDO73SALDQPWEEVAV3XCPFPNG3CQDLOZ/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-07 Thread Gilboa Davara
Hello,

On Mon, Feb 7, 2022 at 8:45 AM Yedidyah Bar David  wrote:

> On Sun, Feb 6, 2022 at 5:09 PM Gilboa Davara  wrote:
> >
> > Unlike my predecessor, I not only lost my vmengine, I also lost the vdsm
> services on all hosts.
> > All seem to be hitting the same issue - read, the certs under
> /etc/pki/vdsm/certs and /etc/pki/ovirt* all expired a couple of days ago.
> > As such, the hosted engine cannot go into global maintenance mode,
>
> What do you mean by that? What happens if you 'hosted-engine
> --set-maintenance --mode=global'?
>

Failed, stating the cluster is not in global maintenance mode.
(Understandable, given two of 3 hosts were offline due to certificate
issues...)



>
> > preventing engine-setup --offline from running.
>
> Actually just a few days ago I pushed a patch for:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1700460
>
> But:
>
> If you really have a problem that you can't set global maintenance,
> using this is a risk - HA might intervene in the middle and shutdown
> the VM. So either make sure global maintenance does work, or stop
> all HA services on all hosts.
>
> > Two questions:
> > 1. Is there any automated method to renew the vdsm certificates?
>
> You mean, without an engine?
>
> I think that if you have a functional engine one way or another,
> you can automate this somehow, didn't check. Try checking e.g. the
> python sdk examples - there might be there something you can base
> on.
>
> > 2. Assuming the previous answer is "no", assuming I'm somewhat versed in
> using openssl, how can I manually renew them?
>
> I'd rather not try to invent from memory how this is supposed to work,
> and doing this methodically and verifying before replying is quite
> an effort.
>
> If this is really what you want, I suggest something like:
>
> 1. Set up a test env with an engine and one host
> 2. Backup (or use git on) /etc on both
> 3. Renew the host cert from the UI
> 4. Check what changed
>
> You should find, IMO, that the key(s) on the host didn't
> change. I guess you might also find CSRs on one or both of them.
> So basically it should be something like:
> 1. Create a CSR on the host for the existing key (one or more,
> not sure).
> 2. Copy and sign this on the engine using pki-enroll-request.sh
> (I think you can find examples for it scattered around, perhaps
> even in the main guides)
> 3. Copy back the generated certs to the host
> 4. Perhaps restart one or more services there (vdsm, imageio?,
> ovn, etc.)
>
> You can check the code in
> /usr/share/ovirt-engine/ansible-runner-service-project/project
> to see how it's done when initiated from the UI.
>
> Good luck and best regards,
>

I more of less found a document stating the above somewhere in the middle
of the night.
Tried it.
Got the WebUI working again.
However, for the life of me I couldn't get the hosts to work to talk to the
engine. (Even though I could use openssl s_client -showcerts -connect host
and got valid certs).
In the end, @around ~4am, I decided to take the brute force route, clean
the hosts, upgrade them to -streams, and redeploy the engine again (3'rd
attempt, after sufficient amount of coffee reminded me the qemu-6.1 is
broken, and needed to be downgraded before trying to deploy the HE...).
Either way, when I finish importing the VMs, I'll open a RFE to add
BIG-WARNING-IN-BOLD-LETTERS in the WebUI to notify the admin that the
certificates are about to expire.

Thanks for the help!

- Gilboa



> --
> Didi
>
>
___
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/CGSAB7NPWWOYON6WXIRJXPZASVWCPQJT/


[ovirt-users] Re: Cannot log into oVirt Manager - certificate issue

2022-02-06 Thread Gilboa Davara
Hello,

On Tue, Feb 1, 2022 at 8:46 AM Yedidyah Bar David  wrote:

> On Mon, Jan 31, 2022 at 6:06 PM Diggy Mc  wrote:
> >
> > > On Sun, Jan 30, 2022 at 8:16 PM Diggy Mc  wrote:
> > >
> > > If it's a certificate created by engine-setup for you, you can run
> > > 'engine-setup' and it can recreate it for you. If you do not want to
> > > update the system, you can run it with 'engine-setup --offline'.
> > > Otherwise, if it's a certificate you got elsewhere, you should update
> > > it manually, perhaps following some of the steps of the procedure to
> > > replace the certificate - the one you followed originally.
> > >
> > > Good luck and best regards,
> >
> >
> > It is the original certificate created during initial install/setup.  If
> possible, I would like to have another oVirt generated certificate without
> upgrading the engine's version. Where can I find instructions on how to do
> that?
> >  What would be the pros and cons of generating my own self-signed
> certificate
>
> Generally speaking, this is recommended. The main "con" is simply that it
> requires some work and responsibility.
>
> > with a longer validity period?
>
> You already linked to the pki-renew page. This one links at several
> bugs, which link to several patches, which (also) explain the reasoning,
> also linking e.g. at:
>
>
> https://www.thesslstore.com/blog/ssl-certificate-validity-will-be-limited-to-one-year-by-apples-safari-browser/
> https://cabforum.org/2017/03/17/ballot-193-825-day-certificate-lifetimes/
>
> Latter is old, this one is newer (found by searching their site for "398
> days"):
>
> https://cabforum.org/2021/04/22/ballot-sc42-398-day-re-use-period/
>
> >  Where can I find instructions on that?
>
>
> https://www.ovirt.org/documentation/administration_guide/#appe-Red_Hat_Enterprise_Virtualization_and_SSL
>
> Actually creating your own CA and signing certs with it is not in the
> scope of this document. You can search the net and find several guides
> on how to do that, or you can use the services of an existing CA -
> letsencrypt is quite popular these days, being free (gratis).
>
> >  Again, thanks for your help.
>
> Good luck and best regards,
> --
> Didi
>

Unlike my predecessor, I not only lost my vmengine, I also lost the vdsm
services on all hosts.
All seem to be hitting the same issue - read, the certs under
/etc/pki/vdsm/certs and /etc/pki/ovirt* all expired a couple of days ago.
As such, the hosted engine cannot go into global maintenance mode,
preventing engine-setup --offline from running.
Two questions:
1. Is there any automated method to renew the vdsm certificates?
2. Assuming the previous answer is "no", assuming I'm somewhat versed in
using openssl, how can I manually renew them?

Thanks,

Gilboa
___
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/P3QPMCCZJCS3BC3AAXBGJMBDDSZTL2DB/


[ovirt-users] Re: mdadm vs. JBOD

2022-01-21 Thread Gilboa Davara
On Fri, Jan 21, 2022 at 10:45 AM Gilboa Davara  wrote:

> On Thu, Jan 20, 2022 at 8:52 AM  wrote:
>
>> Hi all,
>>
>> Feel free to give your personal opinion whether software RAID makes any
>> sense at all with oVirt Node or what your architecture would be given the
>> mentioned hardware (3 servers, 6 800GB NVME disks, 18 7.68TB NVME disks).
>>
>> Thanks a lot for any feedback,
>> Jonas
>>
>
> Hello,
>
> I somehow missed your original email.
> While I don't have a comparable setup (We usually opt for mixed SSD HDD
> setups with fast VMs running on SSD bached gluster volumes and
> large-storage VMs using HDD backed gluster volume), I can offer some
> insight.
> 1. Performance wise, using software RAID10 on the NVME drives will give
> you great performance, while reducing the chance of a double drop.
> 2. Avoid using RAID5/50/6/60 as the write amplification will eat up your
> read-intensive NVMEs life span in a couple of months.
> 3, Use a fast network back-end. A good high-end server with hardware RAID
> HDD can easily saturate a 10GbR Linux @peak load.
> 4. Use arbiter volumes, split the load between the nodes to reduce the
> write amplifications. (N1: brick, brick, arbiter. N2: brick, arbiter,
> brick. N3: arbiter, brick, brick).
> 5. In general I usually avoid using the wizard, manually creating the
> gluster volumes before I begin the deployment.
>
> - Gilboa
>

I missed the fact that your 3'rd host has considerably smaller storage.
In this case, luckily I have a comparable setup @Home. I simply placed all
the arbiter volumes on the 3'rd host.

- Gilboa
___
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/U2ZEWLRF5D6FENQEI5QXL77CMWB7XF32/


[ovirt-users] Re: mdadm vs. JBOD

2022-01-21 Thread Gilboa Davara
On Thu, Jan 20, 2022 at 8:52 AM  wrote:

> Hi all,
>
> Feel free to give your personal opinion whether software RAID makes any
> sense at all with oVirt Node or what your architecture would be given the
> mentioned hardware (3 servers, 6 800GB NVME disks, 18 7.68TB NVME disks).
>
> Thanks a lot for any feedback,
> Jonas
>

Hello,

I somehow missed your original email.
While I don't have a comparable setup (We usually opt for mixed SSD HDD
setups with fast VMs running on SSD bached gluster volumes and
large-storage VMs using HDD backed gluster volume), I can offer some
insight.
1. Performance wise, using software RAID10 on the NVME drives will give you
great performance, while reducing the chance of a double drop.
2. Avoid using RAID5/50/6/60 as the write amplification will eat up your
read-intensive NVMEs life span in a couple of months.
3, Use a fast network back-end. A good high-end server with hardware RAID
HDD can easily saturate a 10GbR Linux @peak load.
4. Use arbiter volumes, split the load between the nodes to reduce the
write amplifications. (N1: brick, brick, arbiter. N2: brick, arbiter,
brick. N3: arbiter, brick, brick).
5. In general I usually avoid using the wizard, manually creating the
gluster volumes before I begin the deployment.

- Gilboa




> ___
> 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/ZZ5VDBPHTEVGATFRRQDEWIUFTBWK6TWN/
>
___
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/MUNFLE23LVLBURNCP7EXESLWLJQZM3JL/


[ovirt-users] Re: Unrecoverable NMI error on HP Gen8 hosts.

2022-01-02 Thread Gilboa Davara
On Thu, Dec 30, 2021 at 8:02 PM Diggy Mc  wrote:

>
> I have oVirt Node v4.4.8.3 running on several HP ProLiant Gen8 servers.  I
> receive the following error under certain circumstances:
> "An Unrecoverable System Error (NMI) has occurred (iLO application
> watchdog timeout NMI, Service Information: 0x002B, 0x)"
>
> When a host starts taking a load (but nowhere near a threshold), I
> encounter the above iLO-logged error and the host locks-up.  I have had to
> grossly under-utilize my hosts to avoid this problem.  I'm hoping for a
> better fix or work-around.
>
> I've had the same problem beginning with my oVirt 4.3.x hosts, so it isn't
> oVirt version specific.
>
> The little information I could find on the error wasn't helpful.  Red Hat
> acknowledges the issue, but limited to shutdown/reboot operations; not
> during "normal" operations.
>
> Anyone else experienced this problem?  How did you fix it or work around
> it?  I'd like to better utilize my servers if possible.
>
> In advance, thank you to anyone and everyone who offers help.
>
> NMI errors are usually hardware related or kernel / system related. (E.g.
memory failure, hardware health check watchdog, etc)
They are not oVirt related per-say.

That said, I'm seeing an HPE report with the same NMI service code.
https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/Proliant-dl360p-gen8An-Unrecoverable-SystemError-NMI-has/td-p/7043891#.YdHHOduxUik

- Gilboa
___
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/MXADE3ZVXA3VNQISODECP5XQEBEUYA4Y/


[ovirt-users] Re: Update Issue

2021-11-21 Thread Gilboa Davara
On Fri, Nov 19, 2021 at 10:26 PM Darrell Budic 
wrote:

> Ah, sounds like the issue I was having with a new install/upgrade as well (
> https://bugzilla.redhat.com/show_bug.cgi?id=2023919)
>
> It’s definitely affecting stream users and pretty  much any new install at
> the moment.
>

I can confirm that downgrading the qemu packages to 6.0 solves the problem.
I managed to successfully deploy the ME on a gluster and migrate VMs
between the hosts.

- Gilboa



>
> On Nov 18, 2021, at 7:14 AM, Yedidyah Bar David  wrote:
>
> On Thu, Nov 18, 2021 at 2:14 PM Christoph Timm  wrote:
>
>
> looks like they are already aware of it:
>
>
> Indeed.
>
>
> https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/BDYP62MAJL2QVQZ7RHM2USZD4HXBGUA6/
>
>
> Now replied there, and created this bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2024605
>
> Also posted now to centos-devel, "qemu-kvm 6.1.0 with 16 PCIE root
> ports is broken".
>
> For the time being, we know of two workarounds:
>
> 1. Use qemu-kvm 6.0.0, available from the advanced virtualization SIG
> repo, should automatically be enabled by ovirt-release package. So
> e.g.:
>
> Per host:
> - Move to maintenance
> - dnf downgrade qemu-kvm-core-6.0.0
> - Activate
>
> 2. Configure your engine to use less than 16 pcie root ports, e.g. 12 like
> here:
>
> https://gerrit.ovirt.org/c/ovirt-system-tests/+/117689
>
> This might be problematic, though, if you need to add many devices to your
> VMs.
>
> Best regards,
>
> --
> Didi
> ___
> 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:
>
>
>
___
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/GDI5QN3ITUL2K3OTAHRXITG52G5KTVRV/


[ovirt-users] Re: CentOS 8 streams: Hosted engine deploy failed.

2021-11-19 Thread Gilboa Davara
Resolved: Downgrading qemu* on all hosts involved allows me to successfully
deploy the ME.

- Gilboa

On Sat, Nov 20, 2021 at 7:12 AM Gilboa Davara  wrote:

> Most likely I'm hitting this [1].
> Attempting to downgrade qemu and redeploying.
>
> - Gilboa
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2023919
>
> On Fri, Nov 19, 2021 at 10:25 PM Gilboa Davara  wrote:
>
>> Hello all,
>>
>> I'm trying to redeploy one of the HE/Gluster clusters after a botched
>> upgrade to Stream + simultaneous 2 x UPS failure that killed the previous
>> setup.
>> Post crash, the 3 nodes were cleaned up
>> (manually + ovirt-hosted-engine-cleanup) and upgraded to Streams + reboot.
>> I've made 3 attempts to deploy the HE, all failed with the same error.
>> As far as I can see, everything works up until the final deployment,
>> there the host fails to access the HE static address.
>> Note: All machines have a static IP, resolved via local hosts file.
>>
>> Please advise (log attached).
>>
>> - Gilboa
>>
>
___
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/LSARLLQIK5GMPK5P5T2KBLQTRF7NFLXT/


[ovirt-users] Re: CentOS 8 streams: Hosted engine deploy failed.

2021-11-19 Thread Gilboa Davara
Most likely I'm hitting this [1].
Attempting to downgrade qemu and redeploying.

- Gilboa
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2023919

On Fri, Nov 19, 2021 at 10:25 PM Gilboa Davara  wrote:

> Hello all,
>
> I'm trying to redeploy one of the HE/Gluster clusters after a botched
> upgrade to Stream + simultaneous 2 x UPS failure that killed the previous
> setup.
> Post crash, the 3 nodes were cleaned up
> (manually + ovirt-hosted-engine-cleanup) and upgraded to Streams + reboot.
> I've made 3 attempts to deploy the HE, all failed with the same error.
> As far as I can see, everything works up until the final deployment, there
> the host fails to access the HE static address.
> Note: All machines have a static IP, resolved via local hosts file.
>
> Please advise (log attached).
>
> - Gilboa
>
___
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/Y7CWIAZAFX22Y5VL6WE2Z2MDYLU366HJ/


[ovirt-users] CentOS 8 streams: Hosted engine deploy failed.

2021-11-19 Thread Gilboa Davara
Hello all,

I'm trying to redeploy one of the HE/Gluster clusters after a botched
upgrade to Stream + simultaneous 2 x UPS failure that killed the previous
setup.
Post crash, the 3 nodes were cleaned up
(manually + ovirt-hosted-engine-cleanup) and upgraded to Streams + reboot.
I've made 3 attempts to deploy the HE, all failed with the same error.
As far as I can see, everything works up until the final deployment, there
the host fails to access the HE static address.
Note: All machines have a static IP, resolved via local hosts file.

Please advise (log attached).

- Gilboa


ovirt-hosted-engine-setup-2029210827-filq48.log.bz2
Description: application/bzip
___
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/62SOPJTEBPVHLABKNOYNHTJFK2MTAM4D/


[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-09 Thread Gilboa Davara
Strike that, said cluster is already using 4.40.90.4-1. Adding myself to
the BZ.

 - Gilboa

On Tue, Nov 9, 2021 at 5:48 PM Gilboa Davara  wrote:

> Many thanks!
>
> Somehow my Google-fu skills (and DDG-Fu skills) missed this bug report.
> I wonder if 4.4.9 will fix the sporadic -ENOMEM (1) that I'm getting under
> Q35...
>
> Thanks,
> - Gilboa
>
> (1)
> 2021-11-05T13:13:06.290874Z qemu-kvm: -device
> vfio-pci,host=:07:00.0,id=ua-a3048786-da87-425f-83e6-51afbb906423,bus=pci.10,addr=0x0:
> VFIO_MAP_DMA failed: Cannot allocate memory
> 2021-11-05T13:13:06.362210Z qemu-kvm: -device
> vfio-pci,host=:07:00.0,id=ua-a3048786-da87-425f-83e6-51afbb906423,bus=pci.10,addr=0x0:
> VFIO_MAP_DMA failed: Cannot allocate memory
> 2021-11-05T13:13:06.362609Z qemu-kvm: -device
> vfio-pci,host=:07:00.0,id=ua-a3048786-da87-425f-83e6-51afbb906423,bus=pci.10,addr=0x0:
> vfio :07:00.0: failed to setup container for group 33: memory listener
> initialization failed: Region ram-node0: vfio_dma_map(0x55fe05d647f0,
> 0xc, 0x7ff4, 0x7f821fec) = -12 (Cannot allocate memory)
> 2021-11-05 13:13:06.580+: shutting down, reason=failed
>
> On Tue, Nov 9, 2021 at 3:29 PM Arik Hadas  wrote:
>
>>
>>
>> On Tue, Nov 9, 2021 at 11:57 AM Gilboa Davara  wrote:
>>
>>> (Sorry: Pressed send too fast...)
>>> 3. I'm facing some odd memory allocation issues (only if the VM is Q35,
>>> all works well if the VM is configured as i440fx), which may require me to
>>> change additional VM parameters.
>>>
>>> BTW, ironically, the two other hosts in the same cluster, with older
>>> MBs, have zero issues with GPU/Audio/USB passthrough...)
>>>
>>> - Gilboa
>>>
>>> On Tue, Nov 9, 2021 at 11:52 AM Gilboa Davara  wrote:
>>>
>>>> Hello,
>>>>
>>>> Many thanks for the prompt reply.
>>>>
>>>> On Mon, Nov 8, 2021 at 8:52 PM Nir Soffer  wrote:
>>>>
>>>>> On Mon, Nov 8, 2021 at 5:47 PM Gilboa Davara 
>>>>> wrote:
>>>>> >
>>>>> > Hello all,
>>>>> >
>>>>> > I'm setting up a fairly (?) complex oVirt over Gluster setup built
>>>>> around 3 Xeon servers-turned-into-workstations, each doubling as oVirt 
>>>>> node
>>>>> + one primary Fedora VM w/ a dedicated passthrough GPU (+audio and a 
>>>>> couple
>>>>> of USB root devices).
>>>>> > One of the servers seems to have some weird issue w/ the passthrough
>>>>> nVidia GPU that seems to require me to edit the VM iommu (1) and
>>>>> passthrough device (2) command line.
>>>>> > I tried using the qemu-cmdline addon to add the missing parameters,
>>>>> but it seems that qemu treats the added parameters as an additional device
>>>>> / iommu instead of editing the existing parameters.
>>>>> >
>>>>> > So:
>>>>> > 1. How can I view the VM qemu command line?
>>>>>
>>>>> less /var/log/libvirt/qemu/vm-name.log
>>>>>
>>>>
>>>> Found it, thanks!
>>>>
>>>>
>>>>> > 2. Can I somehow manually edit the qemu command line, either
>>>>> directly or by somehow adding parameters in the HE XML file?
>>>>>
>>>>> I think this should be possible via vdsm hook, but hooks are bad.
>>>>> Can you explain what do you want to change?
>>>>>
>>>>> Nir
>>>>>
>>>>
>>>> 1. IOMMU:
>>>> -device intel-iommu,intremap=on,eim=on
>>>> To (Add: caching-mode=on, per qemu log message)
>>>> -device intel-iommu,intremap=on,eim=on,caching-mode=on
>>>> (2021-11-05T18:42:36.651191Z qemu-kvm: We need to set caching-mode=on
>>>> for intel-iommu to enable device assignment with IOMMU protection.)
>>>>
>>>
>> Note that this one should be fixed in the latest ovirt-engine
>> (ovirt-engine-4.4.9.4) -
>> https://bugzilla.redhat.com/show_bug.cgi?id=2013752
>>
>>
>>>
>>>> 2. Device:
>>>> -device
>>>> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.10,addr=0x0
>>>>
>>>> -device
>>>> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8,addr=0x0
>>>> To (Attach hdmi sound as function of GPU, possibly add x-vga=on):
>>>> -device
>>>> vfio-pci,host=:8

[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-09 Thread Gilboa Davara
Many thanks!

Somehow my Google-fu skills (and DDG-Fu skills) missed this bug report.
I wonder if 4.4.9 will fix the sporadic -ENOMEM (1) that I'm getting under
Q35...

Thanks,
- Gilboa

(1)
2021-11-05T13:13:06.290874Z qemu-kvm: -device
vfio-pci,host=:07:00.0,id=ua-a3048786-da87-425f-83e6-51afbb906423,bus=pci.10,addr=0x0:
VFIO_MAP_DMA failed: Cannot allocate memory
2021-11-05T13:13:06.362210Z qemu-kvm: -device
vfio-pci,host=:07:00.0,id=ua-a3048786-da87-425f-83e6-51afbb906423,bus=pci.10,addr=0x0:
VFIO_MAP_DMA failed: Cannot allocate memory
2021-11-05T13:13:06.362609Z qemu-kvm: -device
vfio-pci,host=:07:00.0,id=ua-a3048786-da87-425f-83e6-51afbb906423,bus=pci.10,addr=0x0:
vfio :07:00.0: failed to setup container for group 33: memory listener
initialization failed: Region ram-node0: vfio_dma_map(0x55fe05d647f0,
0xc, 0x7ff4, 0x7f821fec) = -12 (Cannot allocate memory)
2021-11-05 13:13:06.580+: shutting down, reason=failed

On Tue, Nov 9, 2021 at 3:29 PM Arik Hadas  wrote:

>
>
> On Tue, Nov 9, 2021 at 11:57 AM Gilboa Davara  wrote:
>
>> (Sorry: Pressed send too fast...)
>> 3. I'm facing some odd memory allocation issues (only if the VM is Q35,
>> all works well if the VM is configured as i440fx), which may require me to
>> change additional VM parameters.
>>
>> BTW, ironically, the two other hosts in the same cluster, with older MBs,
>> have zero issues with GPU/Audio/USB passthrough...)
>>
>> - Gilboa
>>
>> On Tue, Nov 9, 2021 at 11:52 AM Gilboa Davara  wrote:
>>
>>> Hello,
>>>
>>> Many thanks for the prompt reply.
>>>
>>> On Mon, Nov 8, 2021 at 8:52 PM Nir Soffer  wrote:
>>>
>>>> On Mon, Nov 8, 2021 at 5:47 PM Gilboa Davara  wrote:
>>>> >
>>>> > Hello all,
>>>> >
>>>> > I'm setting up a fairly (?) complex oVirt over Gluster setup built
>>>> around 3 Xeon servers-turned-into-workstations, each doubling as oVirt node
>>>> + one primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple
>>>> of USB root devices).
>>>> > One of the servers seems to have some weird issue w/ the passthrough
>>>> nVidia GPU that seems to require me to edit the VM iommu (1) and
>>>> passthrough device (2) command line.
>>>> > I tried using the qemu-cmdline addon to add the missing parameters,
>>>> but it seems that qemu treats the added parameters as an additional device
>>>> / iommu instead of editing the existing parameters.
>>>> >
>>>> > So:
>>>> > 1. How can I view the VM qemu command line?
>>>>
>>>> less /var/log/libvirt/qemu/vm-name.log
>>>>
>>>
>>> Found it, thanks!
>>>
>>>
>>>> > 2. Can I somehow manually edit the qemu command line, either directly
>>>> or by somehow adding parameters in the HE XML file?
>>>>
>>>> I think this should be possible via vdsm hook, but hooks are bad.
>>>> Can you explain what do you want to change?
>>>>
>>>> Nir
>>>>
>>>
>>> 1. IOMMU:
>>> -device intel-iommu,intremap=on,eim=on
>>> To (Add: caching-mode=on, per qemu log message)
>>> -device intel-iommu,intremap=on,eim=on,caching-mode=on
>>> (2021-11-05T18:42:36.651191Z qemu-kvm: We need to set caching-mode=on
>>> for intel-iommu to enable device assignment with IOMMU protection.)
>>>
>>
> Note that this one should be fixed in the latest ovirt-engine
> (ovirt-engine-4.4.9.4) -
> https://bugzilla.redhat.com/show_bug.cgi?id=2013752
>
>
>>
>>> 2. Device:
>>> -device
>>> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.10,addr=0x0
>>>
>>> -device
>>> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8,addr=0x0
>>> To (Attach hdmi sound as function of GPU, possibly add x-vga=on):
>>> -device
>>> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.8.0,x-vga=on,addr=0x0
>>>
>>> -device
>>> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8.1,addr=0x0
>>>
>>> 3. I'm facing some odd memory allocation issues (only if the VM is Q35,
>>> all works well if the VM is configured as i440fx), which may req
>>>
>> ___
>> 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/XKZLE6ZEU7ZNXSMYEMA65F6MJBSNZQVD/
>>
>
___
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/THCZLYXCPVR6SF63HKNBIYUKB74HIFZG/


[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-09 Thread Gilboa Davara
(Sorry: Pressed send too fast...)
3. I'm facing some odd memory allocation issues (only if the VM is Q35, all
works well if the VM is configured as i440fx), which may require me to
change additional VM parameters.

BTW, ironically, the two other hosts in the same cluster, with older MBs,
have zero issues with GPU/Audio/USB passthrough...)

- Gilboa

On Tue, Nov 9, 2021 at 11:52 AM Gilboa Davara  wrote:

> Hello,
>
> Many thanks for the prompt reply.
>
> On Mon, Nov 8, 2021 at 8:52 PM Nir Soffer  wrote:
>
>> On Mon, Nov 8, 2021 at 5:47 PM Gilboa Davara  wrote:
>> >
>> > Hello all,
>> >
>> > I'm setting up a fairly (?) complex oVirt over Gluster setup built
>> around 3 Xeon servers-turned-into-workstations, each doubling as oVirt node
>> + one primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple
>> of USB root devices).
>> > One of the servers seems to have some weird issue w/ the passthrough
>> nVidia GPU that seems to require me to edit the VM iommu (1) and
>> passthrough device (2) command line.
>> > I tried using the qemu-cmdline addon to add the missing parameters, but
>> it seems that qemu treats the added parameters as an additional device /
>> iommu instead of editing the existing parameters.
>> >
>> > So:
>> > 1. How can I view the VM qemu command line?
>>
>> less /var/log/libvirt/qemu/vm-name.log
>>
>
> Found it, thanks!
>
>
>> > 2. Can I somehow manually edit the qemu command line, either directly
>> or by somehow adding parameters in the HE XML file?
>>
>> I think this should be possible via vdsm hook, but hooks are bad.
>> Can you explain what do you want to change?
>>
>> Nir
>>
>
> 1. IOMMU:
> -device intel-iommu,intremap=on,eim=on
> To (Add: caching-mode=on, per qemu log message)
> -device intel-iommu,intremap=on,eim=on,caching-mode=on
> (2021-11-05T18:42:36.651191Z qemu-kvm: We need to set caching-mode=on for
> intel-iommu to enable device assignment with IOMMU protection.)
>
> 2. Device:
> -device
> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.10,addr=0x0
>
> -device
> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8,addr=0x0
> To (Attach hdmi sound as function of GPU, possibly add x-vga=on):
> -device
> vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.8.0,x-vga=on,addr=0x0
>
> -device
> vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8.1,addr=0x0
>
> 3. I'm facing some odd memory allocation issues (only if the VM is Q35,
> all works well if the VM is configured as i440fx), which may req
>
___
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/XKZLE6ZEU7ZNXSMYEMA65F6MJBSNZQVD/


[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-09 Thread Gilboa Davara
Hello,

Many thanks for the prompt reply.

On Mon, Nov 8, 2021 at 8:52 PM Nir Soffer  wrote:

> On Mon, Nov 8, 2021 at 5:47 PM Gilboa Davara  wrote:
> >
> > Hello all,
> >
> > I'm setting up a fairly (?) complex oVirt over Gluster setup built
> around 3 Xeon servers-turned-into-workstations, each doubling as oVirt node
> + one primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple
> of USB root devices).
> > One of the servers seems to have some weird issue w/ the passthrough
> nVidia GPU that seems to require me to edit the VM iommu (1) and
> passthrough device (2) command line.
> > I tried using the qemu-cmdline addon to add the missing parameters, but
> it seems that qemu treats the added parameters as an additional device /
> iommu instead of editing the existing parameters.
> >
> > So:
> > 1. How can I view the VM qemu command line?
>
> less /var/log/libvirt/qemu/vm-name.log
>

Found it, thanks!


> > 2. Can I somehow manually edit the qemu command line, either directly or
> by somehow adding parameters in the HE XML file?
>
> I think this should be possible via vdsm hook, but hooks are bad.
> Can you explain what do you want to change?
>
> Nir
>

1. IOMMU:
-device intel-iommu,intremap=on,eim=on
To (Add: caching-mode=on, per qemu log message)
-device intel-iommu,intremap=on,eim=on,caching-mode=on
(2021-11-05T18:42:36.651191Z qemu-kvm: We need to set caching-mode=on for
intel-iommu to enable device assignment with IOMMU protection.)

2. Device:
-device
vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.10,addr=0x0

-device
vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8,addr=0x0
To (Attach hdmi sound as function of GPU, possibly add x-vga=on):
-device
vfio-pci,host=:84:00.0,id=ua-c774115b-c0ee-43a5-97c8-12ac73cb6f3a,bus=pci.8.0,x-vga=on,addr=0x0

-device
vfio-pci,host=:84:00.1,id=ua-3c7d3b66-57aa-470b-afc8-78383ac9a025,bus=pci.8.1,addr=0x0

3. I'm facing some odd memory allocation issues (only if the VM is Q35, all
works well if the VM is configured as i440fx), which may req
___
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/ZO7LU22PMJNTEUC5FEJPDGXH64XDAQIV/


[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-08 Thread Gilboa Davara
On Mon, Nov 8, 2021 at 5:37 PM Gilboa Davara  wrote:

> Hello all,
>
> I'm setting up a fairly (?) complex oVirt over Gluster setup built around
> 3 Xeon servers-turned-into-workstations, each doubling as oVirt node + one
> primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple of
> USB root devices).
> One of the servers seems to have some weird issue w/ the passthrough
> nVidia GPU that seems to require me to edit the VM iommu (1) and
> passthrough device (2) command line.
> I tried using the qemu-cmdline addon to add the missing parameters, but it
> seems that qemu treats the added parameters as an additional device / iommu
> instead of editing the existing parameters.
>
> So:
> 1. How can I view the VM qemu command line?
> 2. Can I somehow manually edit the qemu command line, either directly or
> by somehow adding parameters in the HE XML file?
>
> - Gilboa.
> [1] iommu:  VM XXX is down with error. Exit message: internal error: qemu
> unexpectedly closed the monitor: 2021-11-05T14:59:44.499366Z qemu-kvm: We
> need to set caching-mode=on for intel-iommu to enable device assignment
> with IOMMU protection.
> [2] GPU: May need to add x-vga=off,
>

BTW, FWIW, by isolated I mean device attached during boot to vfio_pci, and
passed to the VM with all of its iommu group members (e.g. nVidia GPU +
nVidia HDMI audio).

- Gilboa
___
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/QB5JWEEGXKMR36EJDTDZCIORFPEBJYRZ/


[ovirt-users] Viewing and hopefully, modifying the VM's qemu command line

2021-11-08 Thread Gilboa Davara
Hello all,

I'm setting up a fairly (?) complex oVirt over Gluster setup built around 3
Xeon servers-turned-into-workstations, each doubling as oVirt node + one
primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple of
USB root devices).
One of the servers seems to have some weird issue w/ the passthrough nVidia
GPU that seems to require me to edit the VM iommu (1) and passthrough
device (2) command line.
I tried using the qemu-cmdline addon to add the missing parameters, but it
seems that qemu treats the added parameters as an additional device / iommu
instead of editing the existing parameters.

So:
1. How can I view the VM qemu command line?
2. Can I somehow manually edit the qemu command line, either directly or by
somehow adding parameters in the HE XML file?

- Gilboa.
[1] iommu:  VM XXX is down with error. Exit message: internal error: qemu
unexpectedly closed the monitor: 2021-11-05T14:59:44.499366Z qemu-kvm: We
need to set caching-mode=on for intel-iommu to enable device assignment
with IOMMU protection.
[2] GPU: May need to add x-vga=off,
___
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/WGP2VUHG3QHZKCEX2GE3DFLGEI4DT7FW/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-13 Thread Gilboa Davara
Shabbat Shalom,

On Wed, Aug 11, 2021 at 10:03 AM Yedidyah Bar David  wrote:

> On Tue, Aug 10, 2021 at 9:20 PM Gilboa Davara  wrote:
> >
> > Hello,
> >
> > Many thanks again for taking the time to try and help me recover this
> machine (even though it would have been far easier to simply redeploy it...)
> >
> >> >
> >> >
> >> > Sadly enough, it seems that --clean-metadata requires an active agent.
> >> > E.g.
> >> > $ hosted-engine --clean-metadata
> >> > The hosted engine configuration has not been retrieved from shared
> storage. Please ensure that ovirt-ha-agent
> >> > is running and the storage server is reachable.
> >>
> >> Did you try to search the net/list archives?
> >
> >
> > Yes. All of them seem to repeat the same clean-metadata command (which
> fails).
>
> I suppose we need better documentation. Sorry. Perhaps open a
> bug/issue about that.
>

Done.
https://bugzilla.redhat.com/show_bug.cgi?id=1993575


>
> >
> >>
> >>
> >> >
> >> > Can I manually delete the metadata state files?
> >>
> >> Yes, see e.g.:
> >>
> >> https://lists.ovirt.org/pipermail/users/2016-April/072676.html
> >>
> >> As an alternative to the 'find' command there, you can also find the
> IDs with:
> >>
> >> $ grep metadata /etc/ovirt-hosted-engine/hosted-engine.conf
> >>
> >> Best regards,
> >> --
> >> Didi
> >
> >
> > Yippie! Success (At least it seems that way...)
> >
> > Following https://lists.ovirt.org/pipermail/users/2016-April/072676.html
> ,
> > I stopped the broker and agent services, archived the existing hosted
> metadata files, created an empty 1GB metadata file using dd, (dd
> if=/dev/zero of=/run/vdsm/storage// bs=1M count=1024), making
> double sure permissions (0660 / 0644), owner (vdsm:kvm) and SELinux labels
> (restorecon, just incase) stay the same.
> > Let everything settle down.
> > Restarted the services
> > ... and everything is up again :)
> >
> > I plan to let the engine run overnight with zero VMs (making sure all
> backups are fully up-to-date).
> > Once done, I'll return to normal (until I replace this setup with a
> normal multi-node setup).
> >
> > Many thanks again!
>
> Glad to hear that, welcome, thanks for the report!
>
> More tests you might want to do before starting your real VMs:
>
> - Set and later clear global maintenance from each hosts, see that this
> propagates to the others (both 'hosted-engine --vm-status' and agent.log)
>
> - Migrate the engine VM between the hosts and see this propagates
>
> - Shutdown the engine VM without global maint and see that it's started
> automatically.
>
> But I do not think all of this is mandatory, if 'hosted-engine --vm-status'
> looks ok on all hosts.
>
> I'd still be careful with other things that might have been corrupted,
> though - obviously can't tell you what/where...
>
>
Host is back to normal.
The log looks clean (minus some odd smtp errors in the log).

Either way, I'm already in the process of replacing this setup with a real
3 host + gluster setup, so I just need this machine to survive the next
couple of weeks :)

- Gilboa
___
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/N4WIQXDW2ITLT2KDDH4LI4RTZRP2XWTY/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-10 Thread Gilboa Davara
Hello,

Many thanks again for taking the time to try and help me recover this
machine (even though it would have been far easier to simply redeploy it...)

>
> >
> > Sadly enough, it seems that --clean-metadata requires an active agent.
> > E.g.
> > $ hosted-engine --clean-metadata
> > The hosted engine configuration has not been retrieved from shared
> storage. Please ensure that ovirt-ha-agent
> > is running and the storage server is reachable.
>
> Did you try to search the net/list archives?
>

Yes. All of them seem to repeat the same clean-metadata command (which
fails).


>
> >
> > Can I manually delete the metadata state files?
>
> Yes, see e.g.:
>
> https://lists.ovirt.org/pipermail/users/2016-April/072676.html
>
> As an alternative to the 'find' command there, you can also find the IDs
> with:
>
> $ grep metadata /etc/ovirt-hosted-engine/hosted-engine.conf
>
> Best regards,
> --
> Didi
>

Yippie! Success (At least it seems that way...)

Following https://lists.ovirt.org/pipermail/users/2016-April/072676.html,
I stopped the broker and agent services, archived the existing hosted
metadata files, created an empty 1GB metadata file using dd, (dd
if=/dev/zero of=/run/vdsm/storage// bs=1M count=1024), making
double sure permissions (0660 / 0644), owner (vdsm:kvm) and SELinux labels
(restorecon, just incase) stay the same.
Let everything settle down.
Restarted the services
... and everything is up again :)

I plan to let the engine run overnight with zero VMs (making sure all
backups are fully up-to-date).
Once done, I'll return to normal (until I replace this setup with a normal
multi-node setup).

Many thanks again!

- Gilboa
___
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/DXPXGU4FKWJOJZJM7CKAB7ZJZFR7NJZE/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-09 Thread Gilboa Davara
On Mon, Aug 9, 2021 at 4:13 PM Gilboa Davara  wrote:

>
>
> On Mon, Aug 9, 2021 at 2:46 PM Yedidyah Bar David  wrote:
>
>> On Mon, Aug 9, 2021 at 1:56 PM Gilboa Davara  wrote:
>> >
>> >
>> >
>> > On Mon, Aug 9, 2021 at 12:16 PM Gilboa Davara 
>> wrote:
>> >>
>> >> Hello,
>> >>
>> >> On Mon, Aug 9, 2021 at 11:50 AM Yedidyah Bar David 
>> wrote:
>> >>>
>> >>> On Mon, Aug 9, 2021 at 11:43 AM Strahil Nikolov via Users
>> >>>  wrote:
>> >>> >
>> >>> > Corrupted metadata is the problem you see.
>> >>> >
>> >>> > I think there was a command to fix it, but I can't recall it right
>> now.
>> >>>
>> >>> I think you refer to 'hosted-engine --clean_metadata'. Gilboa - I
>> >>> suggest to search the net/archives for docs/mentions/discussions of
>> >>> this option - it's rather drastic. Good luck.
>> >>>
>> >>> That said, I must say that if your metadata is corrupted, I wonder
>> >>> what else is - so would continue using this setup with great care.
>> >>> Ideally restore from backups, after testing/replacing the hardware.
>> >>>
>> >>> Best regards,
>> >>>
>> >>
>> >> Thanks for the pointer.
>> >> This is a side setup that's about to replaced by a real setup (3 host
>> Gluster).
>> >> That said, beyond the corrupted meta data, everything else seems to be
>> working just fine, host boot just fine, RAID sync showed no issues. XFS
>> partitions mounted OK, etc.
>> >> The only thing that seems damaged is the hosted engine meta data.
>> >>
>> >> I'll test it and report back.
>> >>
>> >> - Gilboa
>> >>
>> >
>> >
>> > Stupid question:
>> > Won't clean meta data remove the host from the "cluster" and given the
>> fact that its a single host configuration, require a clean redploy?
>>
>> It's not stupid.
>>
>> Generally speaking, the metadata is populated by the HA daemons
>> themselves, not something "external". If a specific host's entry is
>> missing, they should write it.
>>
>>
> OK. Thanks again for the prompt answer.
>
> - Gilboa
>

Sadly enough, it seems that --clean-metadata requires an active agent.
E.g.
$ hosted-engine --clean-metadata
The hosted engine configuration has not been retrieved from shared storage.
Please ensure that ovirt-ha-agent
is running and the storage server is reachable.

Can I manually delete the metadata state files?

- Gilboa
___
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/QVDS62AHPWK6NKZGG7QHWGSXV4FQLD43/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-09 Thread Gilboa Davara
On Mon, Aug 9, 2021 at 2:46 PM Yedidyah Bar David  wrote:

> On Mon, Aug 9, 2021 at 1:56 PM Gilboa Davara  wrote:
> >
> >
> >
> > On Mon, Aug 9, 2021 at 12:16 PM Gilboa Davara  wrote:
> >>
> >> Hello,
> >>
> >> On Mon, Aug 9, 2021 at 11:50 AM Yedidyah Bar David 
> wrote:
> >>>
> >>> On Mon, Aug 9, 2021 at 11:43 AM Strahil Nikolov via Users
> >>>  wrote:
> >>> >
> >>> > Corrupted metadata is the problem you see.
> >>> >
> >>> > I think there was a command to fix it, but I can't recall it right
> now.
> >>>
> >>> I think you refer to 'hosted-engine --clean_metadata'. Gilboa - I
> >>> suggest to search the net/archives for docs/mentions/discussions of
> >>> this option - it's rather drastic. Good luck.
> >>>
> >>> That said, I must say that if your metadata is corrupted, I wonder
> >>> what else is - so would continue using this setup with great care.
> >>> Ideally restore from backups, after testing/replacing the hardware.
> >>>
> >>> Best regards,
> >>>
> >>
> >> Thanks for the pointer.
> >> This is a side setup that's about to replaced by a real setup (3 host
> Gluster).
> >> That said, beyond the corrupted meta data, everything else seems to be
> working just fine, host boot just fine, RAID sync showed no issues. XFS
> partitions mounted OK, etc.
> >> The only thing that seems damaged is the hosted engine meta data.
> >>
> >> I'll test it and report back.
> >>
> >> - Gilboa
> >>
> >
> >
> > Stupid question:
> > Won't clean meta data remove the host from the "cluster" and given the
> fact that its a single host configuration, require a clean redploy?
>
> It's not stupid.
>
> Generally speaking, the metadata is populated by the HA daemons
> themselves, not something "external". If a specific host's entry is
> missing, they should write it.
>
>
OK. Thanks again for the prompt answer.

- Gilboa
___
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/3PASD2C2CRL3G4KCNEL2OGUUBAUAYXQQ/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-09 Thread Gilboa Davara
On Mon, Aug 9, 2021 at 12:16 PM Gilboa Davara  wrote:

> Hello,
>
> On Mon, Aug 9, 2021 at 11:50 AM Yedidyah Bar David 
> wrote:
>
>> On Mon, Aug 9, 2021 at 11:43 AM Strahil Nikolov via Users
>>  wrote:
>> >
>> > Corrupted metadata is the problem you see.
>> >
>> > I think there was a command to fix it, but I can't recall it right now.
>>
>> I think you refer to 'hosted-engine --clean_metadata'. Gilboa - I
>> suggest to search the net/archives for docs/mentions/discussions of
>> this option - it's rather drastic. Good luck.
>>
>> That said, I must say that if your metadata is corrupted, I wonder
>> what else is - so would continue using this setup with great care.
>> Ideally restore from backups, after testing/replacing the hardware.
>>
>> Best regards,
>>
>>
> Thanks for the pointer.
> This is a side setup that's about to replaced by a real setup (3 host
> Gluster).
> That said, beyond the corrupted meta data, everything else seems to be
> working just fine, host boot just fine, RAID sync showed no issues. XFS
> partitions mounted OK, etc.
> The only thing that seems damaged is the hosted engine meta data.
>
> I'll test it and report back.
>
> - Gilboa
>
>

Stupid question:
Won't clean meta data remove the host from the "cluster" and given the fact
that its a single host configuration, require a clean redploy?

- Gilboa



> >
>> > Best Regards,
>> > Strahil Nikolov
>> >
>> > On Sun, Aug 8, 2021 at 22:09, Gilboa Davara
>> >  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/OIFK3ZYOL2DBEI62UTVJANZBHT76B5FP/
>> >
>> > ___
>> > 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/LMJEU5MA3MAIELID3E2D6FNSIKK2T6RJ/
>>
>>
>>
>> --
>> Didi
>>
>>
___
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/NUOBF4CWNNSHLMIJ43PGASWQJPEPWXL5/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-09 Thread Gilboa Davara
Hello,

On Mon, Aug 9, 2021 at 11:50 AM Yedidyah Bar David  wrote:

> On Mon, Aug 9, 2021 at 11:43 AM Strahil Nikolov via Users
>  wrote:
> >
> > Corrupted metadata is the problem you see.
> >
> > I think there was a command to fix it, but I can't recall it right now.
>
> I think you refer to 'hosted-engine --clean_metadata'. Gilboa - I
> suggest to search the net/archives for docs/mentions/discussions of
> this option - it's rather drastic. Good luck.
>
> That said, I must say that if your metadata is corrupted, I wonder
> what else is - so would continue using this setup with great care.
> Ideally restore from backups, after testing/replacing the hardware.
>
> Best regards,
>
>
Thanks for the pointer.
This is a side setup that's about to replaced by a real setup (3 host
Gluster).
That said, beyond the corrupted meta data, everything else seems to be
working just fine, host boot just fine, RAID sync showed no issues. XFS
partitions mounted OK, etc.
The only thing that seems damaged is the hosted engine meta data.

I'll test it and report back.

- Gilboa


> >
> > Best Regards,
> > Strahil Nikolov
> >
> > On Sun, Aug 8, 2021 at 22:09, Gilboa Davara
> >  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/OIFK3ZYOL2DBEI62UTVJANZBHT76B5FP/
> >
> > ___
> > 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/LMJEU5MA3MAIELID3E2D6FNSIKK2T6RJ/
>
>
>
> --
> Didi
>
>
___
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/UGOGF34WS6TOWORNU3S5XLV3B33F25IJ/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-08 Thread Gilboa Davara
k.py",
line 85, in start_monitor
response = self._proxy.start_monitor(type, options)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__
return self.__send(self.__name, args)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request
verbose=self.__verbose
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request
return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1166, in single_request
http_conn = self.send_request(host, handler, request_body, verbose)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1279, in send_request
self.send_content(connection, request_body)
  File "/usr/lib64/python3.6/xmlrpc/client.py", line 1309, in send_content
connection.endheaders(request_body)
  File "/usr/lib64/python3.6/http/client.py", line 1264, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1040, in _send_output
self.send(msg)
  File "/usr/lib64/python3.6/http/client.py", line 978, in send
self.connect()
  File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py",
line 74, in connect
self.sock.connect(base64.b16decode(self.host))
FileNotFoundError: [Errno 2] No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
line 131, in _run_agent
return action(he)
  File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/agent.py",
line 55, in action_proper
return he.start_monitoring()
  File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 437, in start_monitoring
self._initialize_broker()
  File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py",
line 561, in _initialize_broker
m.get('options', {}))
  File
"/usr/lib/python3.6/site-packages/ovirt_hosted_engine_ha/lib/brokerlink.py",
line 91, in start_monitor
).format(t=type, o=options, e=e)
ovirt_hosted_engine_ha.lib.exceptions.RequestError: brokerlink - failed to
start monitor via ovirt-ha-broker: [Errno 2] No such file or directory,
[monitor: 'network', options: {'addr': '192.168.1.9', 'network_test':
'tcp', 'tcp_t_address': '192.168.1.2', 'tcp_t_port': '22'}]








>
>
>
> В неделя, 8 август 2021 г., 20:06:46 ч. Гринуич+3, Gilboa Davara <
> gilb...@gmail.com> написа:
>
>
>
>
>
> On Sun, Aug 8, 2021 at 7:53 PM Gilboa Davara  wrote:
> > Hello all,
> >
> > During the night, one of my (smaller) setups, a single node self hosted
> engine (localhost NFS) crashed due to what-looks-like a massive disk
> failure (Software RAID6, with 10 drives + spare).
> > After a reboot, I let the RAID resync with a fresh drive) and went on to
> start oVirt.
> > However, no such luck.
> > Two issues:
> > 1. ovirt-ha-broker fails due to broken hosted engine state (log
> attached).
> > 2. ovirt-ha-agent fails due to network test (tcp) even though both
> remote-host and DNS servers are active. (log attached).
> >
> > Two questions:
> > 1. Can I somehow force the agent to disable the network liveliness test?
> > 2. Can I somehow force the broker to rebuild / fix the hosted engine
> state?
> >
> > - Gilboa
>
> FWIW switching agent network test to none (via hosted-engine
> --set-shared-config network_test none --type=he_local) doesn't seem to work.
> (Unless I'm missing the point and the agent is failing due to broker
> issues and not due to a failed network liveliness check).
>
>
> - Gilboa
>
>
>
> ___
> 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/OH4H5K2FZXO6YNVFU6W3XL7NHW6N5LAU/
>
___
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/OIFK3ZYOL2DBEI62UTVJANZBHT76B5FP/


[ovirt-users] Re: Cannot restart ovirt after massive failure.

2021-08-08 Thread Gilboa Davara
On Sun, Aug 8, 2021 at 7:53 PM Gilboa Davara  wrote:

> Hello all,
>
> During the night, one of my (smaller) setups, a single node self hosted
> engine (localhost NFS) crashed due to what-looks-like a massive disk
> failure (Software RAID6, with 10 drives + spare).
> After a reboot, I let the RAID resync with a fresh drive) and went on to
> start oVirt.
> However, no such luck.
> Two issues:
> 1. ovirt-ha-broker fails due to broken hosted engine state (log attached).
> 2. ovirt-ha-agent fails due to network test (tcp) even though both
> remote-host and DNS servers are active. (log attached).
>
> Two questions:
> 1. Can I somehow force the agent to disable the network liveliness test?
> 2. Can I somehow force the broker to rebuild / fix the hosted engine state?
>
> - Gilboa
>

FWIW switching agent network test to none (via hosted-engine
--set-shared-config network_test none --type=he_local) doesn't seem to work.
(Unless I'm missing the point and the agent is failing due to broker issues
and not due to a failed network liveliness check).

- Gilboa
___
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/OH4H5K2FZXO6YNVFU6W3XL7NHW6N5LAU/


[ovirt-users] Cannot restart ovirt after massive failure.

2021-08-08 Thread Gilboa Davara
Hello all,

During the night, one of my (smaller) setups, a single node self hosted
engine (localhost NFS) crashed due to what-looks-like a massive disk
failure (Software RAID6, with 10 drives + spare).
After a reboot, I let the RAID resync with a fresh drive) and went on to
start oVirt.
However, no such luck.
Two issues:
1. ovirt-ha-broker fails due to broken hosted engine state (log attached).
2. ovirt-ha-agent fails due to network test (tcp) even though both
remote-host and DNS servers are active. (log attached).

Two questions:
1. Can I somehow force the agent to disable the network liveliness test?
2. Can I somehow force the broker to rebuild / fix the hosted engine state?

- Gilboa


hosted_log_config.tgz
Description: application/compressed-tar
___
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/LG5WEGGIDJIZSRCHSZLY2UUSVFBW6GTN/


[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-08-04 Thread Gilboa Davara
On Tue, Aug 3, 2021 at 3:18 PM  wrote:

> Yes - local as in 5400 RPM SATA - standard desktop, slow storage.. :)
>
> It's still 'slow' being 5400 RPM SATA, but after setting the new VM to
> 'VirtIO-SCSI' and loading the driver, the performance is 'as expected'. I
> don't notice with with the Linux VMs because they don't do anything that
> requires a lot of disk I/O. Mostly Ansible/Python education and such.
>
> https://i.postimg.cc/28f764yb/Untitled.png
>
> I actually have some super fast Serial SCSI SSD drives I am going to use
> in the future. A storage vendor where I worked at ordered a bunch by
> mistake to upgrade our storage array and then left them sitting on-site for
> like 9 months. I contacted them to remind them we still had them in our
> data center and asked if they wanted to come and get them. I joked with our
> field engineer and told him if they didn't want them, I could find a use
> for them! He actually contacted his manager who gave us approval to just
> 'dispose' of them. So I thought why not recycle them? :)
>
> I'm in the process of moving soon for a new job. Once I get settled, I'm
> going to upgrade the storage I use for VMs. Either to those SSDs or maybe a
> small NAS device. Ideally.. a NAS device that can support Serial SCSI. I'll
> need to get a controller and a cable for them, but considering the
> performance... it should be well worth it. And no - I didn't get fired for
> swiping the drives! Too many years invested in IT for something that stupid
> and I'm just not that kind of person anyway. I took a position that's a bit
> more 'administrative' and less technical; but with better pay, so I want to
> keep my tech skills sharp, just because I enjoy it.
>
> This is just a 'home lab' - nothing that supports anything even remotely
> important. I'm so used to SSD now.. my desktop OS is on SSD, my CentOS
> machine is on SSD.. putting Windows on spinning platters is just painful
> anymore!
>

While I do have big oVirt setups running on pure SSD storage, I must admit
that Windows (and Linux VMs) are perfectly usable on HDD software RAIDs,
*if* everything is configured correctly (and you have a lot of RAM).
E.g. I'm typing this message on a Fedora VM running (w/ VFIO + nVidia GPU +
USB passthrough) on a pretty beefy 8 y/o Xeon machine with 6 x 2TB MDRAID
and ~10 other VMs (including Windows), and unless multiple VMs are trashing
the disks, I get near bare-metal performance. (I even run 3D games on this
VM...)

- Gilboa


> ___
> 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/5EVF6FR7Z46A2PI26EYJGBJBFF7LUGVX/
>
___
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/IV3WQFRI3FDXBCFRLGOEWLLKURY6SGTH/


[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-08-04 Thread Gilboa Davara
On Tue, Aug 3, 2021 at 12:24 PM Tony Pearce  wrote:

> I believe "local" in this context is using the local ovirt Host OS disk as
> VM storage ie "local storage". The disk info mentioned "WDC WD40EZRZ-00G" =
> a single 4TB disk, at 5400RPM.
>
> OP the seek time on that disk will be high. How many VMs are running off
> it?
>
> Are you able to try other storage? If you could run some monitoring on the
> host, I'd expect to see low throughput and high delay on that disk.
>
> Regards,
>
> Tony Pearce
>
>
Stupid question:
I must be missing something.
AFAIR oVirt doesn't support local storage, one needs to choose localhost
NFS, single-host-Gluster to localhost-iSCSI.

Assuming I'm not mistaken, in my experience the type of storage domain used
has a considerable impact on performance, especially latency.
E.g. Running Bonnie++ on a Fedora Linux VM, single host GlusterFS has 2-3
times the latency of localhost NFS, and noticeably lower throughput.

Hence my question.
- Gilboa


>
> On Tue, 3 Aug 2021 at 16:54, Gilboa Davara  wrote:
>
>>
>> On Fri, Jul 30, 2021 at 5:17 PM  wrote:
>>
>>> This is a simple one desktop setup I use at home for being a nerd :)
>>>
>>> So it's a single host 'cluster' using local storage.
>>>
>>
>> Sorry for the late reply.
>> Define: local.
>> NFS, Gluster or ISCSI?
>>
>> - Gilboa
>>
>>
>>>
>>> Host Info:
>>> CentOS Linux 8 - 4.18.0-305.10.2.el8_4.x86_64 (I keep fairly well
>>> updated)
>>> Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz [Kaby Lake] {Skylake}, 14nm
>>> The disk it's on is: WDC WD40EZRZ-00G (5400 RPM platter disk) - it's not
>>> the fastest thing in the world, but it should be sufficient.
>>>
>>> VM info:
>>> Windows 10 Professional (Desktop not server)
>>> 6144 MB of RAM
>>> 2 Virtual CPUS
>>>  - Some settings I ran across for 'Performance' mode and a couple I had
>>> seen on some similar issues (the similar issues were quite dated)
>>> Running in headless mode
>>> I/O Threads enabled = 1
>>> Multi-Queues enabled
>>> Virt-IO-SCSI enabled
>>> Random Number generator enabled
>>> Added a custom property of 'viodiskcache' = writeback  (Didn't seem to
>>> make any significant improvement)
>>>
>>> As I type this though - I was going to add this link as it's what I
>>> followed to install the storage driver during the Windows install and then
>>> in the OS after that:
>>>
>>> https://access.redhat.com/solutions/17463
>>>
>>> I did notice something.. it says to create a new VM with the 'VirtIO
>>> disk interface' and I just noted my VM is setup as 'SATA'.
>>>
>>> Perhaps that is it. This is just my first attempt at running something
>>> other than a Linux Distro under oVirt. When I first installed the Windows
>>> guest, I didn't have the Virt-IO package downloaded initially. When Windows
>>> couldn't find a storage driver, I found this info out.
>>>
>>> I think I'll deploy a new Windows guest and try the 'VirtIO-SCSI'
>>> interface and see if my performance is any better. It's just a default
>>> install of Windows at this point, so that'll be easy. :)
>>>
>>> Will update this thread either way!
>>> ___
>>> 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/4YC5E3MRPKJPFAAQDCTH5CWGPTTN77SU/
>>>
>> ___
>> 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/CIZOXVW2N5ND4AW4DASH445WSUMVJ745/
>>
>
___
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/XPWV6AMPOGDLWUTS2FC6LKRNUJAXU7TP/


[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-08-03 Thread Gilboa Davara
On Fri, Jul 30, 2021 at 5:17 PM  wrote:

> This is a simple one desktop setup I use at home for being a nerd :)
>
> So it's a single host 'cluster' using local storage.
>

Sorry for the late reply.
Define: local.
NFS, Gluster or ISCSI?

- Gilboa


>
> Host Info:
> CentOS Linux 8 - 4.18.0-305.10.2.el8_4.x86_64 (I keep fairly well updated)
> Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz [Kaby Lake] {Skylake}, 14nm
> The disk it's on is: WDC WD40EZRZ-00G (5400 RPM platter disk) - it's not
> the fastest thing in the world, but it should be sufficient.
>
> VM info:
> Windows 10 Professional (Desktop not server)
> 6144 MB of RAM
> 2 Virtual CPUS
>  - Some settings I ran across for 'Performance' mode and a couple I had
> seen on some similar issues (the similar issues were quite dated)
> Running in headless mode
> I/O Threads enabled = 1
> Multi-Queues enabled
> Virt-IO-SCSI enabled
> Random Number generator enabled
> Added a custom property of 'viodiskcache' = writeback  (Didn't seem to
> make any significant improvement)
>
> As I type this though - I was going to add this link as it's what I
> followed to install the storage driver during the Windows install and then
> in the OS after that:
>
> https://access.redhat.com/solutions/17463
>
> I did notice something.. it says to create a new VM with the 'VirtIO disk
> interface' and I just noted my VM is setup as 'SATA'.
>
> Perhaps that is it. This is just my first attempt at running something
> other than a Linux Distro under oVirt. When I first installed the Windows
> guest, I didn't have the Virt-IO package downloaded initially. When Windows
> couldn't find a storage driver, I found this info out.
>
> I think I'll deploy a new Windows guest and try the 'VirtIO-SCSI'
> interface and see if my performance is any better. It's just a default
> install of Windows at this point, so that'll be easy. :)
>
> Will update this thread either way!
> ___
> 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/4YC5E3MRPKJPFAAQDCTH5CWGPTTN77SU/
>
___
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/CIZOXVW2N5ND4AW4DASH445WSUMVJ745/


[ovirt-users] Re: Terrible Disk Performance on Windows 10 VM

2021-07-29 Thread Gilboa Davara
On Wed, Jul 28, 2021 at 2:51 PM  wrote:

> I recently installed a Windows 10 VM under oVirt 4.4.5.11-1.el8
>
> Also installed the drivers using "virtio-win-1.9.16.iso" (Then
> re-installed them after updates just in case it helped)
>
> I found a similar complaint with VMWare (
> https://communities.vmware.com/t5/VMware-Workstation-Pro/vmware-workstation-100-disk-usage/td-p/2704870
> )
>
> So I looked into that and made a registry change for the AHCI controller,
> as well as setting the 'viodiskcache' to write-back (Seen in another thread
> on here) - those two changes seemed to help.. marginally. But not much at
> all.
>
> When I do just about anything, disk usage spikes to 100% and stays there
> for quite a while. Write speeds rarely break 100kb/sec.
>
> Not even sure what to look for next. My Linux VMs don't seem to have this
> issue and the host it's running on is barely working at all. CPU and memory
> stay close to unused. oVirt didn't show a lot, but in task manager in the
> Windows VM - you can see disk queue just pegged completely.
>
> I've given the VM 6GB of RAM, so that's not it. I even turned off paging
> in the Windows VM as well, to no avail.
>
> This is an example of disk usage, just opening 'Groove Music' for the
> first time.
>
> https://i.postimg.cc/FRLq28Mw/Disk-Activity.png
>
>
>
> Any ideas? :)
>

Hello,

I've got a number of Windows 7/8/10 and 16 VMs running on a number of
different oVirt clusters, ranging from single host setups (NFS localhost
storage) up to multiple-host setups (Gluster storage) and I'm not seeing
any performance issues.
Can you share additional information concerning the host, storage and VM
configuration?

- Gilboa
___
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/67XKNSXGPZ3CUFOVM7SO7UL34IMZVJW6/


[ovirt-users] Re: Centos 8 to Centos Stream

2021-05-26 Thread Gilboa Davara
On Thu, May 20, 2021 at 9:49 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno mer 19 mag 2021 alle ore 17:02 Gilboa Davara 
> ha scritto:
>
>> On Wed, May 19, 2021 at 12:50 PM Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il giorno mer 19 mag 2021 alle ore 10:25  ha
>>> scritto:
>>>
>>>> Hi,
>>>> in preparation for upgrade of stand alone engine from centos 8 to
>>>> centos stream, I would like to know if exist a procedure to follow for this
>>>> operation or I must only follow the instruction on CentOS official site. 
>>>> [1]
>>>
>>>
>>>
>>> CentOS procedure is correct. Only addition is after upgrading to Stream
>>> re-install the ovirt-release44 rpm
>>>
>>
>> Both on host(s) and hosted engine? In what order?
>>
>> - Gilboa
>>
>
> I would start with the engine but order shouldn't really matter here.
>
>
Thanks.
I'll give it a try on one of my test machines / clusters.

- Gilboa
___
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/D2TAOQZNIVZIFYBOQYRBRN3FS4GYZSOU/


[ovirt-users] Re: Centos 8 to Centos Stream

2021-05-19 Thread Gilboa Davara
On Wed, May 19, 2021 at 12:50 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno mer 19 mag 2021 alle ore 10:25  ha scritto:
>
>> Hi,
>> in preparation for upgrade of stand alone engine from centos 8 to centos
>> stream, I would like to know if exist a procedure to follow for this
>> operation or I must only follow the instruction on CentOS official site. [1]
>
>
>
> CentOS procedure is correct. Only addition is after upgrading to Stream
> re-install the ovirt-release44 rpm
>

Both on host(s) and hosted engine? In what order?

- Gilboa
___
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/75JBFPQJ6DTURHAEEDTSNYZN6WCEEG3R/


[ovirt-users] Upgrading single host ovirt "clusters" to v4.5 via command line?

2021-04-19 Thread Gilboa Davara
Hello all,

As the title suggests I have a couple of single-host hyper converged
setups, mostly used for testing.
As I cannot use the GUI cluster upgrade method on a single host (it
requires me to reboot the host, which will require me to shutdown the
hosted engine), is there any method to upgrade the cluster / data-center
via command line in maintenance=global mode?

Beyond that, can I use the same method on my production setups?
(multi-node, gluster based setups).

Thanks,
Gilboa
___
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/LKYRV4UVOKFTFW37VMAEODQQQBJBES3F/


[ovirt-users] Re: The best HCI config with 8Nodes and 2 sites?

2021-03-23 Thread Gilboa Davara
On Tue, Mar 23, 2021 at 6:42 PM Arman Khalatyan  wrote:
>
> Hello everybody,
> I would like to deploy HCI with our 2 buildings each with 8 compute nodes.
> Each host has a mirrored OS disks and 1 slot for the SSD. So I will use SSD 
> for the glusterfs.
> my question is what is the best type of the glusterfs volume?
> I can leave with 8way mirror but what happened if the connection between 
> buildings will go down?
> where will my ovirt-engine start?

I'd start by asking a simple question: Is there any solid reason to do
an 8-way cross building gluster cluster?
Beyond the unbelievable waste of space (8 way mirror) that can only be
solved by creating a complex setup of alternating normal and arbiter
gluster bricks, you are also literally opening yourself to countless
gluster stability and performance problems due to semi-reliable
cross-building network link(s).
In-short, unless you really, really, really need an 8 way mirror,
simply don't do it.

If I were you, I'd go with the much simpler and better solution of
creating two separate clusters, one in every building, making sure
each VM has an active version in one cluster and a recent backup in
the other (and vice versa).

- Gilboa
___
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/PUYQI5WTJ5CJULQFYSVOBNOYW5FUUAWH/


[ovirt-users] Re: 2 Node oVirt Cluster

2021-03-01 Thread Gilboa Davara
On Mon, Mar 1, 2021 at 3:05 PM  wrote:
> Yes That was my goal! But isn't it using this: 
> https://github.com/gluster/gluster-ansible playbook? And it is supposed to 
> work on debian/ubuntu based oses. So if all prerequesites are met, shouldn't 
> it work?

Never tried using a playbook to setup a Gluster cluster. Can't comment on that.
BTW, which distribution is used on the RPI? are you certain the RPI
and oVirt hosts have the same Gluster versions?

> Is the hosted-engine HA then? How about updates, is it retaining the config?

The Gluster takes care of the storage HA. The two oVirt nodes, if
setup correctly, will handle the oVirt HA.

> I do have a PI 4. Wouldn't that be alright for an arbiter node? Since it's 
> just saving metadata. My nodes are connected via 10Gig btw

In general, In my experience Gluster is very sensitive to network
latency. The RPI, even the RPI4, has a lousy CPU and lousy network.
Given the fact that Gluster depends on the performance of the weakest
link in the chain, the 10GbE links between the nodes may go unused,
while the RPI will start throttling down...
If I were you, I'd get a mATX with a low end i3 or AMD CPU (even
second hand will do), connect a 10GbE link (ebay is your friend...),
and use it as an arbiter. (As an added bonus it can be part of the
oVirt HA cluster and even run a VM or two).

- Gilboa
___
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/JKGRBD4L7LJB3TEBJ26UGASGCVVAGUPL/


[ovirt-users] Re: 2 Node oVirt Cluster

2021-02-28 Thread Gilboa Davara
On Wed, Feb 24, 2021 at 9:08 AM  wrote:
>
> Hey there,
>
> I tried using oVirt for some time now and like to convert my main Proxmox 
> Cluster (2 Nodes + RPI for Quorum) to oVirt. But I obvioulsy need three 
> servers to do HA. Now I am asking myself: can't I just use the PI as an 
> arbiter node for the Selfhosted-Engine on gluster? I tried running the 
> playbook already, but it's always failing and even if the gluster deployment 
> would go through, it would most likely fail aftwards, right?
> Before I waste too much energy and time into that, does anyone of you guys 
> use a 2 node cluster? And no I can't add another node (energy + space + 
> money)!
> Also I know with doing that I'm totally on my own etcetera
>
> 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/EYIIHKLPK42OVKPU5CMYIWNTSLLOKCEJ/

I usually create the gluster shares by hand and then deploy oVirt on
each node using the pre-existing gluster shares.
There's no reason it won't work for you.
That said, I never had  a situation in which one of the gluster
members isn't also a member of the oVirt cluster.

Oh, which RPI is it? Are you sure its networking is up to the task?
(RPI3 has a terrible NIC, RPI4 isn't much better).

- Gilboa
___
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/VN7VPW3CSSX6PWNAB3Z4DEPSOHIJKYTP/


[ovirt-users] Re: 2021 first ovirt network question

2021-01-11 Thread Gilboa Davara
Hello,

As far as I know, spice doesn't support GPU acceleration on the host. Its
CPU only. The vGPU option in the host configuration only works for specific
enterprise grade GPUs.

At least in my experience, spice performance is limited by three different
parameters:
A. Bandwidth. B. Network latency. C. Host CPU utilization.

BTW, I just fired up ~20 virt-viewer windows, ~1/3 of them GUI w/ 2K
resolution, over a 10GbE link and performance was OK, and network
utilization was well below 1GbE.

- Gilboa

On Mon, Jan 11, 2021 at 10:00 AM  wrote:

> Thanks for all,
> Clients have 1Gb and iperf3 results are 900Mb per client, if multiple
> client run at same time.
> I think client and server network is ok.
>
> I've figured out something else.
> On Host setting there is an option for "console and gpu". separated or
> consolidated.
> It's made me suspected that the issue might come from this.
>
> I've checked my gpu which is onboard
>
>  lshw -C Display
>   *-display
>description: VGA compatible controller
>product: MGA G200eH3
>vendor: Matrox Electronics Systems Ltd.
>physical id: 0.1
>bus info: pci@:01:00.1
>logical name: /dev/fb0
>version: 02
>width: 32 bits
>clock: 33MHz
>capabilities: pm msi pciexpress vga_controller bus_master cap_list
> rom fb
>configuration: depth=32 driver=mgag200 latency=0 resolution=1024,768
>resources: irq:17 memory:d800-d8ff memory:d9b98000-d9b9bfff
> memory:d900-d97f memory:c-d
>
> Spice uses gpu, RDP uses cpu.
> So, maybe if i change my primary gpu with some powerful one it can effect
> spice in a good way
>
> What do you think about that?
> ___
> 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/HYEKRGLHSCXXQSJTAHVE2N7DTSO5HUZH/
>
___
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/CR3X23X4AADJLAVXUUKSE3ZBHBHDOUCV/


[ovirt-users] Re: 2021 first ovirt network question

2021-01-09 Thread Gilboa Davara
Hello,

Can you run iperf3 simultaneously on multiple clients?
The idea is simple, check that indeed you are getting more than 5-10GbE
aggregated bandwidth in/from the machine.

As for comparing the performance to rdp - I'm not sure you are comparing
apples to apples. As far as I remember, by default rdp clients drop the
quality of the display when faced with limited bandwidth. No sure
virt-viewer can do the same (I'll let the kind people @RedHat confirm deny
the above).
Either, I'd suggest you start by verifying that you are indeed getting
10GbE from the clients to the display network.

- Gilboa



On Thu, Jan 7, 2021 at 4:14 PM  wrote:

> Thanks for advice.
> Here is the iperf3 test results
>
> Connecting to host xyz.example.com, port 6000
> [  4] local XXX.XXX.XXX.XXX port 36140 connected to XYZ.XYZ.XYZ.XYZ port
> 6000
> [ ID] Interval   Transfer Bandwidth   Retr  Cwnd
> [  4]   0.00-1.00   sec  81.9 MBytes   687 Mbits/sec0352 KBytes
>
> [  4]   1.00-2.00   sec  80.5 MBytes   676 Mbits/sec0352 KBytes
>
> [  4]   2.00-3.00   sec  80.5 MBytes   676 Mbits/sec0362 KBytes
>
> [  4]   3.00-4.00   sec  79.8 MBytes   669 Mbits/sec0362 KBytes
>
> [  4]   4.00-5.00   sec  80.6 MBytes   676 Mbits/sec0362 KBytes
>
> [  4]   5.00-6.00   sec  82.0 MBytes   688 Mbits/sec0362 KBytes
>
> [  4]   6.00-7.00   sec  81.3 MBytes   682 Mbits/sec0362 KBytes
>
> [  4]   7.00-8.00   sec  80.5 MBytes   676 Mbits/sec0362 KBytes
>
> [  4]   8.00-9.00   sec  80.5 MBytes   676 Mbits/sec0362 KBytes
>
> [  4]   9.00-10.00  sec  79.8 MBytes   669 Mbits/sec0362 KBytes
>
> Actually, what i was trying to ask is is there any reletion between
> "default route" and "display" network on oVirt network.
> Because, if there is, it might be the source of the problem.
> As i wrote above, my "ovirtmanagement" and "default route"  network on the
> 1Gb port
> ___
> 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/TPQXDGMQOVCO2FFBOW2S5G4AVPSIZ2ZB/
>
___
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/ONJ74IDXUKZT2TEK7QKJNUEUUECGGU4H/


[ovirt-users] Re: 2021 first ovirt network question

2021-01-06 Thread Gilboa Davara
Sadly enough we never had more than 20+ concurrent spice connections and
most of them were text consoles. In this case, our 40/10GbE link(s) were
mostly idle.
That said, there's a vast difference between spice displaying VGA
resolution and spice displaying 2K/4K resolution.
Hence my question about the type of VMs and by extension, the resolution
used.

BTW, stupid question: Have you tried running iperf3 (or a similar tool)
between your client machines and the oVirt cluster to verify that indeed
you have 10GbE of usable bandwith?

- Gilboa

On Wed, Jan 6, 2021 at 10:58 AM  wrote:

> Concurrent spice connection.
> Today 75 VM i exist and all use spice connection
>
> Thanks for your interest
> ___
> 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/MIXL57E6XTRLUFPZC2OKLVTMDET7XQBV/
>
___
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/HDKCLTPZ2F2O3HJZXIWPIKUGHUKCHZPP/


[ovirt-users] Re: 2021 first ovirt network question

2021-01-05 Thread Gilboa Davara
Hello,

On Mon, Jan 4, 2021 at 8:41 AM  wrote:

> Hi,
> We're using oVirt as VDI solution for awhile.
> Infrastacture is 2 HPE Gen10 server with 80x2 Core cpu, 2TB RAM, 16GBX2 HBA
>
> For getting performance i've splited the networks on physical layer
> 2X10GB LACP for VM network
> 2X10GB LACP for Display(Spice) network
> 1GB for management + Default Route
>
> After 40 VMs spice connections start to be laggy.
> We've found our SAN storage I/O is bad and we'll change it SSD
> But, on the other hand, RDP connections is flawless.
> Now, we have 70 VMs and i need to solve this problem.
>
> Do you thing this is a network problem?
> We've also checked dropping packages on the switches, but found nothing.
> ___
>

40 concurrent spice connections or 40 active VMs?
What type of VMs?

- Gilboa
___
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/KXU2IAB45MP24NXQL7M5YL5EAQGXHJV7/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-31 Thread Gilboa Davara
Many thanks. Happy new year.

- Gilboa

On Wed, Dec 30, 2020 at 9:12 PM Strahil Nikolov 
wrote:

> Maybe there is a missing package that is preventing that.
> Let's see what the devs will find out next year (thankfully you wpn't have
> to wait much).
>
> Best Regards,
> Strahil Nikolov
>
>
>
>
>
>
> В сряда, 30 декември 2020 г., 16:30:37 Гринуич+2, Gilboa Davara <
> gilb...@gmail.com> написа:
>
>
>
>
>
> Short update.
> 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes.
> 2. Installed hosted engine on the first engine via hosted-engine --deploy
> (w/ gluster storage).
> 3. Added the two remaining hosts using host -> new -> w/ hosted engine ->
> deploy.
> 4. All machines are up and running and I can see theme in hosted-engine
> --vm-status and they all have a valid score (3400).
> 5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is
> still in 4.4 :/
>
> - Gilboa
>
> On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara  wrote:
> >
> >
> > On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov 
> wrote:
> >> Any hints in vdsm logs on the affected host or on the
> broker.log/agent.log ?
> >>
> >> Happy Hollidays to everyone!
> >>
> >> Best Regards,
> >> Strahil Nikolov
> >>
> >
> > Hello,
> >
> > Sorry for the late reply.
> > One of the nodes suffered a major failure and I'm waiting for the tech
> support to ship replacement parts.
> > Once it's up and running, I'll send the logs.
> >
> > Happy holidays!
> > - Gilboa
> >
> >
> >
> >>
> >> В 14:33 +0200 на 25.12.2020 (пт), Gilboa Davara написа:
> >>> Hello,
> >>>
> >>> Reinstall w/ redeploy produced the same results.
> >>>
> >>> - Gilboa
> >>>
> >>> On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov 
> wrote:
> >>>>>
> >>>>> I "forked" this email into a new subject ("Manually deploying a
> hyperconverged setup with an existing gluster bricks")
> >>>>> But nevertheless, no idea if its intended or not, but it seems that
> adding a host via "host->computer->create" doesn't create the necessary
> /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
> preventing ovirt-ha-* services from starting.
> >>>>>
> >>>>>
> >>>>
> >>>> So , set the host into maintenance and
> >>>> then select installation -> reinstall -> Hosted Engine -> Deploy
> >>>>
> >>>> Best Regards,
> >>>> Strahil Nikolov
> >>>>
> >>> ___Users mailing list --
> users@ovirt.orgTo unsubscribe send an email to
> users-leave@ovirt.orgPrivacy Statement:
> https://www.ovirt.org/privacy-policy.htmloVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHBX2LRHIPHRJFAPEX334PRUUYXRCCDB/
> >>
> >
>
___
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/ZTU5OEWK6BXCJS3YWEBWO7ZI7YN74U3I/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-30 Thread Gilboa Davara
Engine log attached. (Looks clean)

- Gilboa

On Wed, Dec 30, 2020 at 4:30 PM Gilboa Davara  wrote:

> Short update.
> 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes.
> 2. Installed hosted engine on the first engine via hosted-engine --deploy
> (w/ gluster storage).
> 3. Added the two remaining hosts using host -> new -> w/ hosted engine ->
> deploy.
> 4. All machines are up and running and I can see theme in hosted-engine
> --vm-status and they all have a valid score (3400).
> 5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is
> still in 4.4 :/
>
> - Gilboa
>
> On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara  wrote:
>
>>
>> On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov 
>> wrote:
>>
>>> Any hints in vdsm logs on the affected host or on the
>>> broker.log/agent.log ?
>>>
>>> Happy Hollidays to everyone!
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>>
>> Hello,
>>
>> Sorry for the late reply.
>> One of the nodes suffered a major failure and I'm waiting for the tech
>> support to ship replacement parts.
>> Once it's up and running, I'll send the logs.
>>
>> Happy holidays!
>> - Gilboa
>>
>>
>>
>>
>>> В 14:33 +0200 на 25.12.2020 (пт), Gilboa Davara написа:
>>>
>>> Hello,
>>>
>>> Reinstall w/ redeploy produced the same results.
>>>
>>> - Gilboa
>>>
>>> On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov 
>>> wrote:
>>>
>>>
>>> I "forked" this email into a new subject ("Manually deploying a
>>> hyperconverged setup with an existing gluster bricks")
>>> But nevertheless, no idea if its intended or not, but it seems that
>>> adding a host via "host->computer->create" doesn't create the necessary
>>> /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
>>> preventing ovirt-ha-* services from starting.
>>>
>>>
>>> So , set the host into maintenance and
>>> then select installation -> reinstall -> Hosted Engine -> Deploy
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> ___
>>>
>>> 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/KHBX2LRHIPHRJFAPEX334PRUUYXRCCDB/
>>>
>>>
>>>


engine.log.bz2
Description: application/bzip
___
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/QJAGGPRST3HROLUQ5GRVAFIYJO63VWGF/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-30 Thread Gilboa Davara
Short update.
1. Ran ovirt-hosted-engine-cleanup on all 3 nodes.
2. Installed hosted engine on the first engine via hosted-engine --deploy
(w/ gluster storage).
3. Added the two remaining hosts using host -> new -> w/ hosted engine ->
deploy.
4. All machines are up and running and I can see theme in hosted-engine
--vm-status and they all have a valid score (3400).
5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is
still in 4.4 :/

- Gilboa

On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara  wrote:

>
> On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov 
> wrote:
>
>> Any hints in vdsm logs on the affected host or on the
>> broker.log/agent.log ?
>>
>> Happy Hollidays to everyone!
>>
>> Best Regards,
>> Strahil Nikolov
>>
>>
> Hello,
>
> Sorry for the late reply.
> One of the nodes suffered a major failure and I'm waiting for the tech
> support to ship replacement parts.
> Once it's up and running, I'll send the logs.
>
> Happy holidays!
> - Gilboa
>
>
>
>
>> В 14:33 +0200 на 25.12.2020 (пт), Gilboa Davara написа:
>>
>> Hello,
>>
>> Reinstall w/ redeploy produced the same results.
>>
>> - Gilboa
>>
>> On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov 
>> wrote:
>>
>>
>> I "forked" this email into a new subject ("Manually deploying a
>> hyperconverged setup with an existing gluster bricks")
>> But nevertheless, no idea if its intended or not, but it seems that
>> adding a host via "host->computer->create" doesn't create the necessary
>> /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
>> preventing ovirt-ha-* services from starting.
>>
>>
>> So , set the host into maintenance and
>> then select installation -> reinstall -> Hosted Engine -> Deploy
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> ___
>>
>> 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/KHBX2LRHIPHRJFAPEX334PRUUYXRCCDB/
>>
>>
>>
___
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/2KSNS5ZHKLHKA4QCSP4G4PBRCRBWLCTP/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-28 Thread Gilboa Davara
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov 
wrote:

> Any hints in vdsm logs on the affected host or on the broker.log/agent.log
> ?
>
> Happy Hollidays to everyone!
>
> Best Regards,
> Strahil Nikolov
>
>
Hello,

Sorry for the late reply.
One of the nodes suffered a major failure and I'm waiting for the tech
support to ship replacement parts.
Once it's up and running, I'll send the logs.

Happy holidays!
- Gilboa




> В 14:33 +0200 на 25.12.2020 (пт), Gilboa Davara написа:
>
> Hello,
>
> Reinstall w/ redeploy produced the same results.
>
> - Gilboa
>
> On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov 
> wrote:
>
>
> I "forked" this email into a new subject ("Manually deploying a
> hyperconverged setup with an existing gluster bricks")
> But nevertheless, no idea if its intended or not, but it seems that adding
> a host via "host->computer->create" doesn't create the necessary
> /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
> preventing ovirt-ha-* services from starting.
>
>
> So , set the host into maintenance and
> then select installation -> reinstall -> Hosted Engine -> Deploy
>
> Best Regards,
> Strahil Nikolov
>
> ___
>
> 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/KHBX2LRHIPHRJFAPEX334PRUUYXRCCDB/
>
>
>
___
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/UEKOJEEDKPVBIBJDRYRHCSDGLROBZDF3/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-25 Thread Gilboa Davara
Hello,

Reinstall w/ redeploy produced the same results.

- Gilboa

On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov 
wrote:

>
> I "forked" this email into a new subject ("Manually deploying a
> hyperconverged setup with an existing gluster bricks")
> But nevertheless, no idea if its intended or not, but it seems that adding
> a host via "host->computer->create" doesn't create the necessary
> /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
> preventing ovirt-ha-* services from starting.
>
>
> So , set the host into maintenance and
> then select installation -> reinstall -> Hosted Engine -> Deploy
>
> Best Regards,
> Strahil Nikolov
>
___
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/KHBX2LRHIPHRJFAPEX334PRUUYXRCCDB/


[ovirt-users] Re: Manually deploying a hyperconverged setup with an existing gluster bricks (Was: Cannot upgrade cluster to v4.5)

2020-12-24 Thread Gilboa Davara
P.S. When creating a host, "Choose hosted engine deployment action" was set
to "deploy".

- Gilboa

On Thu, Dec 24, 2020 at 4:53 PM Gilboa Davara  wrote:

> Hello all,
>
> Found the problem (at least I think so), but not the solution.
> As I have an existing Gluster setup (quite complex one) this was the first
> time I didn't use the "Hyperconverged gluster wizard" (via cockpit), but
> used the "hosted-engine --deploy" cli instead (which I usually use to
> deploy single host setups).
> The idea being: Deploy the first hosts (via cli) and then add the two
> additional hosts via compute->host->create.
> For some odd reason I seem to remember this method was an approved way of
> deploying an hyperconverged gluster setup, in cases you don't want to let a
> wizard create the gluster bricks. Am I wrong?
>
> A. In case I'm wrong: How can I deploy a 3 host hyperconverged setup,
> _while_ using the preexisting gluster bricks (data/export/iso)?
>
> B. I did a clean redeploy (via cockpit -> hosted engine -> hosted engine
> deploy) and the cluster version is still 4.4 (and given the fact it only
> deploys a single host, there's no way to upgrade it to 4.5, as I cannot put
> the host into maintenance and I cannot add additional hosts).
>
> - Gilboa
>
>
>
> On Thu, Dec 24, 2020 at 12:50 PM Strahil Nikolov 
> wrote:
>
>> Are you sure you have installed them with HE support ?
>>
>> Best Regards,
>> Strahil Nikolov
>> В 19:06 +0200 на 23.12.2020 (ср), Gilboa Davara написа:
>>
>>
>> On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara  wrote:
>>
>>
>>
>> On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara  wrote:
>>
>> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola 
>> wrote:
>>
>>
>>
>> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara 
>> ha scritto:
>>
>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina  wrote:
>>
>>
>>
>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara  wrote:
>>
>> Thanks for the prompt reply.
>> I assume I can safely ignore the "Upgrade cluster compatibility" warning
>> until libvirt 6.6 gets pushed to CentOS 8.3?
>>
>>
>> We are working on releasing AV 8.3, hopefully it will be available soon,
>> but until that happen you have no way how to upgrade to CL 4.5 and you just
>> need to stay in 4.4
>>
>>
>> Understood.
>>
>> Thanks again.
>> - Gilboa
>>
>>
>>
>> Just updating that oVirt 4.4.4 released yesterday comes with Advanced
>> Virtualization 8.3 so you can now enable CL 4.5.
>>
>>
>> Sadly enough, even post-full-upgrade (engine + hosts) something seems to
>> be broken.
>>
>> In the WebUI, I see all 3 hosts marked as "up".
>> But when I run hosted-engine --vm-status (or migrate the hosted engine),
>> only the first (original deployed) host is available.
>> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
>> change.
>> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
>> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>>
>> Any idea what's broken?
>>
>> - Gilboa
>>
>>
>>
>> I'll remove the problematic hosts, re-add them, and reconfigure the
>> network(s). Let's see if it works.
>>
>> - Gilboa
>>
>>
>>
>> Sorry for the noise. No go.
>> Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried
>> "adding" them again, to no avail.
>> Host marked as "up" in WebUI, network correctly configured, however,
>> hosted-engine.conf isn't being created (see log below),
>> ovirt-ha-broker/agent services cannot start and vm-status only shows one
>> host.
>>
>> - Gilboa
>>
>> ___
>>
>> 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/2JEBBBCTAB5JV2LR42JSHQWDKBU3NR5J/
>>
>>
>>
___
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/IELVBEGLCDRU4KSOY4KFCMIUZBWEGQOL/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-24 Thread Gilboa Davara
On Thu, Dec 24, 2020 at 5:04 PM Gilboa Davara  wrote:

> Hello,
>
> On Thu, Dec 24, 2020 at 12:45 PM Strahil Nikolov 
> wrote:
>
>> In the WebUI, I see all 3 hosts marked as "up".
>> But when I run hosted-engine --vm-status (or migrate the hosted engine),
>> only the first (original deployed) host is available.
>> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
>> change.
>> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
>> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>>
>>
>> Start debugging from the hosts that are not seen via "hosted-engine
>> --vm-status".
>> There are 2 log files to check:
>> /var/log/ovirt-hosted-engine-ha/{broker,agent}.log
>>
>> Just check what they are complaining about.
>> Also , you need both ovirt-ha-broker.service and ovirt-ha-agent.service
>> up and running. If there is an issue, the ovirt-ha-agent is being restarted
>> (so it's expected behaviour).
>>
>> Usually the broker should stop complaining and then the agent will kick
>> in.
>>
>>
>> Best Regards,
>> Strahil Nikolov
>>
>
> I "forked" this email into a new subject ("Manually deploying a
> hyperconverged setup with an existing gluster bricks")
> But nevertheless, no idea if its intended or not, but it seems that adding
> a host via "host->computer->create" doesn't create the necessary
> /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
> preventing ovirt-ha-* services from starting.
>
> Thanks,
> Gilboa
>

Typo: ...it seems that adding a host via "Compute -> Host > Create"

- Gilboa
___
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/5CXPXXBJHA6OAQZTXCF3VVTAYWANEUXC/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-24 Thread Gilboa Davara
Hello,

On Thu, Dec 24, 2020 at 12:45 PM Strahil Nikolov 
wrote:

> In the WebUI, I see all 3 hosts marked as "up".
> But when I run hosted-engine --vm-status (or migrate the hosted engine),
> only the first (original deployed) host is available.
> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
> change.
> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>
>
> Start debugging from the hosts that are not seen via "hosted-engine
> --vm-status".
> There are 2 log files to check:
> /var/log/ovirt-hosted-engine-ha/{broker,agent}.log
>
> Just check what they are complaining about.
> Also , you need both ovirt-ha-broker.service and ovirt-ha-agent.service up
> and running. If there is an issue, the ovirt-ha-agent is being restarted
> (so it's expected behaviour).
>
> Usually the broker should stop complaining and then the agent will kick in.
>
>
> Best Regards,
> Strahil Nikolov
>

I "forked" this email into a new subject ("Manually deploying a
hyperconverged setup with an existing gluster bricks")
But nevertheless, no idea if its intended or not, but it seems that adding
a host via "host->computer->create" doesn't create the necessary
/etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts,
preventing ovirt-ha-* services from starting.

Thanks,
Gilboa
___
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/EO5A6PN5EYYD2KIDGK7MIDGK3KNZTVQ6/


[ovirt-users] Manually deploying a hyperconverged setup with an existing gluster bricks (Was: Cannot upgrade cluster to v4.5)

2020-12-24 Thread Gilboa Davara
Hello all,

Found the problem (at least I think so), but not the solution.
As I have an existing Gluster setup (quite complex one) this was the first
time I didn't use the "Hyperconverged gluster wizard" (via cockpit), but
used the "hosted-engine --deploy" cli instead (which I usually use to
deploy single host setups).
The idea being: Deploy the first hosts (via cli) and then add the two
additional hosts via compute->host->create.
For some odd reason I seem to remember this method was an approved way of
deploying an hyperconverged gluster setup, in cases you don't want to let a
wizard create the gluster bricks. Am I wrong?

A. In case I'm wrong: How can I deploy a 3 host hyperconverged setup,
_while_ using the preexisting gluster bricks (data/export/iso)?

B. I did a clean redeploy (via cockpit -> hosted engine -> hosted engine
deploy) and the cluster version is still 4.4 (and given the fact it only
deploys a single host, there's no way to upgrade it to 4.5, as I cannot put
the host into maintenance and I cannot add additional hosts).

- Gilboa



On Thu, Dec 24, 2020 at 12:50 PM Strahil Nikolov 
wrote:

> Are you sure you have installed them with HE support ?
>
> Best Regards,
> Strahil Nikolov
> В 19:06 +0200 на 23.12.2020 (ср), Gilboa Davara написа:
>
>
> On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara  wrote:
>
>
>
> On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara  wrote:
>
> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola 
> wrote:
>
>
>
> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara 
> ha scritto:
>
> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina  wrote:
>
>
>
> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara  wrote:
>
> Thanks for the prompt reply.
> I assume I can safely ignore the "Upgrade cluster compatibility" warning
> until libvirt 6.6 gets pushed to CentOS 8.3?
>
>
> We are working on releasing AV 8.3, hopefully it will be available soon,
> but until that happen you have no way how to upgrade to CL 4.5 and you just
> need to stay in 4.4
>
>
> Understood.
>
> Thanks again.
> - Gilboa
>
>
>
> Just updating that oVirt 4.4.4 released yesterday comes with Advanced
> Virtualization 8.3 so you can now enable CL 4.5.
>
>
> Sadly enough, even post-full-upgrade (engine + hosts) something seems to
> be broken.
>
> In the WebUI, I see all 3 hosts marked as "up".
> But when I run hosted-engine --vm-status (or migrate the hosted engine),
> only the first (original deployed) host is available.
> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
> change.
> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>
> Any idea what's broken?
>
> - Gilboa
>
>
>
> I'll remove the problematic hosts, re-add them, and reconfigure the
> network(s). Let's see if it works.
>
> - Gilboa
>
>
>
> Sorry for the noise. No go.
> Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried
> "adding" them again, to no avail.
> Host marked as "up" in WebUI, network correctly configured, however,
> hosted-engine.conf isn't being created (see log below),
> ovirt-ha-broker/agent services cannot start and vm-status only shows one
> host.
>
> - Gilboa
>
> ___
>
> 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/2JEBBBCTAB5JV2LR42JSHQWDKBU3NR5J/
>
>
>
___
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/FOKS6MJLCZVYZ2CIQ7R5ODBKHDNN2PYE/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-23 Thread Gilboa Davara
On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara  wrote:

>
>
> On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara  wrote:
>
>> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <
>>> gilb...@gmail.com> ha scritto:
>>>
>>>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina 
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara 
>>>>> wrote:
>>>>>
>>>>>> Thanks for the prompt reply.
>>>>>> I assume I can safely ignore the "Upgrade cluster compatibility"
>>>>>> warning until libvirt 6.6 gets pushed to CentOS 8.3?
>>>>>>
>>>>>
>>>>> We are working on releasing AV 8.3, hopefully it will be available
>>>>> soon, but until that happen you have no way how to upgrade to CL 4.5 and
>>>>> you just need to stay in 4.4
>>>>>
>>>>
>>>> Understood.
>>>>
>>>> Thanks again.
>>>> - Gilboa
>>>>
>>>>
>>>
>>> Just updating that oVirt 4.4.4 released yesterday comes with Advanced
>>> Virtualization 8.3 so you can now enable CL 4.5.
>>>
>>
>> Sadly enough, even post-full-upgrade (engine + hosts) something seems to
>> be broken.
>>
>> In the WebUI, I see all 3 hosts marked as "up".
>> But when I run hosted-engine --vm-status (or migrate the hosted engine),
>> only the first (original deployed) host is available.
>> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
>> change.
>> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
>> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>>
>> Any idea what's broken?
>>
>> - Gilboa
>>
>>
> I'll remove the problematic hosts, re-add them, and reconfigure the
> network(s). Let's see if it works.
>
> - Gilboa
>
>

Sorry for the noise. No go.
Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried
"adding" them again, to no avail.
Host marked as "up" in WebUI, network correctly configured, however,
hosted-engine.conf isn't being created (see log below),
ovirt-ha-broker/agent services cannot start and vm-status only shows one
host.

- Gilboa
___
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/2JEBBBCTAB5JV2LR42JSHQWDKBU3NR5J/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-23 Thread Gilboa Davara
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara  wrote:

> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara 
>> ha scritto:
>>
>>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara 
>>>> wrote:
>>>>
>>>>> Thanks for the prompt reply.
>>>>> I assume I can safely ignore the "Upgrade cluster compatibility"
>>>>> warning until libvirt 6.6 gets pushed to CentOS 8.3?
>>>>>
>>>>
>>>> We are working on releasing AV 8.3, hopefully it will be available
>>>> soon, but until that happen you have no way how to upgrade to CL 4.5 and
>>>> you just need to stay in 4.4
>>>>
>>>
>>> Understood.
>>>
>>> Thanks again.
>>> - Gilboa
>>>
>>>
>>
>> Just updating that oVirt 4.4.4 released yesterday comes with Advanced
>> Virtualization 8.3 so you can now enable CL 4.5.
>>
>
> Sadly enough, even post-full-upgrade (engine + hosts) something seems to
> be broken.
>
> In the WebUI, I see all 3 hosts marked as "up".
> But when I run hosted-engine --vm-status (or migrate the hosted engine),
> only the first (original deployed) host is available.
> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no
> change.
> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
> upgrade is successful; hosts1 fails (cannot migrate the hosted engine).
>
> Any idea what's broken?
>
> - Gilboa
>
>
I'll remove the problematic hosts, re-add them, and reconfigure the
network(s). Let's see if it works.

- Gilboa


>
>
>>
>>
>>>
>>>>> - Gilboa
>>>>>
>>>>> On Wed, Dec 16, 2020 at 5:56 PM Martin Perina 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara 
>>>>>> wrote:
>>>>>>
>>>>>>> Shani,
>>>>>>>
>>>>>>> 1. I created a new 4.5 cluster with the same CPU (Secure Intel
>>>>>>> Cascadelake Server Family) and platform type (Q35/BIOS).
>>>>>>> 2. All 3 hosts are 8.3, but report 4.4 compatibility.
>>>>>>> 3. The only reason I attempted to upgrade the cluster was simple:
>>>>>>> The cluster state kept on dropping down to "unavailable" (even though 
>>>>>>> all 3
>>>>>>> hosts are up) and I was offered to upgrade the cluster to v4.5.
>>>>>>>
>>>>>>> - Gilboa
>>>>>>>
>>>>>>> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Gilboa,
>>>>>>>>
>>>>>>>> Here are some guidelines/checks:
>>>>>>>> - Are you able to create a 4.5 DC/cluster?
>>>>>>>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level
>>>>>>>> compatibility (it's based on RHEL 8.3).
>>>>>>>>   Can you make sure that on all 3 hosts?
>>>>>>>> - You can upgrade the 4.4 clusters to 4.5 only when all
>>>>>>>> Up/NonOperational hosts are reporting 4.5 level
>>>>>>>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are
>>>>>>>> on the 4.5 level
>>>>>>>> - A 4.5 host-based on RHEL 8.3 should be fully functional in
>>>>>>>> 4.2/4.3/4.4 clusters
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *Regards,*
>>>>>>>>
>>>>>>>> *Shani Leviim*
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hello all,
>>>>>>>>>
>>>>>>>>> I'm more-or-less finished building a new ovirt over glusterfs
>>>>>>>>> cluster with 3 fairly beefy servers.
>>>>>>>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before
>>>>>>>>> they joined the cluster.
>>>>>>>>> Looking at the cluster view in the WebUI, I get an exclamation
>>>>>>>>> mark with the following message: "Upgrade cluster compatibility 
>>>>>>>>> level".
>>>>>>>>> When I try to upgrade the cluster, 2 of the 3 hosts go into
>>>>>>>>> maintenance and reboot, but once the procedure is complete, the 
>>>>>>>>> cluster
>>>>>>>>> version remains the same.
>>>>>>>>> Looking at the host vdsm logs, I see that once the engine
>>>>>>>>> refreshes their capabilities, all hosts return 4.2-4.4 and not 4.5.
>>>>>>>>>
>>>>>>>>> E.g.
>>>>>>>>>  'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels':
>>>>>>>>> ['4.2', '4.3', '4.4']
>>>>>>>>> I assume I should be seeing 4.5 after the upgrade, no?
>>>>>>>>>
>>>>>>>>> AmI missing something?
>>>>>>>>>
>>>>>>>>
>>>>>> EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in
>>>>>> particular libvirt 6.6)
>>>>>>
>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> - Gilboa
>>>>>>>>> ___
>>>>>>>>
>>>>>>>>
>>
>>
>>
___
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/7QHLUHA2LES6GD6Y7NLKNBKBGMDGBC2S/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-23 Thread Gilboa Davara
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola 
wrote:

>
>
> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara 
> ha scritto:
>
>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina  wrote:
>>
>>>
>>>
>>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara  wrote:
>>>
>>>> Thanks for the prompt reply.
>>>> I assume I can safely ignore the "Upgrade cluster compatibility"
>>>> warning until libvirt 6.6 gets pushed to CentOS 8.3?
>>>>
>>>
>>> We are working on releasing AV 8.3, hopefully it will be available soon,
>>> but until that happen you have no way how to upgrade to CL 4.5 and you just
>>> need to stay in 4.4
>>>
>>
>> Understood.
>>
>> Thanks again.
>> - Gilboa
>>
>>
>
> Just updating that oVirt 4.4.4 released yesterday comes with Advanced
> Virtualization 8.3 so you can now enable CL 4.5.
>

Sadly enough, even post-full-upgrade (engine + hosts) something seems to be
broken.

In the WebUI, I see all 3 hosts marked as "up".
But when I run hosted-engine --vm-status (or migrate the hosted engine),
only the first (original deployed) host is available.
I tried "reinstalling" (from the WebUI) the two hosts, no errors, no change.
I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts)
upgrade is successful; hosts1 fails (cannot migrate the hosted engine).

Any idea what's broken?

- Gilboa



>
>
>>
>>>> - Gilboa
>>>>
>>>> On Wed, Dec 16, 2020 at 5:56 PM Martin Perina 
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara 
>>>>> wrote:
>>>>>
>>>>>> Shani,
>>>>>>
>>>>>> 1. I created a new 4.5 cluster with the same CPU (Secure Intel
>>>>>> Cascadelake Server Family) and platform type (Q35/BIOS).
>>>>>> 2. All 3 hosts are 8.3, but report 4.4 compatibility.
>>>>>> 3. The only reason I attempted to upgrade the cluster was simple: The
>>>>>> cluster state kept on dropping down to "unavailable" (even though all 3
>>>>>> hosts are up) and I was offered to upgrade the cluster to v4.5.
>>>>>>
>>>>>> - Gilboa
>>>>>>
>>>>>> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Gilboa,
>>>>>>>
>>>>>>> Here are some guidelines/checks:
>>>>>>> - Are you able to create a 4.5 DC/cluster?
>>>>>>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level
>>>>>>> compatibility (it's based on RHEL 8.3).
>>>>>>>   Can you make sure that on all 3 hosts?
>>>>>>> - You can upgrade the 4.4 clusters to 4.5 only when all
>>>>>>> Up/NonOperational hosts are reporting 4.5 level
>>>>>>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on
>>>>>>> the 4.5 level
>>>>>>> - A 4.5 host-based on RHEL 8.3 should be fully functional in
>>>>>>> 4.2/4.3/4.4 clusters
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *Regards,*
>>>>>>>
>>>>>>> *Shani Leviim*
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hello all,
>>>>>>>>
>>>>>>>> I'm more-or-less finished building a new ovirt over glusterfs
>>>>>>>> cluster with 3 fairly beefy servers.
>>>>>>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before
>>>>>>>> they joined the cluster.
>>>>>>>> Looking at the cluster view in the WebUI, I get an exclamation mark
>>>>>>>> with the following message: "Upgrade cluster compatibility level".
>>>>>>>> When I try to upgrade the cluster, 2 of the 3 hosts go into
>>>>>>>> maintenance and reboot, but once the procedure is complete, the cluster
>>>>>>>> version remains the same.
>>>>>>>> Looking at the host vdsm logs, I see that once the engine refreshes
>>>>>>>> their capabilities, all hosts return 4.2-4.4 and not 4.5.
>>>>>>>>
>>>>>>>> E.g.
>>>>>>>>  'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels':
>>>>>>>> ['4.2', '4.3', '4.4']
>>>>>>>> I assume I should be seeing 4.5 after the upgrade, no?
>>>>>>>>
>>>>>>>> AmI missing something?
>>>>>>>>
>>>>>>>
>>>>> EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in
>>>>> particular libvirt 6.6)
>>>>>
>>>>>>
>>>>>>>> Thanks,
>>>>>>>> - Gilboa
>>>>>>>> ___
>>>>>>>
>>>>>>>
>
>
>
___
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/UWCTKKVX5VTRNHFDWAMCU76UTMLEKQE3/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-16 Thread Gilboa Davara
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina  wrote:

>
>
> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara  wrote:
>
>> Thanks for the prompt reply.
>> I assume I can safely ignore the "Upgrade cluster compatibility" warning
>> until libvirt 6.6 gets pushed to CentOS 8.3?
>>
>
> We are working on releasing AV 8.3, hopefully it will be available soon,
> but until that happen you have no way how to upgrade to CL 4.5 and you just
> need to stay in 4.4
>

Understood.

Thanks again.
- Gilboa


>
>> - Gilboa
>>
>> On Wed, Dec 16, 2020 at 5:56 PM Martin Perina  wrote:
>>
>>>
>>>
>>> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara  wrote:
>>>
>>>> Shani,
>>>>
>>>> 1. I created a new 4.5 cluster with the same CPU (Secure Intel
>>>> Cascadelake Server Family) and platform type (Q35/BIOS).
>>>> 2. All 3 hosts are 8.3, but report 4.4 compatibility.
>>>> 3. The only reason I attempted to upgrade the cluster was simple: The
>>>> cluster state kept on dropping down to "unavailable" (even though all 3
>>>> hosts are up) and I was offered to upgrade the cluster to v4.5.
>>>>
>>>> - Gilboa
>>>>
>>>> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim 
>>>> wrote:
>>>>
>>>>> Hi Gilboa,
>>>>>
>>>>> Here are some guidelines/checks:
>>>>> - Are you able to create a 4.5 DC/cluster?
>>>>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level
>>>>> compatibility (it's based on RHEL 8.3).
>>>>>   Can you make sure that on all 3 hosts?
>>>>> - You can upgrade the 4.4 clusters to 4.5 only when all
>>>>> Up/NonOperational hosts are reporting 4.5 level
>>>>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on
>>>>> the 4.5 level
>>>>> - A 4.5 host-based on RHEL 8.3 should be fully functional in
>>>>> 4.2/4.3/4.4 clusters
>>>>>
>>>>>
>>>>>
>>>>> *Regards,*
>>>>>
>>>>> *Shani Leviim*
>>>>>
>>>>>
>>>>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara 
>>>>> wrote:
>>>>>
>>>>>> Hello all,
>>>>>>
>>>>>> I'm more-or-less finished building a new ovirt over glusterfs cluster
>>>>>> with 3 fairly beefy servers.
>>>>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before
>>>>>> they joined the cluster.
>>>>>> Looking at the cluster view in the WebUI, I get an exclamation mark
>>>>>> with the following message: "Upgrade cluster compatibility level".
>>>>>> When I try to upgrade the cluster, 2 of the 3 hosts go into
>>>>>> maintenance and reboot, but once the procedure is complete, the cluster
>>>>>> version remains the same.
>>>>>> Looking at the host vdsm logs, I see that once the engine refreshes
>>>>>> their capabilities, all hosts return 4.2-4.4 and not 4.5.
>>>>>>
>>>>>> E.g.
>>>>>>  'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2',
>>>>>> '4.3', '4.4']
>>>>>> I assume I should be seeing 4.5 after the upgrade, no?
>>>>>>
>>>>>> AmI missing something?
>>>>>>
>>>>>
>>> EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in
>>> particular libvirt 6.6)
>>>
>>>>
>>>>>> Thanks,
>>>>>> - Gilboa
>>>>>> ___
>>>>>> 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/7CCUHPEGVZD3BBLBDTOCHG5J6EEG5DE2/
>>>>>>
>>>>> ___
>>>> 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/RMZ3S64FFIOFTRBQOWVTTLCRJJA65EMJ/
>>>>
>>>
>>>
>>> --
>>> Martin Perina
>>> Manager, Software Engineering
>>> Red Hat Czech s.r.o.
>>>
>>
>
> --
> Martin Perina
> Manager, Software Engineering
> Red Hat Czech s.r.o.
>
___
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/OEL5Y7UYBGLOTKVOTJ3Y5MPFX55FRO4P/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-16 Thread Gilboa Davara
Thanks for the prompt reply.
I assume I can safely ignore the "Upgrade cluster compatibility" warning
until libvirt 6.6 gets pushed to CentOS 8.3?

- Gilboa

On Wed, Dec 16, 2020 at 5:56 PM Martin Perina  wrote:

>
>
> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara  wrote:
>
>> Shani,
>>
>> 1. I created a new 4.5 cluster with the same CPU (Secure Intel
>> Cascadelake Server Family) and platform type (Q35/BIOS).
>> 2. All 3 hosts are 8.3, but report 4.4 compatibility.
>> 3. The only reason I attempted to upgrade the cluster was simple: The
>> cluster state kept on dropping down to "unavailable" (even though all 3
>> hosts are up) and I was offered to upgrade the cluster to v4.5.
>>
>> - Gilboa
>>
>> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim  wrote:
>>
>>> Hi Gilboa,
>>>
>>> Here are some guidelines/checks:
>>> - Are you able to create a 4.5 DC/cluster?
>>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level
>>> compatibility (it's based on RHEL 8.3).
>>>   Can you make sure that on all 3 hosts?
>>> - You can upgrade the 4.4 clusters to 4.5 only when all
>>> Up/NonOperational hosts are reporting 4.5 level
>>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on the
>>> 4.5 level
>>> - A 4.5 host-based on RHEL 8.3 should be fully functional in 4.2/4.3/4.4
>>> clusters
>>>
>>>
>>>
>>> *Regards,*
>>>
>>> *Shani Leviim*
>>>
>>>
>>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara 
>>> wrote:
>>>
>>>> Hello all,
>>>>
>>>> I'm more-or-less finished building a new ovirt over glusterfs cluster
>>>> with 3 fairly beefy servers.
>>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before they
>>>> joined the cluster.
>>>> Looking at the cluster view in the WebUI, I get an exclamation mark
>>>> with the following message: "Upgrade cluster compatibility level".
>>>> When I try to upgrade the cluster, 2 of the 3 hosts go into maintenance
>>>> and reboot, but once the procedure is complete, the cluster version remains
>>>> the same.
>>>> Looking at the host vdsm logs, I see that once the engine refreshes
>>>> their capabilities, all hosts return 4.2-4.4 and not 4.5.
>>>>
>>>> E.g.
>>>>  'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2',
>>>> '4.3', '4.4']
>>>> I assume I should be seeing 4.5 after the upgrade, no?
>>>>
>>>> AmI missing something?
>>>>
>>>
> EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in
> particular libvirt 6.6)
>
>>
>>>> Thanks,
>>>> - Gilboa
>>>> ___
>>>> 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/7CCUHPEGVZD3BBLBDTOCHG5J6EEG5DE2/
>>>>
>>> ___
>> 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/RMZ3S64FFIOFTRBQOWVTTLCRJJA65EMJ/
>>
>
>
> --
> Martin Perina
> Manager, Software Engineering
> Red Hat Czech s.r.o.
>
___
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/XZTFYVAV45254FPNVEIHDXYUX5SVQI4W/


[ovirt-users] Re: Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-16 Thread Gilboa Davara
Shani,

1. I created a new 4.5 cluster with the same CPU (Secure Intel Cascadelake
Server Family) and platform type (Q35/BIOS).
2. All 3 hosts are 8.3, but report 4.4 compatibility.
3. The only reason I attempted to upgrade the cluster was simple: The
cluster state kept on dropping down to "unavailable" (even though all 3
hosts are up) and I was offered to upgrade the cluster to v4.5.

- Gilboa

On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim  wrote:

> Hi Gilboa,
>
> Here are some guidelines/checks:
> - Are you able to create a 4.5 DC/cluster?
> - Host can be Up in the 4.5 clusters only when it reports 4.5 level
> compatibility (it's based on RHEL 8.3).
>   Can you make sure that on all 3 hosts?
> - You can upgrade the 4.4 clusters to 4.5 only when all Up/NonOperational
> hosts are reporting 4.5 level
> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on the
> 4.5 level
> - A 4.5 host-based on RHEL 8.3 should be fully functional in 4.2/4.3/4.4
> clusters
>
>
>
> *Regards,*
>
> *Shani Leviim*
>
>
> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara  wrote:
>
>> Hello all,
>>
>> I'm more-or-less finished building a new ovirt over glusterfs cluster
>> with 3 fairly beefy servers.
>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before they
>> joined the cluster.
>> Looking at the cluster view in the WebUI, I get an exclamation mark with
>> the following message: "Upgrade cluster compatibility level".
>> When I try to upgrade the cluster, 2 of the 3 hosts go into maintenance
>> and reboot, but once the procedure is complete, the cluster version remains
>> the same.
>> Looking at the host vdsm logs, I see that once the engine refreshes their
>> capabilities, all hosts return 4.2-4.4 and not 4.5.
>>
>> E.g.
>>  'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2',
>> '4.3', '4.4']
>> I assume I should be seeing 4.5 after the upgrade, no?
>>
>> AmI missing something?
>>
>> Thanks,
>> - Gilboa
>> ___
>> 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/7CCUHPEGVZD3BBLBDTOCHG5J6EEG5DE2/
>>
>
___
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/RMZ3S64FFIOFTRBQOWVTTLCRJJA65EMJ/


[ovirt-users] Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)

2020-12-16 Thread Gilboa Davara
Hello all,

I'm more-or-less finished building a new ovirt over glusterfs cluster with
3 fairly beefy servers.
Nodes were fully upgraded to CentOS Linux release 8.3.2011 before they
joined the cluster.
Looking at the cluster view in the WebUI, I get an exclamation mark with
the following message: "Upgrade cluster compatibility level".
When I try to upgrade the cluster, 2 of the 3 hosts go into maintenance and
reboot, but once the procedure is complete, the cluster version remains the
same.
Looking at the host vdsm logs, I see that once the engine refreshes their
capabilities, all hosts return 4.2-4.4 and not 4.5.

E.g.
 'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2', '4.3',
'4.4']
I assume I should be seeing 4.5 after the upgrade, no?

AmI missing something?

Thanks,
- Gilboa
___
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/7CCUHPEGVZD3BBLBDTOCHG5J6EEG5DE2/


  1   2   >