[ovirt-users] Re: Interested in contributing with Spanish translation.

2022-08-31 Thread Sandro Bonazzola 
+Sharon Gratch  , +Michal Skrivanek
 can you please help here?

Il giorno mer 31 ago 2022 alle ore 22:17 Luis Pereida <
luis.pere...@gmail.com> ha scritto:

> Hello,
>
> My name is Luis Pereida, I am Mexican, from Guadalajara and I am currently
> an application security specialist.
>
> Some time ago I met the O-Virt project and it helped me a lot to solve
> many situations where virtualization was the perfect option.
>
> Since some time ago I have been thinking about how to contribute to the
> project, and talking with some friends, they would like to have
> documentation in Spanish. Although English is basic for us, many times the
> context or expressions are hard to understand.
>
> I would like to help with that. How can I do it? I see that it is
> necessary to use a Zanata account. How can I get an account?
>
> Regards and thanks for being so supportive of the community.
> ___
> 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/6GILTJOZEP65E7BNHOUFBRZAV7QKSOKI/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D PERFORMANCE & SCALE

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/SED7RQMXD4VIZW6PO5Y6INWPW5UE64WR/

[ovirt-users] Re: Ubuntu NFS

2022-08-31 Thread thilburn 
I submitted my own for 22.04. Maybe re-open your pull request? I see it closed 
with the note no one is working on it.
___
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/2HQFWUCFUW3AFYQQLRV3JFXI5SENWWSF/

[ovirt-users] Can't upgrade Cluster Compatibility Version

2022-08-31 Thread Gillingham, Eric J (US 393D) via Users 
When trying to edit my default clusters compat version from 4.5 to anything 
newer it fails with " Error while executing action Edit Cluster properties: 
Internal Engine Error"

engine.log contains the very long stack traces:
##
2022-08-31 23:43:08,647Z ERROR [org.ovirt.engine.core.bll.UpdateVmCommand] 
(default task-26) [590a6527] Error during ValidateFailure.: 
java.lang.NullPointerException
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.UpdateVmCommand.validate(UpdateVmCommand.java:1015)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.internalValidateInTransaction(CommandBase.java:824)
at 
org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:140)
at 
org.ovirt.engine.core.utils//org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:157)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.internalValidate(CommandBase.java:803)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:417)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.executor.DefaultBackendActionExecutor.execute(DefaultBackendActionExecutor.java:13)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.runAction(Backend.java:450)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.runActionImpl(Backend.java:432)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.Backend.runInternalAction(Backend.java:638)
at jdk.internal.reflect.GeneratedMethodAccessor380.invoke(Unknown 
Source)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
at 
org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79)
at 
org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89)
at 
org.jboss.as.weld.common@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102)
at 
org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at 
org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53)
at 
org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
at 
org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232)
at 
org.jboss.as.ej

[ovirt-users] Re: Ubuntu NFS

2022-08-31 Thread thilburn 
That's strange
___
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/ZU2V5S4AXSAJMB6FAOSJQBWSKA543DMS/

[ovirt-users] Re: Ubuntu NFS

2022-08-31 Thread thilburn 
> Host
> supervdsm.log
>  -open error -13 EACCES: no permission to open /ThePath/ids
>  -check that daemon user sanlock *** group sanlock *** has access to disk or 
> file.

Wrong log on Host. It was sanlock.log not supervdsm.log
___
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/KENZBEDOL3F2JT37M7JZNX3A7BRDRSQX/

[ovirt-users] Re: Ubuntu NFS

2022-08-31 Thread Matt Snow 
I submitted a PR (https://github.com/oVirt/ovirt-site/pull/2433) over a
year ago to capture this exact issue.

The NFS troubleshooting page remains the same wth no mention of this Ubuntu
NFS Server issue:
-
https://github.com/oVirt/ovirt-site/blob/main/source/develop/troubleshooting-nfs-storage-issues.md

On Wed, Aug 31, 2022 at 5:10 PM  wrote:

> Hello,
>  I was having trouble with getting an Ubuntu 22.04 NFS share working and
> after searching for hours I was able to figure out what was needed. Below
> is what I found if anyone else runs into this.
>
> My error was
> engine.log
> "...Unexpected return value: Status [code=701, message=Could not
> initialize cluster lock: ()]"
>
> Host
> supervdsm.log
>  -open error -13 EACCES: no permission to open /ThePath/ids
>  -check that daemon user sanlock *** group sanlock *** has access to disk
> or file.
>
> The fix was
> changing /etc/nfs.conf manage-gids=y ( Which is the default ) to #
> manage-gids=y ( Commenting this sets the default which is no )
> It looks like in the past the fix was to change
> /etc/default/nfs-kernel-server Line RPCMOUNTDOPTS="--manage-gids" which I
> didn't need to change.
> ___
> 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/PT6SKJ4ZTX3EKMEYPRDFW2PE5U3UGVK5/
>
___
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/3RYWBYNHNIKTAAYD5WNB7XGLKF6XE2TB/

[ovirt-users] Ubuntu NFS

2022-08-31 Thread thilburn 
Hello,
 I was having trouble with getting an Ubuntu 22.04 NFS share working and after 
searching for hours I was able to figure out what was needed. Below is what I 
found if anyone else runs into this.

My error was
engine.log
"...Unexpected return value: Status [code=701, message=Could not initialize 
cluster lock: ()]"

Host
supervdsm.log
 -open error -13 EACCES: no permission to open /ThePath/ids
 -check that daemon user sanlock *** group sanlock *** has access to disk or 
file.

The fix was
changing /etc/nfs.conf manage-gids=y ( Which is the default ) to # 
manage-gids=y ( Commenting this sets the default which is no )
It looks like in the past the fix was to change /etc/default/nfs-kernel-server 
Line RPCMOUNTDOPTS="--manage-gids" which I didn't need to change.
___
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/PT6SKJ4ZTX3EKMEYPRDFW2PE5U3UGVK5/

[ovirt-users] Interested in contributing with Spanish translation.

2022-08-31 Thread Luis Pereida 
Hello,

My name is Luis Pereida, I am Mexican, from Guadalajara and I am currently
an application security specialist.

Some time ago I met the O-Virt project and it helped me a lot to solve many
situations where virtualization was the perfect option.

Since some time ago I have been thinking about how to contribute to the
project, and talking with some friends, they would like to have
documentation in Spanish. Although English is basic for us, many times the
context or expressions are hard to understand.

I would like to help with that. How can I do it? I see that it is necessary
to use a Zanata account. How can I get an account?

Regards and thanks for being so supportive of the community.
___
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/6GILTJOZEP65E7BNHOUFBRZAV7QKSOKI/

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

2022-08-31 Thread Jirka Simon 

OK  thank you for clarification

Diky Martine.


Jirka

On 8/31/22 15:34, Martin Perina wrote:

Hi,

As mentioned to run oVirt Engine 4.5 you need at least on EL8.6 or CS8 
machine. Then you can create DataCenter with compatibility level 4.2, 
where you can create 4.2 cluster.


Martin

On Wed, 31 Aug 2022, 14:41 Jirka Simon,  wrote:

Hi Martin,

then I'm a bit confused :D in ovirt doc is  written.

see

https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_to_4-5_4-4_local_db
and when I have a fresh oVirt4.5 installation there is cluster
compatibility version 4.2 not available.

Jirka

On 8/29/22 16:27, Martin Perina wrote:

Hi,

you are mixing 2 unrelated versioning parts:

1. Supported cluster levels
- oVirt Engine 4.5 supports cluster level 4.2 - 4.7

https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/compat/src/main/java/org/ovirt/engine/core/compat/Version.java#L22
- This means that both EL7 based (4.2 and 4.3) and EL8 based
(4.4-4.7) hosts can be successfully managed by oVirtEngine 4.5

2. OS requirements of oVirt Engine 4.5
- oVirt Engine 4.5 is supported only on EL 8.6+ and CS8 stream
- This means that:
    - for standalone engine you need to have a machine with EL8.6
or CS8
      - for hosted engine you need to have a cluster with EL8.6
or CS8 hosts, where hosted engine VM based on E8.6 or CS8 can run

So specifically for your use case you need:

1. Standalone engine 4.5 running on EL8.6 or CS8, which can
manage 4.2 hosts in 4.2 cluster
2. Hosted engine 4.5 running on cluster of EL8.6 or CS8 hosts
with additional (different) 4.2 cluster, where your 4.2 hosts reside

Regards,
Martin


On Mon, Aug 29, 2022 at 2:43 PM Jirka Simon  wrote:

Hi Andrei,

ovirt 4.4+ has to run with centos/ rhel 8, I would not
recommend mix
versions of ovirt node version within one cluster. (there
couldbe / will
be a problem with vdsm version on each node)

And yes cluster compatibility version number doesn't match 
ovirt version.

I would recommend to try to remove the oldest node from the
cluster (if
upu have some spare nodes) and try to reinstall it to centos
8 or 9 with
standalone engine for test if it works or not.

Jirka

On 8/29/22 14:26, Andrei Verovski wrote:
> Hi,
>
> My oldest nodes are version 4.2 on CentOS 7.6.
> What is the latest cluster compatibility level they support?
> Looks like oVirt Engine version and cluster compatibility
level do not match number to number, e.g. my oVirt engine
4.4.10 seems can set cluster compatibility level up to 4.6.
>
> Someone from Red Hat, please clarify.
> Thanks in advance.
>
>
>> On 29 Aug 2022, at 15:09, Jirka Simon  wrote:
>>
>> Hi Andrei,
>>
>> as I know,  you need to have to have your cluster with at
least 4.3 version to migrate to 4.5. I was facing the same 
problem with (not so) old hardware. and i started to do step
by step migration.
>>
>> it means i created new cluster with fresh configuration
with ovirt 4.5  and cluster compatibility version 4.7 next to
old one with 4.4.   Iit is a good opportunity to prepare
whole cluster configuration in ansible for me :D
>>
>> Then I migrate VMs one by one from old cluster to the new
one. When is one node free on old cluster I reinstall it and
add to new cluster.
>>
>> Maybe it is not the fastest solution, but i can arrange
maintenance for each VM.
>>
>> Jirka
>>
>> On 8/29/22 10:13, Andrei Verovski wrote:
>>> Hi,
>>>
>>> I have cluster compatibility version 4.2, due to some old
nodes.
>>>  From what I remember in oVirt 4.5 release notes (correct
please, may be wrong here), oVirt engine 4.5 requires cluster
compatibility version >= 4.3.
>>> Please clarify. Thanks.
>>>
>>>
> On 28. 8. 2022, at 18:52, Andrei Verovski
 wrote:
>
> Hi,
>
> I have engine version 4.4.10.7-1.el8, is it possible to
set up new node host on CentOS Stream 9, or I need to upgrade
engine to version 4.5 first (which is not right now possible
because of some quite old nodes) ?
 yes, you generally need the latest version
 You can keep your old nodes old, 4.2 based nodes are
still working with 4.5

> Thanks
> Andrei
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an e

[ovirt-users] Re: Moving SelfHosted Engine

2022-08-31 Thread matthew.st...@fujitsu.com 
Assuming your are using SAN or NAS storage, have you considered just collapsing 
everything into the Default cluster?

-Original Message-
From: murat.cel...@dbpro.com.tr  
Sent: Wednesday, August 31, 2022 9:41 AM
To: users@ovirt.org
Subject: [ovirt-users] Moving SelfHosted Engine

Hello
We have got an Production ovirt installation with 1 datacenter and 2 clusters.

Default Cluster has got 2 hosts in it. kvm01 and kvm02.
PrimarySite cluster has got 2 hosts in it. kvm03 and kvm04

Our Self hosted engine is running on kvm01. We need to migrate the 
Selfhosted-engine to kvm03 or kvm04 since the hosts kvm01 and kvm02 hosts are 
going to be retired.

Anyone has any idea how this can be accomplished?
___
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/KW5YYL37FLURI67I2FQHRJD6BYYOTWTD/
___
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/ZNYY3RYMNTRGNM52AYW4O4QMBGOTXPA6/

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Benny Zlotnik 
Thanks Diego, I was able to reproduce it manually, shouldn't be too
difficult to fix

On Wed, Aug 31, 2022 at 5:37 PM Diego Ercolani  wrote:
>
> This is the bug report I filled: 
> https://bugzilla.redhat.com/show_bug.cgi?id=2123008
> ___
> 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/ZFF7FCEJJBTILXIKJ4J333WURXCFRWJR/
___
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/BDOB5T2TJGDUEDSYEA3GVIBLH33LWKOY/

[ovirt-users] Re: Moving SelfHosted Engine

2022-08-31 Thread Diego Ercolani 
So you need to migrate the self-hosted engine between clusters, I think the 
only way is to backup hosted-engine configuration and restore it in the other 
cluster via a new hosted-engine deploy in the other cluster and a restore of 
the backup.
But I'm very interested on how to manipulate hosted engine in the correct way 
as this is only my interpretation.
___
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/75LTCQMMVEV4KFQSODIMCT5RSWMADQSZ/

[ovirt-users] hosted-engine -vm-status show a ghost node that is not anymore in the cluster: how to remove?

2022-08-31 Thread Diego Ercolani 
engine 4.5.2.4
The issue is that in my cluster when I use the:
[root@ovirt-node3 ~]# hosted-engine --vm-status


--== Host ovirt-node3.ovirt (id: 1) status ==--

Host ID: 1
Host timestamp : 1633143
Score  : 3400
Engine status  : {"vm": "down", "health": "bad", "detail": 
"unknown", "reason": "vm not running on this host"}
Hostname   : ovirt-node3.ovirt
Local maintenance  : False
stopped: False
crc32  : 1cbfcd19
conf_on_shared_storage : True
local_conf_timestamp   : 1633143
Status up-to-date  : True
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1633143 (Wed Aug 31 14:37:53 2022)
host-id=1
score=3400
vm_conf_refresh_time=1633143 (Wed Aug 31 14:37:53 2022)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False


--== Host ovirt-node1.ovirt (id: 2) status ==--

Host ID: 2
Host timestamp : 373629
Score  : 0
Engine status  : unknown stale-data
Hostname   : ovirt-node1.ovirt
Local maintenance  : True
stopped: False
crc32  : 12a6eb81
conf_on_shared_storage : True
local_conf_timestamp   : 373630
Status up-to-date  : False
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=373629 (Tue Jun 14 16:48:50 2022)
host-id=2
score=0
vm_conf_refresh_time=373630 (Tue Jun 14 16:48:50 2022)
conf_on_shared_storage=True
maintenance=True
state=LocalMaintenance
stopped=False


--== Host ovirt-node2.ovirt (id: 3) status ==--

Host ID: 3
Host timestamp : 434247
Score  : 3400
Engine status  : {"vm": "down", "health": "bad", "detail": 
"unknown", "reason": "vm not running on this host"}
Hostname   : ovirt-node2.ovirt
Local maintenance  : False
stopped: False
crc32  : badb3751
conf_on_shared_storage : True
local_conf_timestamp   : 434247
Status up-to-date  : True
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=434247 (Wed Aug 31 14:37:45 2022)
host-id=3
score=3400
vm_conf_refresh_time=434247 (Wed Aug 31 14:37:45 2022)
conf_on_shared_storage=True
maintenance=False
state=EngineDown
stopped=False


--== Host ovirt-node4.ovirt (id: 4) status ==--

Host ID: 4
Host timestamp : 1646655
Score  : 3400
Engine status  : {"vm": "up", "health": "good", "detail": 
"Up"}
Hostname   : ovirt-node4.ovirt
Local maintenance  : False
stopped: False
crc32  : 1a16027e
conf_on_shared_storage : True
local_conf_timestamp   : 1646655
Status up-to-date  : True
Extra metadata (valid at timestamp):
metadata_parse_version=1
metadata_feature_version=1
timestamp=1646655 (Wed Aug 31 14:37:43 2022)
host-id=4
score=3400
vm_conf_refresh_time=1646655 (Wed Aug 31 14:37:43 2022)
conf_on_shared_storage=True
maintenance=False
state=EngineUp
stopped=False

The problem is that ovirt-node1.ovirt is not anymore in ther cluster, in the 
host list presented by the ui there is correctly no ovirt-node1, the 
ovirt-node1 appears only in the commandline.

I did a full text search in the engine DB, but node1 doesn't appear anywhere, 
even in the filesystem, a grep doesn't find anything
___
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/S544RUVUXTQFWMEUIGO3UOHQVCPXT3QX/

[ovirt-users] Moving SelfHosted Engine

2022-08-31 Thread murat . celebi 
Hello
We have got an Production ovirt installation with 1 datacenter and 2 clusters.

Default Cluster has got 2 hosts in it. kvm01 and kvm02.
PrimarySite cluster has got 2 hosts in it. kvm03 and kvm04

Our Self hosted engine is running on kvm01. We need to migrate the 
Selfhosted-engine to kvm03 or kvm04 since the hosts kvm01 and kvm02 hosts are 
going to be retired.

Anyone has any idea how this can be accomplished?
___
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/KW5YYL37FLURI67I2FQHRJD6BYYOTWTD/

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Diego Ercolani 
This is the bug report I filled: 
https://bugzilla.redhat.com/show_bug.cgi?id=2123008
___
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/ZFF7FCEJJBTILXIKJ4J333WURXCFRWJR/

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Diego Ercolani 
There is only one daemon.log per directory.
Here it is the archive for the daemon.log
https://cloud.ssis.sm/index.php/s/y6XxgH7CcrL5AC3

I will create the bug report referring this thread.
Thank you
___
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/LNNFGGXIAEPTDY4JKYESUGS5L4HZ6H3M/

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

2022-08-31 Thread Martin Perina 
Hi,

As mentioned to run oVirt Engine 4.5 you need at least on EL8.6 or CS8
machine. Then you can create DataCenter with compatibility level 4.2, where
you can create 4.2 cluster.

Martin

On Wed, 31 Aug 2022, 14:41 Jirka Simon,  wrote:

> Hi Martin,
>
> then I'm a bit confused :D in ovirt doc is  written.
>
> see
> https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_to_4-5_4-4_local_db
> and when I have a fresh oVirt4.5 installation there is cluster
> compatibility version 4.2 not available.
>
> Jirka
>
> On 8/29/22 16:27, Martin Perina wrote:
>
> Hi,
>
> you are mixing 2 unrelated versioning parts:
>
> 1. Supported cluster levels
> - oVirt Engine 4.5 supports cluster level 4.2 - 4.7
>
> https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/compat/src/main/java/org/ovirt/engine/core/compat/Version.java#L22
> - This means that both EL7 based (4.2 and 4.3) and EL8 based (4.4-4.7)
> hosts can be successfully managed by oVirtEngine 4.5
>
> 2. OS requirements of oVirt Engine 4.5
> - oVirt Engine 4.5 is supported only on EL 8.6+ and CS8 stream
> - This means that:
> - for standalone engine you need to have a machine with EL8.6 or
> CS8
> - for hosted engine you need to have a cluster with EL8.6 or CS8
> hosts, where hosted engine VM based on E8.6 or CS8 can run
>
> So specifically for your use case you need:
>
> 1. Standalone engine 4.5 running on EL8.6 or CS8, which can manage 4.2
> hosts in 4.2 cluster
> 2. Hosted engine 4.5 running on cluster of EL8.6 or CS8 hosts with
> additional (different) 4.2 cluster, where your 4.2 hosts reside
>
> Regards,
> Martin
>
>
> On Mon, Aug 29, 2022 at 2:43 PM Jirka Simon  wrote:
>
>> Hi Andrei,
>>
>> ovirt 4.4+ has to run with centos/ rhel 8, I would not recommend mix
>> versions of ovirt node version within one cluster. (there couldbe / will
>> be a problem with vdsm version on each node)
>>
>> And yes cluster compatibility version number doesn't match  ovirt version.
>>
>> I would recommend to try to remove the oldest node from the cluster (if
>> upu have some spare nodes) and try to reinstall it to centos 8 or 9 with
>> standalone engine for test if it works or not.
>>
>> Jirka
>>
>> On 8/29/22 14:26, Andrei Verovski wrote:
>> > Hi,
>> >
>> > My oldest nodes are version 4.2 on CentOS 7.6.
>> > What is the latest cluster compatibility level they support?
>> > Looks like oVirt Engine version and cluster compatibility level do not
>> match number to number, e.g. my oVirt engine 4.4.10 seems can set cluster
>> compatibility level up to 4.6.
>> >
>> > Someone from Red Hat, please clarify.
>> > Thanks in advance.
>> >
>> >
>> >> On 29 Aug 2022, at 15:09, Jirka Simon  wrote:
>> >>
>> >> Hi Andrei,
>> >>
>> >> as I know,  you need to have to have your cluster with at least 4.3
>> version to migrate to 4.5. I was facing the same  problem with (not so) old
>> hardware. and i started to do step by step migration.
>> >>
>> >> it means i created new cluster with fresh configuration with ovirt
>> 4.5  and cluster compatibility version 4.7 next to old one with 4.4.   Iit
>> is a good opportunity to prepare whole cluster configuration in ansible for
>> me :D
>> >>
>> >> Then I migrate VMs one by one from old cluster to the new one. When is
>> one node free on old cluster I reinstall it and add to new cluster.
>> >>
>> >> Maybe it is not the fastest solution, but i can arrange maintenance
>> for each VM.
>> >>
>> >> Jirka
>> >>
>> >> On 8/29/22 10:13, Andrei Verovski wrote:
>> >>> Hi,
>> >>>
>> >>> I have cluster compatibility version 4.2, due to some old nodes.
>> >>>  From what I remember in oVirt 4.5 release notes (correct please, may
>> be wrong here), oVirt engine 4.5 requires cluster compatibility version >=
>> 4.3.
>> >>> Please clarify. Thanks.
>> >>>
>> >>>
>> > On 28. 8. 2022, at 18:52, Andrei Verovski 
>> wrote:
>> >
>> > Hi,
>> >
>> > I have engine version 4.4.10.7-1.el8, is it possible to set up new
>> node host on CentOS Stream 9, or I need to upgrade engine to version 4.5
>> first (which is not right now possible because of some quite old nodes) ?
>>  yes, you generally need the latest version
>>  You can keep your old nodes old, 4.2 based nodes are still working
>> with 4.5
>> 
>> > Thanks
>> > Andrei
>> > ___
>> > Users mailing list -- users@ovirt.org
>> > To unsubscribe send an email to users-le...@ovirt.org
>> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> > oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> > List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/IC3ZW2XY7BAEAU3H72P4VA76Y63F32XU/
>> >>> ___
>> >>> Users mailing list -- users@ovirt.org
>> >>> To unsubscribe send an email to users-le...@ovirt.org
>> >>> Privacy Statement: https://www.ovirt.org/privacy-p

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Benny Zlotnik 
Thanks Diego, I checked one of the failures and I see:

2022-08-26 13:00:16,067Z ERROR
[org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand]
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-6
) [51fb711e-0fbc-4590-8ff0-638a041b13a5] Failed to extend proxy ticket
'1e1846a1-f9f0-49e5-912e-2f5bf8dd8144' for image transfer
'54097389-db69-4aa3-a34d-eb6cb2c1fc4b': {}:
java.lang.RuntimeException: ImageioClient request failed. Status: 404,
Reason: Not Found, Error: No such ticket:
1e1846a1-f9f0-49e5-912e-2f5bf8dd8144.
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.executeRequest(ImageioClient.java:134)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.extendTicket(ImageioClient.java:89)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.extendImageTransferSession(TransferDiskImageCommand.java:1353
)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.extendTicketIfNecessary(TransferDiskImageCommand.java:785)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.handleTransferring(TransferDiskImageCommand.java:774)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.executeStateHandler(TransferDiskImageCommand.java:593)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand.proceedCommandExecution(TransferDiskImageCommand.java:574)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.TransferImageCommandCallback.doPolling(TransferImageCommandCallback.java:21)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175)
at 
deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at 
java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at 
org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(M
anagedScheduledThreadPoolExecutor.java:360)
at 
org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedS
cheduledThreadPoolExecutor.java:511)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
at 
org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227)
...

I see that it happened after restarting, so it looks like it messed up
the cleanup sequence and did not close the nbd server.

Do you have the imageio logs? They should be available on the host
performed the transfer under /var/log/ovirt-imageio/daemon.log
And please submit a bug for this with these logs




On Wed, Aug 31, 2022 at 4:03 PM Diego Ercolani  wrote:
>
> I add also that I upgraded the engine on 2022-08-22 so I have the last 
> "stable" since then:
>
> [root@ovirt-engine dbutils]# rpm -qi ovirt-engine-4.5.2.4-1.el8.noarch
> Name: ovirt-engine
> Version : 4.5.2.4
> Release : 1.el8
> Architecture: noarch
> Install Date: Mon Aug 22 08:17:41 2022
> Group   : Virtualization/Management
> Size: 39473100
> License : ASL 2.0
> Signature   : RSA/SHA256, Sun Aug 21 15:16:08 2022, Key ID ab8c4f9dfe590cb7
> Source RPM  : ovirt-engine-4.5.2.4-1.el8.src.rpm
>
> ___
> 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/B4LIWGEWFNWFGVZ5NSTQYMP4VZHKETBW/
___
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/GK55UOQBOOWFH2E3XKCQCLXARZVMZ3AD/

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Diego Ercolani 
I add also that I upgraded the engine on 2022-08-22 so I have the last "stable" 
since then: 

[root@ovirt-engine dbutils]# rpm -qi ovirt-engine-4.5.2.4-1.el8.noarch
Name: ovirt-engine
Version : 4.5.2.4
Release : 1.el8
Architecture: noarch
Install Date: Mon Aug 22 08:17:41 2022
Group   : Virtualization/Management
Size: 39473100
License : ASL 2.0
Signature   : RSA/SHA256, Sun Aug 21 15:16:08 2022, Key ID ab8c4f9dfe590cb7
Source RPM  : ovirt-engine-4.5.2.4-1.el8.src.rpm

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

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Diego Ercolani 
One process that I killed was:
[root@ovirt-node4 ~]# ps axuww | grep qemu-nbd
vdsm  588156  0.0  0.0 308192 39840 ?Ssl  Aug26   0:12 
/usr/bin/qemu-nbd --socket 
/run/vdsm/nbd/c7653559-508b-4e4a-a591-32dec3e5a29d.sock --persistent --shared=8 
--export-name= --cache=none --aio=native --allocation-depth --read-only 
json:{"driver": "qcow2", "file": {"driver": "file", "filename": 
"/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/7a05ff72-370e-4d0c-ab56-5f161cc98318/52ee7e19-ac78-4c05-81e2-0c75dad71732"}}

The event that was talking about "file lock" is this in the engine.log:
2022-08-31 10:39:16,431Z INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-91) 
[617f02f1-29e6-45f4-b5bc-aa4c16b02b15] FINISH, Ge
tHostJobsVDSCommand, return: 
{667f22f0-3df5-43b8-b94d-c0ee48424247=HostJobInfo:{id='667f22f0-3df5-43b8-b94d-c0ee48424247',
 type='storage', description='merge_subchain', status='failed', progress='0', 
error='VDSError:{co
de='GeneralException', message='General Exception: ('Command 
[\'/usr/bin/qemu-img\', \'commit\', \'-p\', \'-t\', \'none\', \'-b\', 
\'/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/im
ages/7a05ff72-370e-4d0c-ab56-5f161cc98318/d0e6f4b9-ae29-493d-b22f-c6aee55d84ae\',
 \'-f\', \'qcow2\', 
\'/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/7a05ff72-370e-4d0c-ab56-5
f161cc98318/52ee7e19-ac78-4c05-81e2-0c75dad71732\'] failed with rc=1 out=b\'\' 
err=bytearray(b\'qemu-img: Could not open 
\\\'/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/7a0
5ff72-370e-4d0c-ab56-5f161cc98318/52ee7e19-ac78-4c05-81e2-0c75dad71732\\\': 
Failed to get "write" lock\\nIs another process using the image 
[/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b1
00d72/images/7a05ff72-370e-4d0c-ab56-5f161cc98318/52ee7e19-ac78-4c05-81e2-0c75dad71732]?\\n\')',)'}'}},
 log id: 2c62cd00

so these are the logs related to this qemu-nbd command invocation:
https://cloud.ssis.sm/index.php/s/RSpQJHEeDxai5ea

The other qemu-nbd:
[root@ovirt-node3 ~]# ps -ef | grep qemu-nbd
vdsm 1795830   1  0 Aug26 ?00:00:09 /usr/bin/qemu-nbd --socket 
/run/vdsm/nbd/54097389-db69-4aa3-a34d-eb6cb2c1fc4b.sock --persistent --shared=8 
--export-name= --cache=none --aio=native --allocation-depth --read-only 
json:{"driver": "qcow2", "file": {"driver": "file", "filename": 
"/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/f17c3443-b62f-43f5-b35c-5ba9225abaf4"}}

The engine.log lock event:
2022-08-31 10:23:54,033Z INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-91) 
[4a3cf96d-5fb8-4479-9eda-4012d1cae8c2] FINISH, GetHostJobsVDSCommand, return: 
{f0df76ab-c708-4c0f-ad8e-ecf26c8910d9=HostJobInfo:{id='f0df76ab-c708-4c0f-ad8e-ecf26c8910d9',
 type='storage', description='merge_subchain', status='failed', progress='0', 
error='VDSError:{code='GeneralException', message='General Exception: ('Command 
[\'/usr/bin/qemu-img\', \'commit\', \'-p\', \'-t\', \'none\', \'-b\', 
\'/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/f17c3443-b62f-43f5-b35c-5ba9225abaf4\',
 \'-f\', \'qcow2\', 
\'/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/98ddfc07-8d97-4511-bfef-1ea0ce72b5a6\']
 failed with rc=1 out=b\'\' err=bytearray(b\'qemu-img: Failed to get "w
 rite" lock\\nIs another process using the image 
[/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/f17c3443-b62f-43f5-b35c-5ba9225abaf4]?\\n\')',)'}'}},
 log id: 380108e6

and these are related log:
https://cloud.ssis.sm/index.php/s/p3LAAkXxRrAbdxK
___
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/S3Y3ZDCUIWB2F5RAHL4YJWM2SYNBGG4J/

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

2022-08-31 Thread Jirka Simon 

Hi Martin,

then I'm a bit confused :D in ovirt doc is  written.

see 
https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_the_Manager_to_4-5_4-4_local_db
and when I have a fresh oVirt4.5 installation there is cluster 
compatibility version 4.2 not available.


Jirka

On 8/29/22 16:27, Martin Perina wrote:

Hi,

you are mixing 2 unrelated versioning parts:

1. Supported cluster levels
    - oVirt Engine 4.5 supports cluster level 4.2 - 4.7
https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/compat/src/main/java/org/ovirt/engine/core/compat/Version.java#L22
    - This means that both EL7 based (4.2 and 4.3) and EL8 based 
(4.4-4.7) hosts can be successfully managed by oVirtEngine 4.5


2. OS requirements of oVirt Engine 4.5
    - oVirt Engine 4.5 is supported only on EL 8.6+ and CS8 stream
    - This means that:
        - for standalone engine you need to have a machine with EL8.6 
or CS8
        - for hosted engine you need to have a cluster with EL8.6 or 
CS8 hosts, where hosted engine VM based on E8.6 or CS8 can run


So specifically for your use case you need:

1. Standalone engine 4.5 running on EL8.6 or CS8, which can manage 4.2 
hosts in 4.2 cluster
2. Hosted engine 4.5 running on cluster of EL8.6 or CS8 hosts with 
additional (different) 4.2 cluster, where your 4.2 hosts reside


Regards,
Martin


On Mon, Aug 29, 2022 at 2:43 PM Jirka Simon  wrote:

Hi Andrei,

ovirt 4.4+ has to run with centos/ rhel 8, I would not recommend mix
versions of ovirt node version within one cluster. (there couldbe
/ will
be a problem with vdsm version on each node)

And yes cluster compatibility version number doesn't match ovirt
version.

I would recommend to try to remove the oldest node from the
cluster (if
upu have some spare nodes) and try to reinstall it to centos 8 or
9 with
standalone engine for test if it works or not.

Jirka

On 8/29/22 14:26, Andrei Verovski wrote:
> Hi,
>
> My oldest nodes are version 4.2 on CentOS 7.6.
> What is the latest cluster compatibility level they support?
> Looks like oVirt Engine version and cluster compatibility level
do not match number to number, e.g. my oVirt engine 4.4.10 seems
can set cluster compatibility level up to 4.6.
>
> Someone from Red Hat, please clarify.
> Thanks in advance.
>
>
>> On 29 Aug 2022, at 15:09, Jirka Simon  wrote:
>>
>> Hi Andrei,
>>
>> as I know,  you need to have to have your cluster with at least
4.3 version to migrate to 4.5. I was facing the same  problem with
(not so) old hardware. and i started to do step by step migration.
>>
>> it means i created new cluster with fresh configuration with
ovirt 4.5  and cluster compatibility version 4.7 next to old one
with 4.4.   Iit is a good opportunity to prepare whole cluster
configuration in ansible for me :D
>>
>> Then I migrate VMs one by one from old cluster to the new one.
When is one node free on old cluster I reinstall it and add to new
cluster.
>>
>> Maybe it is not the fastest solution, but i can arrange
maintenance for each VM.
>>
>> Jirka
>>
>> On 8/29/22 10:13, Andrei Verovski wrote:
>>> Hi,
>>>
>>> I have cluster compatibility version 4.2, due to some old nodes.
>>>  From what I remember in oVirt 4.5 release notes (correct
please, may be wrong here), oVirt engine 4.5 requires cluster
compatibility version >= 4.3.
>>> Please clarify. Thanks.
>>>
>>>
> On 28. 8. 2022, at 18:52, Andrei Verovski
 wrote:
>
> Hi,
>
> I have engine version 4.4.10.7-1.el8, is it possible to set
up new node host on CentOS Stream 9, or I need to upgrade engine
to version 4.5 first (which is not right now possible because of
some quite old nodes) ?
 yes, you generally need the latest version
 You can keep your old nodes old, 4.2 based nodes are still
working with 4.5

> Thanks
> Andrei
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:

https://lists.ovirt.org/archives/list/users@ovirt.org/message/IC3ZW2XY7BAEAU3H72P4VA76Y63F32XU/
>>> ___
>>> 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/SZCOBNKBBSFUP

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Benny Zlotnik 
Do you have the logs (engine.log, vdsm.log) for this?
qemu-nbd holding the lock might mean the transfer was not finalized
properly and the nbd server was left open which should not happen...

On Wed, Aug 31, 2022 at 1:57 PM Diego Ercolani  wrote:
>
> Thanks Arik,
> we have tried your solution but with no successful results.
> we have gather also other infor and combined in this solution:
>
> we have deleted on DB the row on vm_backups and vm_disk_map related to the 
> hanged backup.
>
> The we have tried to delete shapshot locked , after the row db deletion the 
> messange "cannot delete shapshot during backup operations" does not apper" 
> but deletion failed anyway.
>
> so we watch the log file /var/log/ovirt-engine/engine.log ans see this 
> messages
>
> nIs another process using the image [
>  
> /rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/f17c3443-b62f-43f5-b35c-5ba9225abaf4
>
> then we search on the node which process olds the file with the command:
>
> lsof | grep f17c3443-b62f-43f5-b35c-5ba9225abaf4
>
> and we found on a node that the file was in use by a process qemu-ndb
>
> we kill that process and finally we were enabled to delete the shapshot.
>
>
> Thanks again for your support
> ___
> 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/LX7ZZTJVUI6ZKW3CL4IU7ICUED2L3PP4/
___
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/GALQ4MAA5YZRHNYIKVBAPE5LDPQWZ4MB/

[ovirt-users] Re: how kill backup operation

2022-08-31 Thread Diego Ercolani 
Thanks Arik, 
we have tried your solution but with no successful results.
we have gather also other infor and combined in this solution:

we have deleted on DB the row on vm_backups and vm_disk_map related to the 
hanged backup.

The we have tried to delete shapshot locked , after the row db deletion the 
messange "cannot delete shapshot during backup operations" does not apper" but 
deletion failed anyway.

so we watch the log file /var/log/ovirt-engine/engine.log ans see this messages

nIs another process using the image [
 
/rhev/data-center/mnt/glusterSD/localhost:_gv0/60b7f172-08ed-4a22-8414-31fd5b100d72/images/5d18a058-652f-4c94-a9ff-9c15152c61b4/f17c3443-b62f-43f5-b35c-5ba9225abaf4

then we search on the node which process olds the file with the command:

lsof | grep f17c3443-b62f-43f5-b35c-5ba9225abaf4

and we found on a node that the file was in use by a process qemu-ndb 

we kill that process and finally we were enabled to delete the shapshot.


Thanks again for your support
___
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/LX7ZZTJVUI6ZKW3CL4IU7ICUED2L3PP4/

[ovirt-users] Re: Q: Engione 4.4.10 and New Host on CentOS Stream 9

2022-08-31 Thread Andrei Verovski 
Hi,

Martin, thanks a lot, now I successfully upgraded Engine to latest 4.5, yet old 
nodes 4.2 / CentOS 7.6 still working fine.
Now I can move VMs and upgrade old nodes.


> On 29 Aug 2022, at 17:27, Martin Perina  wrote:
> 
> Hi,
> 
> you are mixing 2 unrelated versioning parts:
> 
> 1. Supported cluster levels
> - oVirt Engine 4.5 supports cluster level 4.2 - 4.7
>  
> https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/compat/src/main/java/org/ovirt/engine/core/compat/Version.java#L22
>  
> 
> - This means that both EL7 based (4.2 and 4.3) and EL8 based (4.4-4.7) 
> hosts can be successfully managed by oVirtEngine 4.5
> 
> 2. OS requirements of oVirt Engine 4.5
> - oVirt Engine 4.5 is supported only on EL 8.6+ and CS8 stream
> - This means that:
> - for standalone engine you need to have a machine with EL8.6 or CS8
> - for hosted engine you need to have a cluster with EL8.6 or CS8 
> hosts, where hosted engine VM based on E8.6 or CS8 can run
> 
> So specifically for your use case you need:
> 
> 1. Standalone engine 4.5 running on EL8.6 or CS8, which can manage 4.2 hosts 
> in 4.2 cluster
> 2. Hosted engine 4.5 running on cluster of EL8.6 or CS8 hosts with additional 
> (different) 4.2 cluster, where your 4.2 hosts reside
> 
> Regards,
> Martin
> 
> 
> On Mon, Aug 29, 2022 at 2:43 PM Jirka Simon  > wrote:
> Hi Andrei,
> 
> ovirt 4.4+ has to run with centos/ rhel 8, I would not recommend mix 
> versions of ovirt node version within one cluster. (there couldbe / will 
> be a problem with vdsm version on each node)
> 
> And yes cluster compatibility version number doesn't match  ovirt version.
> 
> I would recommend to try to remove the oldest node from the cluster (if 
> upu have some spare nodes) and try to reinstall it to centos 8 or 9 with 
> standalone engine for test if it works or not.
> 
> Jirka
> 
> On 8/29/22 14:26, Andrei Verovski wrote:
> > Hi,
> >
> > My oldest nodes are version 4.2 on CentOS 7.6.
> > What is the latest cluster compatibility level they support?
> > Looks like oVirt Engine version and cluster compatibility level do not 
> > match number to number, e.g. my oVirt engine 4.4.10 seems can set cluster 
> > compatibility level up to 4.6.
> >
> > Someone from Red Hat, please clarify.
> > Thanks in advance.
> >
> >
> >> On 29 Aug 2022, at 15:09, Jirka Simon  >> > wrote:
> >>
> >> Hi Andrei,
> >>
> >> as I know,  you need to have to have your cluster with at least 4.3 
> >> version to migrate to 4.5. I was facing the same  problem with (not so) 
> >> old hardware. and i started to do step by step migration.
> >>
> >> it means i created new cluster with fresh configuration with ovirt 4.5  
> >> and cluster compatibility version 4.7 next to old one with 4.4.   Iit is a 
> >> good opportunity to prepare whole cluster configuration in ansible for me 
> >> :D
> >>
> >> Then I migrate VMs one by one from old cluster to the new one. When is one 
> >> node free on old cluster I reinstall it and add to new cluster.
> >>
> >> Maybe it is not the fastest solution, but i can arrange maintenance for 
> >> each VM.
> >>
> >> Jirka
> >>
> >> On 8/29/22 10:13, Andrei Verovski wrote:
> >>> Hi,
> >>>
> >>> I have cluster compatibility version 4.2, due to some old nodes.
> >>>  From what I remember in oVirt 4.5 release notes (correct please, may be 
> >>> wrong here), oVirt engine 4.5 requires cluster compatibility version >= 
> >>> 4.3.
> >>> Please clarify. Thanks.
> >>>
> >>>
> > On 28. 8. 2022, at 18:52, Andrei Verovski  > > wrote:
> >
> > Hi,
> >
> > I have engine version 4.4.10.7-1.el8, is it possible to set up new node 
> > host on CentOS Stream 9, or I need to upgrade engine to version 4.5 
> > first (which is not right now possible because of some quite old nodes) 
> > ?
>  yes, you generally need the latest version
>  You can keep your old nodes old, 4.2 based nodes are still working with 
>  4.5
> 
> > Thanks
> > Andrei
> > ___
> > Users mailing list -- users@ovirt.org 
> > To unsubscribe send an email to users-le...@ovirt.org 
> > 
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html 
> > 
> > oVirt Code of Conduct: 
> > https://www.ovirt.org/community/about/community-guidelines/ 
> > 
> > List Archives: 
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/IC3ZW2XY7BAEAU3H72P4VA76Y63F32XU/
> >  
> >

[ovirt-users] Re: Failed to delete snapshot

2022-08-31 Thread Giulio Casella 

Hi Benny,
we filed a new bug: https://bugzilla.redhat.com/show_bug.cgi?id=2122525

On 30/08/2022 16:00, Giorgio Biacchi wrote:

So it seems there's another bug.

Since the bug was opened for an issue caused by the removal of a 
snapshot by vprotect (backup application) I thought that the fix should 
also fix the issue we have with vprotect, but this didn't happened.


I think we'll file a new bug as soon as possible.

Regards

Il 26/08/2022 20:25, Benny Zlotnik ha scritto:

The bug you mentioned was fixed in 4.5.2.2. But to clarify the issue
that's fixed: The fix is for a situation where a snapshot removal
failed for whatever reason, but the volume was removed in vdsm and
remains present in the engine's database. Without the fix, attempting
to remove the snapshot again would fail.

Is this the scenario you are facing now?

There is another question of why the snapshot removal failed
initially, and I did not get logs with this information (although it
could be due to network issues)

On Fri, Aug 26, 2022 at 7:19 PM Giorgio Biacchi  
wrote:


Hi,
I filed a bug about this last year...

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

We've dome some tests with vProtect after the leatest Ovirt release
4.5.2.4-1.el8  but we still have problems with snapshots removal and
disks left in locked or illegal state.

To bring back a disk from illegal state we live migrate the disk(s) to
another data domain. After this the snapshots are back to legal and can
be removed from the UI. This is pratical only for VMs with small disks.
Sadly one of the VMs we have problems with has a 2.5Tb disk attached :(

Hope this get solved soon.

Regards

Il 25/08/2022 10:26, Jirka Simon ha scritto:

Hello Sven,

Please do you have any details about it? Like bug report od knowledge
base or article ?   We have ovit and vprotect as well and our troubles
started after last update of ovirt 4.4 ( frozen vm with snapshot 
crating

job, then after unlock some snapshots is not possible to delete.)  And
now I'm preparing upgrade to 4.5.2 Yesterday we upgraded vProtect to 
the

latest version.

Thank you for any detail.


Jirka

On 8/24/22 15:20, Sven Jansen via Users wrote:

We are currently sitting on a not really working backup solution.
oVirt 4.5.x has constant issues removing snapshots, same like OP.
vProtect with Snapshots has issues with oVirt deleting snapshots.
vProtect 5.1 has broken CBT with oVirt 4.5.x.

vProtect support tells us that the snapshot issues is in oVirt (true)
and CBT is a preview feature not really supported. So currently
vProtect 5.1 and oVirt 4.5 is a no go solution. We are thinking going
to xcp-ng due to constant issues with oVirt and or vProtect.
___
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/V7VSQLOGJDTBTZ2RMJ7GGD65ZADNY2WP/ 




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





--
gb

PGP Key: http://pgp.mit.edu/
Primary key fingerprint: C510 0765 943E EBED A4F2 69D3 16CC DC90 B9CB 
0F34

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









smime.p7s
Description: S/MIME Cryptographic Signature
___
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/E5CWFX34ZVFMT5SYOIZWZ4YCDHQYJIWN/