- Users - oVirt List Archives

Single node hyperconverged issue with 4.5.0.2
by bpbp＠fastmail.com 18 May '22

18 May '22

I've run into the following issue with oVirt node on a single host using the single node hyperconverged wizard: TASK [gluster.features/roles/gluster_hci : Create the GlusterFS volumes] ******* failed: [ovirt01.syd1.fqdn.com] (item={'volname': 'engine', 'brick': '/gluster_bricks/engine/engine', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": true, "cmd": "gluster volume create engine replica __omit_place_holder__2e79c54ac7e0f34125a3ed6965d6de550953524f transport tcp ovirt01.syd1.fqdn.com:/gluster_bricks/engine/engine force\n", "delta": "0:00:00.086880", "end": "2022-05-18 10:28:49.211929", "item": {"arbiter": 0, "brick": "/gluster_bricks/engine/engine", "volname": "engine"}, "msg": "non-zero return code", "rc": 1, "start": "2022-05-18 10:28:49.125049", "stderr": "replica count should be greater than 1\n\nUsage:\nvolume create <NEW-VOLNAME> [[replica <COUNT> [arbiter <COUNT>]]|[replica 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> <TA-BRICK>... [force]", "stderr_lines": ["replica count should be greater than 1", "", "Usage:", "volume create <NEW-VOLNAME> [[replica <COUNT> [arbiter <COUNT>]]|[replica 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> <TA-BRICK>... [force]"], "stdout": "", "stdout_lines": []} failed: [ovirt01.syd1.fqdn.com] (item={'volname': 'data', 'brick': '/gluster_bricks/data/data', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": true, "cmd": "gluster volume create data replica __omit_place_holder__2e79c54ac7e0f34125a3ed6965d6de550953524f transport tcp ovirt01.syd1.fqdn.com:/gluster_bricks/data/data force\n", "delta": "0:00:00.088490", "end": "2022-05-18 10:28:49.905458", "item": {"arbiter": 0, "brick": "/gluster_bricks/data/data", "volname": "data"}, "msg": "non-zero return code", "rc": 1, "start": "2022-05-18 10:28:49.816968", "stderr": "replica count should be greater than 1\n\nUsage:\nvolume create <NEW-VOLNAME> [[replica <COUNT> [arbiter <COUNT>]]|[replica 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> <TA-BRICK>... [force]", "stderr_lines": ["replica count should be greater than 1", "", "Usage:", "volume create <NEW-VOLNAME> [[replica <COUNT> [arbiter <COUNT>]]|[replic a 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> <TA-BRICK>... [force]"], "stdout": "", "stdout_lines": []} failed: [ovirt01.syd1.fqdn.com] (item={'volname': 'vmstore', 'brick': '/gluster_bricks/vmstore/vmstore', 'arbiter': 0}) => {"ansible_loop_var": "item", "changed": true, "cmd": "gluster volume create vmstore replica __omit_place_holder__2e79c54ac7e0f34125a3ed6965d6de550953524f transport tcp ovirt01.syd1.fqdn.com:/gluster_bricks/vmstore/vmstore force\n", "delta": "0:00:00.086626", "end": "2022-05-18 10:28:50.604015", "item": {"arbiter": 0, "brick": "/gluster_bricks/vmstore/vmstore", "volname": "vmstore"}, "msg": "non-zero return code", "rc": 1, "start": "2022-05-18 10:28:50.517389", "stderr": "replica count should be greater than 1\n\nUsage:\nvolume create <NEW-VOLNAME> [[replica <COUNT> [arbiter <COUNT>]]|[replica 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> <TA-BRICK>... [force]", "stderr_lines": ["replica count should be greater than 1", "", "Usage:", "volume create <NEW-VOLNAME> [[replica <COUNT> [arbiter <COUNT>]]|[replica 2 thin-arbiter 1]] [disperse [<COUNT>]] [disperse-data <COUNT>] [redundancy <COUNT>] [transport <tcp|rdma|tcp,rdma>] <NEW-BRICK> <TA-BRICK>... [force]"], "stdout": "", "stdout_lines": []} The only non-default settings I changed were the stripe size and number of disks. Following the steps here: https://www.ovirt.org/dropped/gluster-hyperconverged/chap-Single_node_hyper… Any ideas to work around this? I will be deploying to 6 nodes eventually but wanted to try out the engine before the rest of my hardware arrives :)

2 2

list-view instead of tiled-view in oVirt VM Portal?
by Goorkate, B.J. 18 May '22

18 May '22

Hi all, Is it possible to have a list of vm's in the oVirt VM-portal instead of the tiled view? (can't find it, but may have overlooked....) Thanks! Regards, Bertjan ------------------------------------------------------------------------------ De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct te informeren door het bericht te retourneren. Het Universitair Medisch Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W. (Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197. Denk s.v.p aan het milieu voor u deze e-mail afdrukt. ------------------------------------------------------------------------------ This message may contain confidential information and is intended exclusively for the addressee. If you receive this message unintentionally, please do not use the contents but notify the sender immediately by return e-mail. University Medical Center Utrecht is a legal person by public law and is registered at the Chamber of Commerce for Midden-Nederland under no. 30244197. Please consider the environment before printing this e-mail.

3 2

Cluster CPU Type
by Colin Coe 18 May '22

18 May '22

Hi all I'm just putting in some new servers to be used as hosts in RHV 4.3 (soon to go to v4.4 or v4.5) but I'm having problems with the cluster CPU. These are HPE DL360 Gen10 with "Xeon Gold 6338N". Google tells me these are "Ice Lake" but RHV complains unless I set the cluster CPU type to "SandyBridge". Is this expected? What do I need to do to get these recognised as the corect CPU type? Thanks CC

2 1

OVA Import Fail
by Abe E 17 May '22

17 May '22

Anyone getting issues with OVA Imports on 4.4? I exported this from ovirt back in March although now importing again it is failing. My engine logs show it erroring out here: Command, return: StatusReturn:{status='Status [code=0, message=Done]'}, log id: 7f970c1f 2022-05-12 17:14:40,396-06 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [] EVENT_ID: USER_ADD_DISK_TO_VM_FINISHED_SUCCESS(97), The d isk Nextgen-CC-Tools_Disk1 was successfully added to VM Nextgen-CC-Tools. 2022-05-12 17:14:40,678-06 INFO [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Running command: ExtractOvaComman d internal: true. Entities affected : ID: 66ff7ebd-7682-4b94-b98d-5ceb76661830 Type: VM 2022-05-12 17:14:40,691-06 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] START, PrepareImageVDSCom mand(HostName = ovirt-2.removed.com, PrepareImageVDSCommandParameters:{hostId='0fbd6429-9c91-44d7-8d50-dcc08c8301f9'}), log id: 6915fcb6 2022-05-12 17:14:40,731-06 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.PrepareImageVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] FINISH, PrepareImageVDSCo mmand, return: PrepareImageReturn:{status='Status [code=0, message=Done]'}, log id: 6915fcb6 2022-05-12 17:14:46,893-06 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] EVENT_ID: ANSIBLE_RUN NER_EVENT_NOTIFICATION(559), Import OVA. Run import yaml on py3. 2022-05-12 17:14:46,918-06 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] EVENT_ID: ANSIBLE_RUN NER_EVENT_NOTIFICATION(559), Import OVA. Set facts. 2022-05-12 17:14:49,936-06 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Command 'org.ovirt.engine.core.bl l.exportimport.ExtractOvaCommand' failed: Task Run extraction script failed to execute. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-import-ova-ansible-20220512171440-ovirt-2.removed.com-192f636b-0dd4-4a61-a673-1b94 6d7e0b56.log 2022-05-12 17:14:49,936-06 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-68) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Exception: org.ovirt.engine.core. common.utils.ansible.AnsibleRunnerCallException: Task Run extraction script failed to execute. Please check logs for more details: /var/log/ovirt-engine/ova/ovirt-import-ova-ansible-20220512171440-ovirt-2.removed.com-192f636b-0dd4-4a61-a6 73-1b946d7e0b56.log at deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleRunnerHttpClient.processEvents(AnsibleRunnerHttpClient.java:251) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:227) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:74) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor.runCommand(AnsibleExecutor.java:51) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand.runAnsibleImportOvaPlaybook(ExtractOvaCommand.java:129) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand.executeVmCommand(ExtractOvaCommand.java:79) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.VmCommand.executeCommand(VmCommand.java:178) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1174) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1332) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:2010) 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.executeInScope(TransactionSupport.java:79) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1392) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:424) 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.GeneratedMethodAccessor202.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@23.0.2.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@23.0.2.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) at org.jboss.as.weld.common@23.0.2.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:89) at org.jboss.as.weld.common@23.0.2.Final//org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:102) at org.jboss.as.ee@23.0.2.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@23.0.2.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@23.0.2.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@23.0.2.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@23.0.2.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@23.0.2.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:164) 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.weld.core@3.1.6.Final//org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) at org.jboss.as.weld.common@23.0.2.Final//org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) 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.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) 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.run(InterceptorContext.java:438) at org.wildfly.security.elytron-private@1.15.3.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:633) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) 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@23.0.2.Final//org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:191) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:81) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.interfaces.BackendInternal$$$view4.runInternalAction(Unknown Source) at jdk.internal.reflect.GeneratedMethodAccessor201.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.weld.core@3.1.6.Final//org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:410) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.module.ejb.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:134) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.module.ejb.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:68) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.BackendCommandObjectsHandler$BackendInternal$BackendLocal2049259618$Proxy$_$$_Weld$EnterpriseProxy$.runInternalAction(Unknown Source) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.CommandBase.runInternalAction(CommandBase.java:2388) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand.convert(ImportVmFromOvaCommand.java:59) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand.executeNextOperation(ImportVmFromExternalProviderCommand.java:510) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.exportimport.ImportVmFromExternalProviderCommand.performNextOperation(ImportVmFromExternalProviderCommand.java:502) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:80) 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(ManagedScheduledThreadPoolExecutor.java:360) at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.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) 2022-05-12 17:14:50,972-06 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-74) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Command 'ExtractOva' id : '6ece0932-038c-485e-8d7c-76927c04ea1c' child commands '[]' executions were completed, status 'FAILED' 2022-05-12 17:14:52,061-06 ERROR [org.ovirt.engine.core.bll.exportimport.ExtractOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-87) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Ending command 'org.ovirt.engine. core.bll.exportimport.ExtractOvaCommand' with failure. 2022-05-12 17:14:52,091-06 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-87) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Command 'ImportVmFromOva' i d: 'c8937f2f-4a54-4dc1-9787-6a147d3e318e' child commands '[94c02f37-4f26-401d-802c-11cc2c2bed92, 6ece0932-038c-485e-8d7c-76927c04ea1c]' executions were completed, status 'FAILED' 2022-05-12 17:14:53,123-06 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [192f636b-0dd4-4a61-a673-1b946d7e0b56] Ending command 'org.ovirt.en gine.core.bll.exportimport.ImportVmFromOvaCommand' with failure. 2022-05-12 17:14:53,138-06 INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveAllVmImagesCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Running command: RemoveAllVmImagesCommand intern al: true. Entities affected : ID: 66ff7ebd-7682-4b94-b98d-5ceb76661830 Type: VM 2022-05-12 17:14:53,147-06 INFO [org.ovirt.engine.core.bll.storage.disk.image.RemoveImageCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Running command: RemoveImageCommand internal: true. En tities affected : ID: 00000000-0000-0000-0000-000000000000 Type: Storage 2022-05-12 17:14:53,337-06 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] START, DeleteImageGroupVDSCommand( DeleteImageGro upVDSCommandParameters:{storagePoolId='3a1daa08-d23f-11ec-9e55-000c29861b3c', ignoreFailoverLimit='false', storageDomainId='ddeb67aa-9ec8-488b-9632-5cc19a244815', imageGroupId='6706932e-ef61-4559-a4c3-f6a28a2f92a5', postZeros='false', di scard='false', forceDelete='false'}), log id: 73957233 2022-05-12 17:14:54,575-06 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.DeleteImageGroupVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] FINISH, DeleteImageGroupVDSCommand, return: , log id: 73957233 2022-05-12 17:14:54,576-06 INFO [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] CommandAsyncTask::Adding CommandMultiAsyncTasks object for command '0 4405e70-986f-427a-b298-c1cdc992cc27' 2022-05-12 17:14:54,576-06 INFO [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] CommandMultiAsyncTasks::attachTask: Attaching task '6e789867-0096-40f 0-a5e5-444047a6f056' to command '04405e70-986f-427a-b298-c1cdc992cc27'. 2022-05-12 17:14:54,609-06 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Adding task '6e789867-0096-40f0-a5e5-444047a6f056' (Parent Command 'R emoveAllVmImages', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.. 2022-05-12 17:14:54,779-06 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] BaseAsyncTask::startPollingTask: Starting to poll task '6e789867-0096-40f 0-a5e5-444047a6f056'. 2022-05-12 17:14:54,781-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating NEW_ENTIT Y_ID of org.ovirt.engine.core.common.businessentities.network.VmNetworkStatistics; snapshot: 9d496b9e-f56f-4175-8274-d1cedff52551. 2022-05-12 17:14:54,782-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating NEW_ENTIT Y_ID of org.ovirt.engine.core.common.businessentities.network.VmNetworkInterface; snapshot: 9d496b9e-f56f-4175-8274-d1cedff52551. 2022-05-12 17:14:54,783-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating TRANSIENT _ENTITY of org.ovirt.engine.core.common.businessentities.ReleaseMacsTransientCompensation; snapshot: org.ovirt.engine.core.common.businessentities.ReleaseMacsTransientCompensation@6bea50f2. 2022-05-12 17:14:54,784-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating NEW_ENTIT Y_ID of org.ovirt.engine.core.common.businessentities.VmStatistics; snapshot: 66ff7ebd-7682-4b94-b98d-5ceb76661830. 2022-05-12 17:14:54,784-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating NEW_ENTIT Y_ID of org.ovirt.engine.core.common.businessentities.VmDynamic; snapshot: 66ff7ebd-7682-4b94-b98d-5ceb76661830. 2022-05-12 17:14:54,785-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating NEW_ENTIT Y_ID of org.ovirt.engine.core.common.businessentities.Snapshot; snapshot: 7456013c-8278-463b-8ebc-7b8461f2e43a. 2022-05-12 17:14:54,786-06 INFO [org.ovirt.engine.core.bll.CommandCompensator] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Command [id=c8937f2f-4a54-4dc1-9787-6a147d3e318e]: Compensating NEW_ENTIT Y_ID of org.ovirt.engine.core.common.businessentities.VmStatic; snapshot: 66ff7ebd-7682-4b94-b98d-5ceb76661830. 2022-05-12 17:14:54,805-06 INFO [org.ovirt.engine.core.bll.exportimport.ImportVmFromOvaCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] Lock freed to object 'EngineLock:{exclusiveLocks='[66ff7 ebd-7682-4b94-b98d-5ceb76661830=VM, Nextgen-CC-Tools=VM_NAME]', sharedLocks=''}' 2022-05-12 17:14:54,869-06 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-86) [1a392932] EVENT_ID: IMPORTEXPORT_IMPORT_VM_FAILED(1,153), F ailed to import Vm Nextgen-CC-Tools to Data Center Default, Cluster Default 2022-05-12 17:15:01,472-06 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-26) [] Task id '6e789867-0096-40f0-a5e5-444047a6f056' is in pre-polling period and shou ld not be polled. Pre-polling period is 60000 millis. 2022-05-12 17:15:11,473-06 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-58) [] Task id '6e789867-0096-40f0-a5e5-444047a6f056' is in pre-polling period and shou ld not be polled. Pre-polling period is 60000 millis. ^C

2 2

getting grafana back connect database (to be able to upgrade ovirt again)
by Moritz Baumann 17 May '22

17 May '22

Hi after upgrade from ovirt-4.4 -> ovirt 4.5 We had to face the jdbc problem and that we had old database enties which prohibited an upgrade. I had dropped all dbs and restored from engine backup but now I get the following error when I want to upgrade again [root@ovirt-engine ~]# engine-setup [ INFO ] Stage: Initializing [ INFO ] Stage: Environment setup Configuration files: /etc/ovirt-engine-setup.conf.d/10-packaging-jboss.conf, /etc/ovirt-engine-setup.conf.d/10-packaging.conf, /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20220517153716-whf2lg.log Version: otopi-1.10.0 (otopi-1.10.0-1.el8) [ ERROR ] Failed to execute stage 'Environment setup': Cannot connect to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20220517153716-whf2lg.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20220517153720-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed the log shows: RuntimeError: Cannot connect to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 2022-05-17 15:37:20,461+0200 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment setup': Cannot connec t to database for grafana using existing credentials: ovirt_engine_history_grafana@localhost:5432 How can I get grafana to connect to database again? With kinde regards Moritz

1 0

Re: GlusterFS storage domain - no "Bricks" tab - Ovirt 4.5.0.2
by Abe E 16 May '22

16 May '22

Under your Datacenter or Cluster (1 of those), there is a tick for enable gluster service, make sure thats ticked. What about in the CLI, gluster bricks show there?

1 0

4.5.0.1 hosted-engine VM deployment fails
by mohamedroushdy＠peopleintouch.com 16 May '22

16 May '22

I got this error accross all nodes I tried to deploy the hosted-engine from. Running Ovirt node 4.5.0.1 ERROR MESSAGE: [ INFO ] TASK [ovirt.ovirt.engine_setup : Restart engine after engine-config] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] [ ERROR ] fatal: [localhost -> 192.168.222.81]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Mon, 09 May 2022 10:57:21 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1", "status": 500, "url": "http://localhost/ovirt-engine/services/health"} [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files] [ INFO ] changed: [localhost -> 192.168.222.81] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.81] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} END Thank you,

3 2

GlusterFS storage domain - no "Bricks" tab - Ovirt 4.5.0.2
by Mohamed Roushdy 16 May '22

16 May '22

Hello, I’ve manually prepared my glusterFS volumes by the glusterCLi, one for the Engine, and the other for Data. Both are detected by the engine as “GlusterFS”, however, there’s no “Bricks” tab in both and I cannot see the bricks status from the engine. Is there a required setting or parameter to configure to make it become visible please? Note: I didn’t specify any “mount options” for both volume.s Mohamed Roushdy Team Member – Systems Administrator M: +31 61 55 94 300 [signature_514057058]<https://peopleintouch.com/>[signature_1294661742]<https://www.linkedin.com/authwall?trk=bf&trkInfo=AQGK3xaGp-v5DAAAAX16b8yY54…>

1 0

500 - Internal Server Error after engine-setup oVirt 4.4 on CentOS Stream 8
by Alessio B. 16 May '22

16 May '22

Dear community, after a fresh installation of CentOS Stream 8 and oVirt 4.4 the web portal send a 500 error. This is the history: 3 yum check-update 4 dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm 5 dnf module -y enable javapackages-tools 6 dnf module -y enable pki-deps 7 dnf module -y enable postgresql:12 8 dnf module -y enable mod_auth_openidc:2.3 9 dnf distro-sync --nobest 10 reboot 11 yum install langpacks-en.noarch 12 localectl set-locale LANG=en_US.UTF-8 13 dnf upgrade --nobest 14 dnf install ovirt-engine 15 engine-setup 16 systemctl restart ovirt-engine This is the error in /var/log/ovirt-engine/server.log after the engine-setup 2022-05-16 12:33:42,931+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 56) MSC000001: Failed to start service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: org.jboss.msc.service.StartException in service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Thread.java:829) at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:163) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) ... 8 more Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@2d479b8 at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:239) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@23.0.2.Final//org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@23.0.2.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.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) 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@23.0.2.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) ... 13 more Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@2d479b8 at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:85) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:66) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:122) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:174) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:794) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.util.Beans.injectBoundFields(Beans.java:336) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:347) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.module.ejb.DynamicInjectionPointInjector.inject(DynamicInjectionPointInjector.java:61) at org.jboss.weld.core@3.1.6.Final//org.jboss.weld.module.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:138) at org.jboss.as.weld@23.0.2.Final//org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39) at org.jboss.as.weld@23.0.2.Final//org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@23.0.2.Final//org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.ComponentInstantiatorInterceptor.processInvocation(ComponentInstantiatorInterceptor.java:74) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@23.0.2.Final//org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:111) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@23.0.2.Final//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@23.0.2.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232) ... 28 more Caused by: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 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.weld.core@3.1.6.Final//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:83) ... 59 more Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id' at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(GenericCallMetaDataProvider.java:362) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.initializeWithProcedureColumnMetaData(GenericCallMetaDataProvider.java:114) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.lambda$createMetaDataProvider$0(CallMetaDataProviderFactory.java:127) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:324) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.createMetaDataProvider(CallMetaDataProviderFactory.java:70) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.CallMetaDataContext.initializeMetaData(CallMetaDataContext.java:252) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.simple.AbstractJdbcCall.compileInternal(AbstractJdbcCall.java:313) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.compileInternal(PostgresDbEngineDialect.java:106) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.simple.AbstractJdbcCall.compile(AbstractJdbcCall.java:296) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.getCall(SimpleJdbcCallsHandler.java:157) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:134) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeReadList(SimpleJdbcCallsHandler.java:105) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dao.TagDaoImpl.getAllForParent(TagDaoImpl.java:82) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.TagsDirector.addChildren(TagsDirector.java:116) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.TagsDirector.init(TagsDirector.java:75) ... 64 more Thank you very much for the help!

3 3

upgrade python3
by ariel.fridman＠ibm.com 16 May '22

16 May '22

Hello on ovirt manage engine, based on CentOS stream 8: python3 3.6.8 is end of life. this is a security vulnerability, yum update do not find the new 3.10 ver. please advise how to upgrade it manually. thanks Ariel

3 2

Deployment suddenly fails at engine check
by Harry O 16 May '22

16 May '22

Hi, After the new update, my deployment fails at engine check. What can I do to debug? [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] [ ERROR ] fatal: [localhost -> 192.168.222.12]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content": "<html><head><title>Error</title></head><body>500 - Internal Server Error</body></html>", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Fri, 22 Apr 2022 16:02:04 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6", "status": 500, "url": "http://localhost/ovirt-engine/services/health"} [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files] [ INFO ] changed: [localhost -> 192.168.222.12] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.12] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"}

3 7

Unable to import ovirt vm ova into aws?
by rickey john 15 May '22

15 May '22

I am trying to import a ubuntu 18 os ovirt vm ova template. For this i am creating task with below command aws ec2 import-image --region ap-south-1 --description "Ovirt VM" --license-type BYOL --disk-containers "file://containers.json" aws ec2 describe-import-image-tasks --region ap-south-1 --import-task-ids import-ami-0755c8cd52d08ac88 But unfortunately it is failing with "StatusMessage": "ClientError: No valid partitions. Not a valid volume." error. can someone please guide the steps to export and import ovirt vm ova into aws ec2 instance?

2 1

Upload Cerfiticate issue
by louisb＠ameritech.net 15 May '22

15 May '22

I’m trying to upload an ISO image in ovirt 4.4.10, It’s been a huge challenge to accomplish this. I read several post regarding this issue, I really don’t have s clear understanding of solution to this issue. My experience has not been very fruitful at all. When I try to perform the upload using the web GUI I get the following message in the status column: “Paused by System“. I’ve been reading for roughly three weeks trying to understand and resolve the issue. There is a tremendous amount of discussion centered around changing certificate file located in the directory “etcpki/ovirt-engine”, however it not clear at all what files need to change. My installation is an out-of-box installation with any certificates beginning generated as part of the install process, I’ve imported the certificate that was generated into my browser/Firefox 91.9.0. Based on what I’ve been reading the solution to my problems is that the certificate does not match the certificate defined in the “imageio-service”, my question is why because it was generated as part of the installation? What files in the “/etc/pki/ovirt-engine” must be changed to get things working. Further should or do I copy the certificate saved from the GUI to files under “/etc/pki/ovirt-engine” directory? I feel like I’m so close after six month of reading and re-installs, what do I do next? Thanks

4 20

[IMPORTANT] Upgrade to postgresql-jdbc-42.2.14-1 breaks oVirt Engine 4.4/4.5
by Martin Perina 13 May '22

13 May '22

Hi, Unfortunately we have just found that latest release of postgresql-jdbc-42.2.14-1 breaks existing oVirt Engine 4.4 and 4.5 installations running on CentOS Stream. The workaround is to downgrade to previous version, for example postgresql-jdbc-42.2.3-3 should work fine. Here are detailed instructions: 1. If you have already upgraded to postgresql-jdbc-42.2.14-1, please downgrade to previous version: $ dnf downgrade postgresql-jdbc $ systemctl restart ovirt-engine 2. If you are going to upgrade your oVirt Engine machine, please exclude postgresql-jdbc package from upgrades: $ dnf update -x postgresql-jdbc We have created https://bugzilla.redhat.com/2077794 to track this issue, but unfortunately we don't have a fix yet. Regards, Martin -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

5 8

oVirt Node 4.5.0.2 Async update
by Sandro Bonazzola 13 May '22

13 May '22

oVirt Node 4.5.0.2 Async update On May 13th 2022 the oVirt project released an async update of oVirt Node (4.5.0.2) delivering important impact security fixes, several bug fixes and enhancements. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. Security fixes included in oVirt Node NG 4.5.0.2 Async compared to oVirt 4.5.0.1 Async: - CVE-2022-1271 <https://bugzilla.redhat.com/show_bug.cgi?id=2073310> - important - gzip: arbitrary-file-write vulnerability oVirt Node has been updated, including: - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Node 4.5.0.1: ovirt-node-ng-image-4.5.0.1 ovirt-node-ng-image-4.5.0.2 NetworkManager 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-config-server 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-libnm 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-ovs 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-team 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-tui 1.39.0-1.el8 1.39.2-2.el8 centos-release-ovirt45 8.6-4.el8s 8.7-1.el8s fence-agents-all 4.2.1-89.el8 4.2.1-93.el8 fence-agents-amt-ws 4.2.1-89.el8 4.2.1-93.el8 fence-agents-apc 4.2.1-89.el8 4.2.1-93.el8 fence-agents-apc-snmp 4.2.1-89.el8 4.2.1-93.el8 fence-agents-bladecenter 4.2.1-89.el8 4.2.1-93.el8 fence-agents-brocade 4.2.1-89.el8 4.2.1-93.el8 fence-agents-cisco-mds 4.2.1-89.el8 4.2.1-93.el8 fence-agents-cisco-ucs 4.2.1-89.el8 4.2.1-93.el8 fence-agents-common 4.2.1-89.el8 4.2.1-93.el8 fence-agents-compute 4.2.1-89.el8 4.2.1-93.el8 fence-agents-drac5 4.2.1-89.el8 4.2.1-93.el8 fence-agents-eaton-snmp 4.2.1-89.el8 4.2.1-93.el8 fence-agents-emerson 4.2.1-89.el8 4.2.1-93.el8 fence-agents-eps 4.2.1-89.el8 4.2.1-93.el8 fence-agents-heuristics-ping 4.2.1-89.el8 4.2.1-93.el8 fence-agents-hpblade 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ibmblade 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ifmib 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ilo-moonshot 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ilo-mp 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ilo-ssh 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ilo2 4.2.1-89.el8 4.2.1-93.el8 fence-agents-intelmodular 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ipdu 4.2.1-89.el8 4.2.1-93.el8 fence-agents-ipmilan 4.2.1-89.el8 4.2.1-93.el8 fence-agents-kdump 4.2.1-89.el8 4.2.1-93.el8 fence-agents-mpath 4.2.1-89.el8 4.2.1-93.el8 fence-agents-redfish 4.2.1-89.el8 4.2.1-93.el8 fence-agents-rhevm 4.2.1-89.el8 4.2.1-93.el8 fence-agents-rsa 4.2.1-89.el8 4.2.1-93.el8 fence-agents-rsb 4.2.1-89.el8 4.2.1-93.el8 fence-agents-sbd 4.2.1-89.el8 4.2.1-93.el8 fence-agents-scsi 4.2.1-89.el8 4.2.1-93.el8 fence-agents-vmware-rest 4.2.1-89.el8 4.2.1-93.el8 fence-agents-vmware-soap 4.2.1-89.el8 4.2.1-93.el8 fence-agents-wti 4.2.1-89.el8 4.2.1-93.el8 gdisk 1.0.3-9.el8 1.0.3-11.el8 glib2 2.56.4-158.el8 2.56.4-159.el8 glibc 2.28-197.el8 2.28-199.el8 glibc-common 2.28-197.el8 2.28-199.el8 glibc-langpack-en 2.28-197.el8 2.28-199.el8 gluster-ansible-cluster 1.0-4.el8 1.0-5.el8 gluster-ansible-features 1.0.5-12.el8 1.0.5-13.el8 gluster-ansible-infra 1.0.4-20.el8 1.0.4-21.el8 gluster-ansible-roles 1.0.5-26.el8 1.0.5-27.el8 gzip 1.9-12.el8 1.9-13.el8 libgcc 8.5.0-12.el8 8.5.0-13.el8 libgomp 8.5.0-12.el8 8.5.0-13.el8 libguestfs 1.44.0-5.module_el8.6.0+1087+b42c8331 1.44.0-6.module_el8.7.0+1140+ff0772f9 libguestfs-appliance 1.44.0-5.module_el8.6.0+1087+b42c8331 1.44.0-6.module_el8.7.0+1140+ff0772f9 libguestfs-tools-c 1.44.0-5.module_el8.6.0+1087+b42c8331 1.44.0-6.module_el8.7.0+1140+ff0772f9 libstdc++ 8.5.0-12.el8 8.5.0-13.el8 libvirt 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-client 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-config-network 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-config-nwfilter 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 Libvirt-daemon-driver-interface 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-network 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-nodedev 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-nwfilter 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-qemu 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-secret 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-core 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-disk 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-gluster 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-iscsi 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 Libvirt-daemon-driver-storage-iscsi-direct 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-logical 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-mpath 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-rbd 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-driver-storage-scsi 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-daemon-kvm 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-libs 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libvirt-lock-sanlock 8.0.0-2.module_el8.6.0+1087+b42c8331 8.0.0-6.module_el8.7.0+1140+ff0772f9 libwbclient 4.15.5-5.el8 4.15.5-8.el8 mokutil 0.3.0-11.el8 0.3.0-12.el8 ovirt-node-ng-image-update-placeholder 4.5.0.1-1.el8 4.5.0.2-1.el8 ovirt-release-host-node 4.5.0.1-1.el8 4.5.0.2-1.el8 python3-dns 1.15.0-10.el8 1.15.0-11.el8 python3-slip 0.6.4-11.el8 0.6.4-13.el8 python3-slip-dbus 0.6.4-11.el8 0.6.4-13.el8 qemu-guest-agent 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-img 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-block-curl 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-block-gluster 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-block-iscsi 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-block-rbd 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-block-ssh 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-common 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-core 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-docs 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-hw-usbredir 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-ui-opengl 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-kvm-ui-spice 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 samba-client-libs 4.15.5-5.el8 4.15.5-8.el8 samba-common 4.15.5-5.el8 4.15.5-8.el8 samba-common-libs 4.15.5-5.el8 4.15.5-8.el8 seabios-bin 1.15.0-1.module_el8.6.0+1087+b42c8331 1.16.0-1.module_el8.7.0+1140+ff0772f9 seavgabios-bin 1.15.0-1.module_el8.6.0+1087+b42c8331 1.16.0-1.module_el8.7.0+1140+ff0772f9 selinux-policy 3.14.3-96.el8 3.14.3-97.el8 selinux-policy-targeted 3.14.3-96.el8 3.14.3-97.el8 supermin 5.2.1-1.module_el8.6.0+983+a7505f3f 5.2.1-2.module_el8.7.0+1140+ff0772f9 virt-v2v 1.42.0-18.module_el8.6.0+1046+bd8eec5e 1.42.0-19.module_el8.7.0+1140+ff0772f9 xmlrpc-c 1.51.0-5.el8 1.51.0-8.el8 xmlrpc-c-client 1.51.0-5.el8 1.51.0-8.el8 yajl 2.1.0-10.el8 2.1.0-11.el8 Additional resources: - Read more about the oVirt 4.5.0 release highlights: https://www.ovirt.org/release/4.5.0/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)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.*

1 0

Problem patching & upgrading a RHEL oVirt host
by David White 13 May '22

13 May '22

Hello,I followed some instructions I found in https://www.ovirt.org/documentation/upgrade_guide/ and https://www.ovirt.org/download/install_on_rhel.html by doing the following: 883 subscription-manager repos --enable rhel-8-for-x86_64-baseos-rpms 884 subscription-manager repos --enable rhel-8-for-x86_64-appstream-rpms 885 subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms 886 rpm -i --justdb --nodeps --force "http://mirror.centos.org/centos/8-stream/BaseOS/$(rpm --eval '%_arch')/os/Packages/centos-stream-release-8.6-1.el8.noarch.rpm" 887 cat >/etc/yum.repos.d/CentOS-Stream-Extras.repo <<'EOF' 888 [cs8-extras] 889 name=CentOS Stream $releasever - Extras 890 mirrorlist=http://mirrorlist.centos.org/?release=8-stream&arch=$basearch&re… 891 #baseurl=http://mirror.centos.org/$contentdir/8-stream/extras/$basearch/os/ 892 gpgcheck=1 893 enabled=1 894 gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-Official 895 EOF 896 cat >/etc/yum.repos.d/CentOS-Stream-Extras-common.repo <<'EOF' 897 [cs8-extras-common] 898 name=CentOS Stream $releasever - Extras common packages 899 mirrorlist=http://mirrorlist.centos.org/?release=8-stream&arch=$basearch&re… 900 #baseurl=http://mirror.centos.org/$contentdir/8-stream/extras/$basearch/extras-common/ 901 gpgcheck=1 902 enabled=1 903 gpgkey=https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-Extras 904 EOF 905 echo "8-stream" > /etc/yum/vars/stream 906 dnf distro-sync --nobest 907 reboot 908 dnf install centos-release-ovirt45 909 dnf install centos-release-ovirt45 --enablerepo=extras But now, yum update isn't working because its trying to install centos-stream-release 8.6.1 over redhat-release-8.6. Surely I shouldn't install CentOS stream release over RHEL release, should I? See below: [root@phys1 dwhite]# cat /etc/redhat-releaseRed Hat Enterprise Linux release 8.5 (Ootpa)[root@phys1 dwhite]# yum updateUpdating Subscription Management repositories.Last metadata expiration check: 0:02:01 ago on Thu 12 May 2022 05:59:38 AM EDT.Error: Problem: installed package centos-stream-release-8.6-1.el8.noarch obsoletes redhat-release < 9 provided by redhat-release-8.6-0.1.el8.x86_64 - cannot install the best update candidate for package redhat-release-8.5-0.8.el8.x86_64 - problem with installed package centos-stream-release-8.6-1.el8.noarch(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Sent with ProtonMail secure email.

3 4

Host cannot connect to storage domains
by suporte＠logicworks.pt 12 May '22

12 May '22

After upgrade to 4.5 host cannot be activated because cannot connect to data domain. I have a data domain in NFS (master) and a GlusterFS. It complains about the Gluster domain: The error message for connection node1-teste.acloud.pt:/data1 returned by VDSM was: XML error # rpm -qa|grep glusterfs* glusterfs-10.1-1.el8s.x86_64 glusterfs-selinux-2.0.1-1.el8s.noarch glusterfs-client-xlators-10.1-1.el8s.x86_64 glusterfs-events-10.1-1.el8s.x86_64 libglusterfs0-10.1-1.el8s.x86_64 glusterfs-fuse-10.1-1.el8s.x86_64 glusterfs-server-10.1-1.el8s.x86_64 glusterfs-cli-10.1-1.el8s.x86_64 glusterfs-geo-replication-10.1-1.el8s.x86_64 engine log: 2022-04-27 13:35:16,118+01 ERR OR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [e be79c6] EVENT_ID: VDS_STORAGES_CONNECTION_FAILED(188), Failed to connect Host NODE1 to the Storage Domains DATA1. 2022-04-27 13:35:16,169+01 ERR OR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [e be79c6] EVENT_ID: STORAGE_DOMAIN_ ERR OR(996), The error message for connection node1-teste.acloud.pt:/data1 returned by VDSM was: XML error 2022-04-27 13:35:16,170+01 ERR OR [org.ovirt.engine.core.bll.storage.connection.FileStorageHelper] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [ebe79c6 ] The connection with details 'node1-teste.acloud.pt:/data1' failed because of error code '4106' and error message is: xml error vdsm log: 2022-04-27 13:40:07,125+0100 ERROR (jsonrpc/4) [storage.storageServer] Could not connect to storage server (storageServer:92) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 90, in connect_all con.connect() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 233, in connect self.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 365, in validate if not self.volinfo: File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 352, in volinfo self._volinfo = self._get_gluster_volinfo() File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 405, in _get_gluster_volinfo self._volfileserver) File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ return callMethod() File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> **kwargs) File "<string>", line 2, in glusterVolumeInfo File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in _callmethod raise convert_to_error(kind, result) vdsm.gluster.exception.GlusterXmlErrorException: XML error: rc=0 out=() err=[b'<cliOutput>\n <opRet>0</opRet>\n <opErrno>0</opErrno>\n <opErrstr />\n <volInfo>\n <volumes>\ n <volume>\n <name>data1</name>\n <id>d7eb2c38-2707-4774-9873-a7303d024669</id>\n <status>1</status>\n <statusStr>Started</statusStr>\n <sn apshotCount>0</snapshotCount>\n <brickCount>2</brickCount>\n <distCount>2</distCount>\n <replicaCount>1</replicaCount>\n <arbiterCount>0</arbiterCount> \n <disperseCount>0</disperseCount>\n <redundancyCount>0</redundancyCount>\n <type>0</type>\n <typeStr>Distribute</typeStr>\n <transport>0</tran sport>\n <bricks>\n <brick uuid="08c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b">node1-teste.acloud.pt:/home/brick1<name>node1-teste.acloud.pt:/home/brick1</name><hostUuid>0 8c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b</hostUuid><isArbiter>0</isArbiter></brick>\n <brick uuid="08c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b">node1-teste.acloud.pt:/brick2<name>nod e1-teste.acloud.pt:/brick2</name><hostUuid>08c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b</hostUuid><isArbiter>0</isArbiter></brick>\n </bricks>\n <optCount>23</optCount>\n <options>\n <option>\n <name>nfs.disable</name>\n <value>on</value>\n </option>\n <option>\n <name>transport.addre ss-family</name>\n <value>inet</value>\n </option>\n <option>\n <name>storage.fips-mode-rchecksum</name>\n <value>on</value>\n </option>\n <option>\n <name>storage.owner-uid</name>\n <value>36</value>\n </option>\n <option>\n <name>storag e.owner-gid</name>\n <value>36</value>\n </option>\n <option>\n <name>cluster.min-free-disk</name>\n <value>5%</value>\n </option>\n <option>\n <name>performance.quick-read</name>\n <value>off</value>\n </option>\n <option>\n <name>perfor mance.read-ahead</name>\n <value>off</value>\n </option>\n <option>\n <name>performance.io-cache</name>\n <value>off</value>\n </option>\n <option>\n <name>performance.low-prio-threads</name>\n <value>32</value>\n </option>\n <option>\n < name>network.remote-dio</name>\n <value>enable</value>\n </option>\n <option>\n <name>cluster.eager-lock</name>\n <value>enable< /value>\n </option>\n <option>\n <name>cluster.quorum-type</name>\n <value>auto</value>\n </option>\n <option>\n <name>cluster.server-quorum-type</name>\n <value>server</value>\n </option>\n <option>\n <name>cluster.data-self-heal-algorithm</name>\n <value>full</value>\n </option>\n <option>\n <name>cluster.locking-scheme</name>\n <value>granular</value>\n </option> \n <option>\n <name>cluster.shd-wait-qlength</name>\n <value>10000</value>\n </option>\n <option>\n <name>features.shar d</name>\n <value>off</value>\n </option>\n <option>\n <name>user.cifs</name>\n <value>off</value>\n </option>\n <option>\n <name>cluster.choose-local</name>\n <value>off</value>\n </option>\n <option>\n <name>client.event-threads</name>\ n <value>4</value>\n </option>\n <option>\n <name>server.event-threads</name>\n <value>4</value>\n </option>\n <option>\n <name>performance.client-io-threads</name>\n <value>on</value>\n </option>\n </options>\n </volume>\n <count>1</count>\ n </volumes>\n </volInfo>\n</cliOutput>'] 2022-04-27 13:40:07,125+0100 INFO (jsonrpc/4) [storage.storagedomaincache] Invalidating storage domain cache (sdc:74) 2022-04-27 13:40:07,125+0100 INFO (jsonrpc/4) [vdsm.api] FINISH connectStorageServer return={'statuslist': [{'id': 'dede3145-651a-4b01-b8d2-82bff8670696', 'status': 4106}]} from= ::ffff:192.168.5.165,42132, flow_id=4c170005, task_id=cec6f36f-46a4-462c-9d0a-feb8d814b465 (api:54) 2022-04-27 13:40:07,410+0100 INFO (jsonrpc/5) [api.host] START getAllVmStats() from=::ffff:192.168.5.165,42132 (api:48) 2022-04-27 13:40:07,411+0100 INFO (jsonrpc/5) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::ffff:192.168.5.1 65,42132 (api:54) 2022-04-27 13:40:07,785+0100 INFO (jsonrpc/7) [api.host] START getStats() from=::ffff:192.168.5.165,42132 (api:48) 2022-04-27 13:40:07,797+0100 INFO (jsonrpc/7) [vdsm.api] START repoStats(domains=()) from=::ffff:192.168.5.165,42132, task_id=4fa4e8c4-7c65-499a-827e-8ae153aa875e (api:48) 2022-04-27 13:40:07,797+0100 INFO (jsonrpc/7) [vdsm.api] FINISH repoStats return={} from=::ffff:192.168.5.165,42132, task_id=4fa4e8c4-7c65-499a-827e-8ae153aa875e (api:54) 2022-04-27 13:40:07,797+0100 INFO (jsonrpc/7) [vdsm.api] START multipath_health() from=::ffff:192.168.5.165,42132, task_id=c6390f2a-845b-420b-a833-475605a24078 (api:48) 2022-04-27 13:40:07,797+0100 INFO (jsonrpc/7) [vdsm.api] FINISH multipath_health return={} from=::ffff:192.168.5.165,42132, task_id=c6390f2a-845b-420b-a833-475605a24078 (api:54) 2022-04-27 13:40:07,802+0100 INFO (jsonrpc/7) [api.host] FINISH getStats return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} from=::ffff:192.168.5.165,42132 ( api:54) 2022-04-27 13:40:11,980+0100 INFO (jsonrpc/6) [api.host] START getAllVmStats() from=::1,37040 (api:48) 2022-04-27 13:40:11,980+0100 INFO (jsonrpc/6) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::1,37040 (api:54) 2022-04-27 13:40:12,365+0100 INFO (periodic/2) [vdsm.api] START repoStats(domains=()) from=internal, task_id=f5084096-e5c5-4ca8-9c47-a92fa5790484 (api:48) 2022-04-27 13:40:12,365+0100 INFO (periodic/2) [vdsm.api] FINISH repoStats return={} from=internal, task_id=f5084096-e5c5-4ca8-9c47-a92fa5790484 (api:54) 2022-04-27 13:40:22,417+0100 INFO (jsonrpc/0) [api.host] START getAllVmStats() from=::ffff:192.168.5.165,42132 (api:48) 2022-04-27 13:40:22,417+0100 INFO (jsonrpc/0) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::ffff:192.168.5.1 65,42132 (api:54) 2022-04-27 13:40:22,805+0100 INFO (jsonrpc/1) [api.host] START getStats() from=::ffff:192.168.5.165,42132 (api:48) 2022-04-27 13:40:22,816+0100 INFO (jsonrpc/1) [vdsm.api] START repoStats(domains=()) from=::ffff:192.168.5.165,42132, task_id=a9fb939c-ea1a-4116-a22f-d14a99e6eada (api:48) 2022-04-27 13:40:22,816+0100 INFO (jsonrpc/1) [vdsm.api] FINISH repoStats return={} from=::ffff:192.168.5.165,42132, task_id=a9fb939c-ea1a-4116-a22f-d14a99e6eada (api:54) 2022-04-27 13:40:22,816+0100 INFO (jsonrpc/1) [vdsm.api] START multipath_health() from=::ffff:192.168.5.165,42132, task_id=5eee2f63-2631-446a-98dd-4947f9499f8f (api:48) 2022-04-27 13:40:22,816+0100 INFO (jsonrpc/1) [vdsm.api] FINISH multipath_health return={} from=::ffff:192.168.5.165,42132, task_id=5eee2f63-2631-446a-98dd-4947f9499f8f (api:54) 2022-04-27 13:40:22,822+0100 INFO (jsonrpc/1) [api.host] FINISH getStats return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} from=::ffff:192.168.5.165,42132 ( api:54) -- Jose Ferradeira http://www.logicworks.pt

4 7

How can I set the host to maintenance mode?
by yp414＠163.com 12 May '22

12 May '22

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?

2 1

grafana @ ovirt 4.5.0.6 "origin not allowed"
by diego.ercolani＠ssis.sm 12 May '22

12 May '22

Hello, in my current new installation ovirt-engine-4.5.0.6-1.el8.noarch I have a problem setting up the grafana monitoring portal. I'm supposing that there is some problem regarding connection to ovirt DWH DB. I tested the credentials stored in /etc/grafana/conf/provisioning/datasources/ovirt-dwh.yaml of the ovirt-engine and with psql it seem to work and also the DWH is populated by the engine. But connecting to configuration->data sources and trying to reconfigure the ovirt dwh datasource, when you click on "save & test" it appears a popup telling that the "origin not allowed". I cannot find anything in the grafana log or the httpd log. Can you help?

3 5

Async release for ovirt-engine-appliance is now available
by Sandro Bonazzola 11 May '22

11 May '22

The oVirt community has just released a new version of the ovirt-engine-appliance (4.5-20220511122240) including ovirt-engine-4.5.0.8 and ovirt-dependencies-4.5.2. Full list of changes: NetworkManager 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-libnm 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-team 1.39.0-1.el8 1.39.2-2.el8 NetworkManager-tui 1.39.0-1.el8 1.39.2-2.el8 binutils 2.30-113.el8 2.30-114.el8 centos-release-ovirt45 8.6-4.el8s 8.6-5.el8s cloud-init 21.1-15.el8 22.1-1.el8 fapolicyd 1.1-4.el8 1.1-6.el8 fapolicyd-selinux 1.1-4.el8 1.1-6.el8 fribidi 1.0.4-8.el8 1.0.4-9.el8 gdisk 1.0.3-9.el8 1.0.3-11.el8 glib2 2.56.4-158.el8 2.56.4-159.el8 glibc 2.28-197.el8 2.28-199.el8 glibc-common 2.28-197.el8 2.28-199.el8 glibc-gconv-extra 2.28-197.el8 2.28-199.el8 glibc-langpack-en 2.28-197.el8 2.28-199.el8 grafana 7.5.11-2.el8 7.5.15-1.el8 gzip 1.9-12.el8 1.9-13.el8 kernel 4.18.0-373.el8 4.18.0-383.el8 kernel-core 4.18.0-373.el8 4.18.0-383.el8 kernel-modules 4.18.0-373.el8 4.18.0-383.el8 kernel-tools 4.18.0-373.el8 4.18.0-383.el8 kernel-tools-libs 4.18.0-373.el8 4.18.0-383.el8 krb5-libs 1.18.2-14.el8 1.18.2-17.el8 libgcc 8.5.0-12.el8 8.5.0-13.el8 libgfortran 8.5.0-12.el8 8.5.0-13.el8 libgomp 8.5.0-12.el8 8.5.0-13.el8 libquadmath 8.5.0-12.el8 8.5.0-13.el8 libstdc++ 8.5.0-12.el8 8.5.0-13.el8 mod_auth_openidc 2.3.7-11.module_el8.6.0+1083+4025e8c5 2.4.9.4-1.module_el8.7.0+1136+d8f380b8 openvswitch2.15 2.15.0-81.el8s 2.15.0-88.el8s ovirt-dependencies 4.5.1-1.el8 4.5.2-1.el8 ovirt-engine 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-backend 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-dbscripts 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-restapi 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-base 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-plugin-cinderlib 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-plugin-imageio 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-plugin-ovirt-engine 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-plugin-ovirt-engine-common 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-plugin-vmconsole-proxy-helper 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-setup-plugin-websocket-proxy 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-tools 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-tools-backup 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-ui-extensions 1.3.2-1.el8 1.3.3-1.el8 ovirt-engine-vmconsole-proxy-helper 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-webadmin-portal 4.5.0.4-1.el8 4.5.0.8-1.el8 ovirt-engine-websocket-proxy 4.5.0.4-1.el8 4.5.0.8-1.el8 postgresql-jdbc 42.2.3-3.el8_2 42.2.14-1.el8 python3-dns 1.15.0-10.el8 1.15.0-11.el8 python3-openvswitch2.15 2.15.0-81.el8s 2.15.0-88.el8s python3-ovirt-engine-lib 4.5.0.4-1.el8 4.5.0.8-1.el8 python3-perf 4.18.0-373.el8 4.18.0-383.el8 python3-slip 0.6.4-11.el8 0.6.4-13.el8 python3-slip-dbus 0.6.4-11.el8 0.6.4-13.el8 qemu-guest-agent 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qemu-img 6.2.0-5.module_el8.6.0+1087+b42c8331 6.2.0-12.module_el8.7.0+1140+ff0772f9 qt5-srpm-macros 5.15.2-1.el8 5.15.3-1.el8 rsyslog 8.2102.0-8.el8 8.2102.0-9.el8 rsyslog-elasticsearch 8.2102.0-8.el8 8.2102.0-9.el8 rsyslog-gnutls 8.2102.0-8.el8 8.2102.0-9.el8 rsyslog-mmjsonparse 8.2102.0-8.el8 8.2102.0-9.el8 rsyslog-mmnormalize 8.2102.0-8.el8 8.2102.0-9.el8 selinux-policy 3.14.3-96.el8 3.14.3-97.el8 selinux-policy-targeted 3.14.3-96.el8 3.14.3-97.el8 virt-what 1.18-13.el8 1.18-14.el8 yajl 2.1.0-10.el8 2.1.0-11.el8 -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)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.*

1 0

Console error
by Andrea Chierici 11 May '22

11 May '22

Hi, yesterday I've migrated from 4.4.10.7-1 to 4.5.0.7-1. Installation went fine and no error at all was reported. A problem anyway is now hitting my installation: if I try to open a vm console, I get the error: Failed to complete handshake Error in the pull function It's not a problem on my browser/os since with another 4.4.x ovirt installation, consoles work flawlessly. No modifications at all were made to default settings on console. Any suggestion on how to solve this issue? Haven't seen any previous report on this. Thanks, Andrea

2 1

Async release for ovirt-engine and ovirt-dependencies is now available
by Lev Veyde 11 May '22

11 May '22

The oVirt community has just released a new versions of: * ovirt-engine package (4.5.0.8) fixing - [BZ 2077794 <https://bugzilla.redhat.com/show_bug.cgi?id=2077794>] Upgrading postgresql-jdbc package to 42.2.14-1 breaks ovirt-engine functionality - [BZ 2083230 <https://bugzilla.redhat.com/show_bug.cgi?id=2083230>] engine-setup on a separate machine fails with: Command '/usr/bin/rpm' failed to execute * ovirt-dependencies (4.5.2) fixing: - [BZ 2084027 <https://bugzilla.redhat.com/show_bug.cgi?id=2084027>] CVE-2022-22950 <https://bugzilla.redhat.com/show_bug.cgi?id=2069414> - moderate impact - ovirt-dependencies: spring-expression: Denial of service via specially crafted SpEL expression [ovirt-4.5] The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. Thanks in advance, -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

oVirt and cluster level 4.7
by Gianluca Cecchi 11 May '22

11 May '22

Hello, I've not had the chance to try 4.5 yet, but in a thread I saw reference to a supposed cluster level 4.7. I didn't find anything special in release notes about it, its features and matrix of compatibility levels usable in 4.5 (only 4.7 up or what?) I found this bugzilla, now closed, where in some part it was asked to file a doc part https://bugzilla.redhat.com/show_bug.cgi?id=2021545 Any further information? BTW: what are the versions of libvirt and qemu-kvm used in latest 4.5.x? Thanks, Gianluca

1 0

OVIRT Engine Restore from old Backup
by Abe E 11 May '22

11 May '22

Hey All, I really dont like spamming the forums but the issues I am having keep changing entirely. I am at the point where I can get much closer to rebuilding my engine although my hurtle currently is restoring. When I restore using my most recent backup it is problematic Currently I am restoring by: clean engine install engine-cleanup engine-backup --mode=restore --file=ovirt-engine-backup-20220504011012.backup --log=restore5.log engine-setup Comes up with alot of annoyances as the ID of the old hosted_storage and the new one are mismatched in the GUI. On top of that it is not allowing me to deploy the engine to the 2nd Gluster (3rd one keeps deleting its glusters on reboot since 4.3 Upgrade). Host 1 which runs the hosted engine is not showing as active or unlike, rather it is unresponsive, when I tried to enroll certificates it finally accepted but failed because it said its missing networks, once added it crashed the engine and ha agent wouldnt come up. Now that I think of it, I could have removed the extra networks from being required although it still doesnt benefit me here as I am unable to deploy or reinstall the 2nd Gluster node and the first one will not show its correct state as the host. Should I just be deploying the DB, or is the full file backup fine? My issue here is it takes long to redeploy so the trial an error of failing takes me hours as my backup is from 4.5 engine even though my nodes are on 4.4 as 4.5 keeps causing the catastrophic failure of my whole cluster.

2 6

Async release for ovirt-engine (4.5.0.7) is now available
by Lev Veyde 10 May '22

10 May '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.0.7) that fixes a few important bugs: - Bug 2066084 <https://bugzilla.redhat.com/2066084> - vmconsole-proxy-user certificate expired - cannot access serial console - Bug 2079799 <https://bugzilla.redhat.com/2079799> - issue the internal Certificate Authority for 20 years - Bug 2079835 <https://bugzilla.redhat.com/2079835> - Separate validity length of Apache and internal certificates - Bug 2079890 <https://bugzilla.redhat.com/2079890> - renew certificates sooner before they expire - Bug 2079901 <https://bugzilla.redhat.com/2079901> - allow Enroll Certificate action when host is Non Responsive The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. Thanks in advance, -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

FC Storage recover
by csabany＠freemail.hu 10 May '22

10 May '22

Hi, We have a 4 node cluster (4.4.10) and a standalone manager. We attached to this cluster 4 volumes on FC. Last week we lost the storage canisters (both), but recovered one of them from the storage disks. Unfortunatly only 3 storages came back from offline. I see the 4th FC ID, but it's on "Can't Extend" status. If i check the storages on nodes (lsblk), i can see only the ID not more on this 4th storage. Do you know any recovery tool or any idea for this situation? Thanks csabany

3 14

Re: Ovirt engine Isuue
by Jonathan Grégoire 09 May '22

09 May '22

Hi Strahil, Do you have any hints for me? Jonathan

2 5

OVA Export from Snapshot?
by Alan G 09 May '22

09 May '22

Hi, Is there a way to export an OVA from a snapshot? Or only from the "Active VM" image? Thanks, Alan

2 2

CLI Offline Engine Deployment failing to activate storage domain to gluster error 400
by Abe E 09 May '22

09 May '22

Due to some complications in my 4.4 to 4.5 upgrade that have taken down ovirt for a few days I must go back to 4.4 to salvage what I can and rethink how I will upgrade. Due to that im having to rebuild my engine although I took backups prior. My issue currently is with 4.4 the engine deployment has an error regarding mirrors so I was able to use the ansible script to deploy offline and I am at the activate storage domain portion where it fails I am setting it to glusterfs with the host:/path as gluster-1.d.com:/engine The host machine i am building the engine on has a mount: gluster-1.d.com:/engine 104804356 13827696 90976660 14% /rhev/data-center/mnt/glusterSD/gluster-1.d.com:_engine within the mapping : drwxr-xr-x. 2 vdsm kvm 6 Apr 5 22:15 gluster-1.d.com:_data drwxr-xr-x. 4 vdsm kvm 38 May 5 15:00 gluster-1.d.com:_engine I am able to get into the temp engines ssh and ping the domain although I cannot seem to find where my steps are incorrect. [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Activate storage domain] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400."} Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: VDSM Logs are showing: 2022-05-05 15:30:32,719-0600 INFO (jsonrpc/6) [storage.StorageDomain] sdUUID=7f7cf7a4-f8fa-41a4-8e6a-275230655a8c (fileSD:535) 2022-05-05 15:30:32,734-0600 INFO (jsonrpc/6) [vdsm.api] FINISH getStorageDomainInfo error=Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) from=::ffff:192.168.222.116,53112, flow_id=661d6831, task_id=480acb07-0a53-4bad-aa30-4cd18ce9e5f2 (api:52) 2022-05-05 15:30:32,734-0600 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='480acb07-0a53-4bad-aa30-4cd18ce9e5f2') Unexpected error (task:877) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in _run return fn(*args, **kargs) File "<decorator-gen-131>", line 2, in getStorageDomainInfo File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 2717, in getStorageDomainInfo dom = self.validateSdUUID(sdUUID) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 313, in validateSdUUID sdDom.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 538, in validate raise se.StorageDomainAccessError(self.sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) 2022-05-05 15:30:32,734-0600 INFO (jsonrpc/6) [storage.TaskManager.Task] (Task='480acb07-0a53-4bad-aa30-4cd18ce9e5f2') aborting: Task is aborted: "value=Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) abortedcode=379" (task:1182) 2022-05-05 15:30:32,735-0600 ERROR (jsonrpc/6) [storage.Dispatcher] FINISH getStorageDomainInfo error=Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) (dispatcher:83) 2022-05-05 15:30:32,735-0600 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call StorageDomain.getInfo failed (error 379) in 0.02 seconds (__init__:312) 2022-05-05 15:30:32,743-0600 INFO (jsonrpc/0) [vdsm.api] START createStoragePool(spUUID='fd385045-8355-4ef8-9970-ade84698ad89', poolName='LabNet', masterDom='7f7cf7a4-f8fa-41a4-8e6a-275230655a8c', domList=['7f7cf7a4-f8fa-41a4-8e6a-275230655a8c'], masterVersion=13, lockRenewalIntervalSec=5, leaseTimeSec=60, ioOpTimeoutSec=10, leaseRetries=3) from=::ffff:192.168.222.116,53112, flow_id=661d6831, task_id=b58a0503-98c3-41a9-b5d7-3330e2985133 (api:48) 2022-05-05 15:30:32,743-0600 INFO (jsonrpc/0) [storage.StoragePool] updating pool fd385045-8355-4ef8-9970-ade84698ad89 backend from type NoneType instance 0x7f767080b9d0 to type StoragePoolDiskBackend instance 0x7f760c4dd308 (sp:168) 2022-05-05 15:30:32,743-0600 INFO (jsonrpc/0) [storage.StoragePool] spUUID=fd385045-8355-4ef8-9970-ade84698ad89 poolName=LabNet master_sd=7f7cf7a4-f8fa-41a4-8e6a-275230655a8c domList=['7f7cf7a4-f8fa-41a4-8e6a-275230655a8c'] masterVersion=13 {'LEASERETRIES': 3, 'LEASETIMESEC': 60, 'LOCKRENEWALINTERVALSEC': 5, 'IOOPTIMEOUTSEC': 10} (sp:624) 2022-05-05 15:30:32,743-0600 INFO (jsonrpc/0) [storage.StorageDomain] sdUUID=7f7cf7a4-f8fa-41a4-8e6a-275230655a8c (fileSD:535) 2022-05-05 15:30:32,759-0600 ERROR (jsonrpc/0) [storage.StoragePool] Unexpected error (sp:640) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 635, in create domain.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 538, in validate raise se.StorageDomainAccessError(self.sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) 2022-05-05 15:30:32,759-0600 INFO (jsonrpc/0) [vdsm.api] FINISH createStoragePool error=Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) from=::ffff:192.168.222.116,53112, flow_id=661d6831, task_id=b58a0503-98c3-41a9-b5d7-3330e2985133 (api:52) 2022-05-05 15:30:32,759-0600 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='b58a0503-98c3-41a9-b5d7-3330e2985133') Unexpected error (task:877) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 635, in create domain.validate() File "/usr/lib/python3.6/site-packages/vdsm/storage/fileSD.py", line 538, in validate raise se.StorageDomainAccessError(self.sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/storage/task.py", line 884, in _run return fn(*args, **kargs) File "<decorator-gen-31>", line 2, in createStoragePool File "/usr/lib/python3.6/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/vdsm/storage/hsm.py", line 1006, in createStoragePool leaseParams) File "/usr/lib/python3.6/site-packages/vdsm/storage/sp.py", line 641, in create raise se.StorageDomainAccessError(sdUUID) vdsm.storage.exception.StorageDomainAccessError: Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) 2022-05-05 15:30:32,759-0600 INFO (jsonrpc/0) [storage.TaskManager.Task] (Task='b58a0503-98c3-41a9-b5d7-3330e2985133') aborting: Task is aborted: "value=Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) abortedcode=379" (task:1182) 2022-05-05 15:30:32,759-0600 ERROR (jsonrpc/0) [storage.Dispatcher] FINISH createStoragePool error=Domain is either partially accessible or entirely inaccessible: ('7f7cf7a4-f8fa-41a4-8e6a-275230655a8c',) (dispatcher:83) 2022-05-05 15:30:32,759-0600 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call StoragePool.create failed (error 379) in 0.02 seconds (__init__:312) 2022-05-05 15:30:34,709-0600 INFO (periodic/0) [vdsm.api] START repoStats(domains=()) from=internal, task_id=1b759c4f-ab60-4f3a-8ede-2606f916bf4a (api:48) 2022-05-05 15:30:34,710-0600 INFO (periodic/0) [vdsm.api] FINISH repoStats return={} from=internal, task_id=1b759c4f-ab60-4f3a-8ede-2606f916bf4a (api:54) 2022-05-05 15:30:36,324-0600 INFO (jsonrpc/7) [api.host] START getStats() from=::ffff:192.168.222.116,53112 (api:48) 2022-05-05 15:30:36,344-0600 INFO (jsonrpc/7) [vdsm.api] START repoStats(domains=()) from=::ffff:192.168.222.116,53112, task_id=3b40703b-83dc-4aff-ae92-41158e5ffefc (api:48) 2022-05-05 15:30:36,344-0600 INFO (jsonrpc/7) [vdsm.api] FINISH repoStats return={} from=::ffff:192.168.222.116,53112, task_id=3b40703b-83dc-4aff-ae92-41158e5ffefc (api:54) 2022-05-05 15:30:36,344-0600 INFO (jsonrpc/7) [vdsm.api] START multipath_health() from=::ffff:192.168.222.116,53112, task_id=00953608-b566-4d3d-be62-f20ea77ff7d9 (api:48) 2022-05-05 15:30:36,344-0600 INFO (jsonrpc/7) [vdsm.api] FINISH multipath_health return={} from=::ffff:192.168.222.116,53112, task_id=00953608-b566-4d3d-be62-f20ea77ff7d9 (api:54) 2022-05-05 15:30:36,348-0600 INFO (jsonrpc/7) [api.host] FINISH getStats return={'status': {'code': 0, 'message': 'Done'}, 'info': (suppressed)} from=::ffff:192.168.222.116,53112 (api:54) 2022-05-05 15:30:36,889-0600 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList() from=internal, task_id=a5db87b7-5130-49da-a5c4-5622dbe9d74b (api:48) 2022-05-05 15:30:36,889-0600 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=a5db87b7-5130-49da-a5c4-5622dbe9d74b (api:54) 2022-05-05 15:30:36,889-0600 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:735) 2022-05-05 15:30:37,444-0600 INFO (jsonrpc/2) [api.host] START getAllVmStats() from=::1,33062 (api:48) 2022-05-05 15:30:37,446-0600 INFO (jsonrpc/2) [api.host] FINISH getAllVmStats return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} from=::1,33062 (api:54) 2022-05-05 15:30:37,451-0600 INFO (jsonrpc/3) [api.host] START getAllVmIoTunePolicies() from=::1,33062 (api:48) 2022-05-05 15:30:37,452-0600 INFO (jsonrpc/3) [api.host] FINISH getAllVmIoTunePolicies return={'status': {'code': 0, 'message': 'Done'}, 'io_tune_policies_dict': {'da57699e-e76a-4125-81ce-50821bb09eef': {'policy': [], 'current_values': []}}} from=::1,33062 (api:54)

2 4

vnc certificate renew
by csabany＠freemail.hu 09 May '22

09 May '22

Hi, LAst month a renewed our hosts certificates by the "Enroll certificates" method. The "/etc/pki/vdsm/libvirt-vnc/server-cert.pem" certificate wasn't renewed on my nodes (other certificates were). How can i renew this certificate too? thanks csabany

6 8

Backing up VMs with qemu-img
by David White 08 May '22

08 May '22

I've recently been working with the qemu-img commands for some work that has nothing to do with oVirt or anything inside an oVirt environment. But learning and using these commands have given me an idea for automating backups. I believe that the following is true, but to confirm, would the qemu-img commands be available on the oVirt hosts to take VM snapshots and disk images? Sent with ProtonMail secure email.

3 3

OVIRT Engine Restore from old Backup
by Abe E 07 May '22

07 May '22

Hey All, I really dont like spamming the forums but the issues I am having keep changing entirely. I am at the point where I can get much closer to rebuilding my engine although my hurtle currently is restoring. When I restore using my most recent backup it is problematic Currently I am restoring by: clean engine install engine-cleanup engine-backup --mode=restore --file=ovirt-engine-backup-20220504011012.backup --log=restore5.log engine-setup Comes up with alot of annoyances as the ID of the old hosted_storage and the new one are mismatched in the GUI. On top of that it is not allowing me to deploy the engine to the 2nd Gluster (3rd one keeps deleting its glusters on reboot since 4.3 Upgrade). Host 1 which runs the hosted engine is not showing as active or unlike, rather it is unresponsive, when I tried to enroll certificates it finally accepted but failed because it said its missing networks, once added it crashed the engine and ha agent wouldnt come up. Now that I think of it, I could have removed the extra networks from being required although it still doesnt benefit me here as I am unable to deploy or reinstall the 2nd Gluster node and the first one will not show its correct state as the host. Should I just be deploying the DB, or is the full file backup fine? My issue here is it takes long to redeploy so the trial an error of failing takes me hours as my backup is from 4.5 engine even though my nodes are on 4.4 as 4.5 keeps causing the catastrophic failure of my whole cluster.

2 1

ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[XML error]". HTTP response code is 400.
by yp414＠163.com 07 May '22

07 May '22

[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Execute just a specific set of steps] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Force facts gathering] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the storage interface to be up] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check local VM dir stat] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce local VM dir existence] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch host facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter facts] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter ID] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster name] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster version] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce cluster major version] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce cluster minor version] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set storage_format] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add NFS storage domain] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add glusterfs storage domain] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[XML error]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[XML error]\". HTTP response code is 400."}

2 1

Re: Ovirt engine Isuue
by Jonas Liechti 06 May '22

06 May '22

Try downgrading postgresql-jdbc (https://lists.ovirt.org/archives/list/users@ovirt.org/message/N6MNSV4ZK26V5…) dnf downgrade postgresql-jdbc systemctl restart ovirt-engine Am 05.05.2022 08:18 schrieb sachendra.shukla(a)yagnaiq.com: > > We have installed ovirt engine on centos 8 by follow the below commond > > nano /etc/hosts > your-server-ip centos.example.com > dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm > dnf module enable javapackages-tools -y > dnf module enable pki-deps -y > dnf module enable postgresql:12 -y > dnf update -y > dnf install ovirt-engine -y > engine-setup (when we require latest version > setsebool -P httpd_can_network_connect 1 > firewall-cmd --permanent --zone public --add-port 80/tcp > firewall-cmd --permanent --zone public --add-port 443/tcp > firewall-cmd --reload > > > But we are unable to connect by browser shwing below error. > > 500 - Internal Server Error > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/N7FTY5ZY6SWJH…

3 4

Re: ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[XML error]". HTTP response code is 400.
by Jonas Liechti 06 May '22

06 May '22

I had the same problem and found the solution here: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6IKZ45B2TUCQB… Find cli.py on the host and comment out the line with `value ['stripeCount'] = el.find('stripeCount').text` Am 06.05.2022 19:01 schrieb yp414(a)163.com: > > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Execute just a specific set of steps] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Force facts gathering] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Wait for the storage interface to be up] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Check local VM dir stat] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce local VM dir existence] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch host facts] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster ID] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster facts] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter facts] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter ID] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch Datacenter name] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster name] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Fetch cluster version] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce cluster major version] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Enforce cluster minor version] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set storage_format] > [ INFO ] ok: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add NFS storage domain] > [ INFO ] skipping: [localhost] > [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Add glusterfs storage domain] > [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[XML error]". HTTP response code is 400. > [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[XML error]\". HTTP response code is 400."} > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/XN3H2YZZ56K7P…

1 0

i need change legacy to ovs switch mode on oVirt node's
by sultanu＠inbox.ru 06 May '22

06 May '22

Hello, Team! I need help. I have cluster with 3 nodes oVirt 4.4.10 and common ISCSI storage, i have hosted engine installed on it. I wont change legacy to ovs switch mode, using instruction below: - Install first host and VM using "hosted-engine --deploy" - In the Engine UI, change Cluster switch type from Legacy to OVS - Shutdown the engine VM and stop vdsmd on the host. - Manually change the switch type to ovs in /var/lib/vdsm/persistence/netconf/nets/ovirtmgmt - Restart the host After this changing my hosted engine don't wont start, it says i have a problem with vnet interface, i don't know virtmanager or i don't know vnetuser. When i had return back settings from ovs to legacy mode, hosted engine start without any problem When i had change file /var/lib/vdsm/persistence/netconf/nets/ovirtmgmt on hosts without hosted engine, they are change network mode and start working as ovs switch mode but they say network out of sync. I tryed to migrate hosted engine from host with legacy switch to host with ovs switch hosted engine don't wont migrate. Could you help me please.

2 1

could not start ovirt-engine: TagsDirector.init() fails
by Liebe, André-Sebastian 06 May '22

06 May '22

Hello list, I'm unable to start ovirt-engine after switching from CentOS 8 to CentOS 8-stream, doing a system update and a reboot. A previously done ovirt update from 4.4.9 to 4.4.10 (w/o system reboot but with service restart) went smoothly, so I guess it's somehow caused by one oft he centOS updates? The root cause logged in server.log reads: > org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id' But according to ovirt-engine-setup-*.log a GettagsByparent_id(v_parent_id UUID) function ist created duging engine-setup (which I run after dnf update). When searching google for " org.ovirt.engine.core.bll.TagsDirector.init()" and "'gettagsbyparent_id" I got some results hinting for a faulty PosgreSQL jdbc driver from 2018 Any hints? sincerely André-Sebastian Liebe Zukunftslabor gematik GmbH | Friedrichstr. 136 | 10117 Berlin Tel +49 30 40041-197 | Fax +49 30 40041-111 andre.liebe(a)gematik.de | www.gematik.de Amtsgericht Charlottenburg HRB 96351 Geschäftsführer: Dr. med Markus Leyck Dieken

2 1

Ovirt engine Isuue
by sachendra.shukla＠yagnaiq.com 06 May '22

06 May '22

We have installed ovirt engine on centos 8 by follow the below commond nano /etc/hosts your-server-ip centos.example.com dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm dnf module enable javapackages-tools -y dnf module enable pki-deps -y dnf module enable postgresql:12 -y dnf update -y dnf install ovirt-engine -y engine-setup (when we require latest version setsebool -P httpd_can_network_connect 1 firewall-cmd --permanent --zone public --add-port 80/tcp firewall-cmd --permanent --zone public --add-port 443/tcp firewall-cmd --reload But we are unable to connect by browser shwing below error. 500 - Internal Server Error

3 3

Re: Getting error on oVirt installation
by Kevin Cahill 06 May '22

06 May '22

I am also struggling with this as I try to install a self-hosted engine. I have read every thread in the forum and tried all the suggestions. Here is my most recent attempt (RHEL 8.5, installing oVirt 4.4): Start the hosted engine deployment, then run the command [ # dnf downgrade postgresql-jdbc ] from a virsh console, to downgrade postgresql as soon as the packages are done updating. The downgrade appears to be successful, however the system still fails at 'Check if engine health page is up'. Restarting the oVirt engine [ # systemctl restart oVirt-engine ] immediately after downgrading postgresql does not make any difference. The system times out at the 'Check if engine health page is up'. The log entry where the latest failure started to occur is below. I can include the entire log if needed. Interestingly, the status was 503 this time. In many prior attempts that status was 500. 2022-05-06 09:42:49,744-0400 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:110 fatal: [localhost -> 192.168.222.150]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content": "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n<html><head>\n<title>503 Service Unavailable</title>\n</head><body>\n<h1>Service Unavailable</h1>\n<p>The server is temporarily unable to service your\nrequest due to maintenance downtime or capacity\nproblems. Please try again later.</p>\n</body></html>\n", "content_length": "299", "content_type": "text/html; charset=iso-8859-1", "date": "Fri, 06 May 2022 13:42:49 GMT", "elapsed": 0, "msg": "Status code was 503 and not [200]: HTTP Error 503: Service Unavailable", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6", "status": 503, "url": http://localhost/ovirt-engine/services/health} I would like to know if anyone has had success doing a fresh install of a self-hosted environment since the postgresql issue arose. If so, any pointers would be greatly appreciated. If I get this working I will follow up with exactly what I did.

1 0

Set password for VM
by vysikantsev＠gmail.com 06 May '22

06 May '22

How to set password for Virtual machine?

2 1

HELP ME! Failed to validate the SSL certificate for localhost:443
by natchawi28＠gmail.com 06 May '22

06 May '22

Hi, I'm having an issue with Failed to validate the SSL certificate for localhost:443 during Deploy "hosted-engine." check the log files, found this error: " [TASK] [ovirt.engine-setup: Check if Engine health page is up] [ERROR] fatal:[localhost -> my_fqdn.domain]:FAILED!=>{"attempts":12, "changed":false,"msg":"Failed to validate the SSL certificate for localhost:443. Make sure your managed systems have a valid CA certificate installed. You can use validate_certs=False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this patform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org, /etc/ansible. The exception msg was: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618).", "status": -1, "url": "http://localhost/ovirt-engine/services/health"} " NOTE: ovirt engine VERSION "ovirt-engine-appliance-4.3-20200603.1.0.2.el7.x86_64" We tried googling to resolve this issue but, unfortunately, unsuccessfully. Can someone help us to solve our critical issue? Best regards, Bunnatee

4 10

Getting error on oVirt installation
by mahmutduzenn＠gmail.com 06 May '22

06 May '22

Hello, I downloaded the oVirt node and installed it on my server. DNS etc. I made the settings. I'm getting an error in the Hosted engine installation step. The error message I got is as follows: [ INFO ] TASK [ovirt.ovirt.engine_setup : Run engine-config] [ INFO ] TASK [ovirt.ovirt.engine_setup : Restart engine after engine-config] [ INFO ] skipping: [localhost] [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is up] [ ERROR ] fatal: [localhost -> 192.168.2.94]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset= UTF-8", "date": "Fri, 29 Apr 2022 02:52:21 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "server": "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1", "status": 500, "url": "http://localhost /ovirt-engine/services/health"} [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files] [ INFO ] changed: [localhost -> 192.168.2.94] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.2.94] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Change ownership of copied engine logs] [ INFO ] changed: [localhost -> localhost] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There was a failure deploying the engine on the local engine VM. The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} How can I fix this. thanks

5 8

Lockspace volume not recognized after NFS outage
by joustie＠gmail.com 06 May '22

06 May '22

Hi, I am running a 3 node Ovirt cluster with a hosted-engine. Unfortunately I had a small issue on my NFS server which provides the shared storage for the cluster. During the outage, all VM's went into pause, and the cluster itself (hosted engine) went down. After restoring nfs service (took 2 minutes), the cluster did not recover. The HA agent can't make sense of the lockspace anymore it seems. The agent fails on all nodes. There are several errors in logs but the main one is (I think) in broker.log: MainThread::WARNING::2022-05-01 22:06:06,085::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: Command Image.prepare with args {'imageID': 'c1b7e131-bbde-416b-b2a0-de746a039dfd', 'storagepoolID': '00000000-0000-0000-0000-000000000000', 'volumeID': 'b221ea37-2c59-49bf-89f7-83766fb53717', 'storagedomainID': 'e3b467ec-fdfc-4c7a-9725-8a6d1fe18c6d'} failed: (code=201, message=Volume does not exist: (u'b221ea37-2c59-49bf-89f7-83766fb53717',)) Which is weird because it seems to exist: ls -l /rhev/data-center/mnt/nas.fritz.box:_mnt_HD_HD__a2_hosted__engine__nas/e3b467ec-fdfc-4c7a-9725-8a6d1fe18c6d/images/c1b7e131-bbde-416b-b2a0-de746a039dfd total 1049608 -rw-rw----. 1 vdsm kvm 1073741824 May 1 15:35 b221ea37-2c59-49bf-89f7-83766fb53717 -rw-rw----. 1 vdsm kvm 1048576 Dec 21 2020 b221ea37-2c59-49bf-89f7-83766fb53717.lease -rw-rw-rw-. 1 vdsm kvm 329 Dec 21 2020 b221ea37-2c59-49bf-89f7-83766fb53717.meta When I try to reinitialize the lockspace (stopping the agent etc) I get: ---- File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/unixrpc.py", line 60, in connect self.sock.connect(base64.b16decode(self.host)) File "/usr/lib64/python2.7/socket.py", line 224, in meth return getattr(self._sock,name)(*args) socket.error: [Errno 2] No such file or directory Is there a way to to this manually and also recreate the lockspace volume? I already tried to recreate the lockspace manually with: sanlock direct init -s hosted-engine:0:/rhev/data-center/mnt/nas.fritz.box:_mnt_HD_HD__a2_hosted__engine__nas/e3b467ec-fdfc-4c7a-9725-8a6d1fe18c6d/ha_agent/hosted-engine.lockspace:0 which resulted in: init done -19 No further info and nothing changed. With kind regards, Joost

2 1

OVS switch type for hosted-engine
by Devin A. Bougie 06 May '22

06 May '22

Is it possible to setup a hosted engine using the OVS switch type instead of Legacy? If it's not possible to start out as OVS, instructions for switching from Legacy to OVS after the fact would be greatly appreciated. Many thanks, Devin

4 5

Re: could not start ovirt-engine: TagsDirector.init() fails
by Liebe, André-Sebastian 06 May '22

06 May '22

Donwngrading postgresql-jdbc from 42.2.14-1.el8 to 42.2.3-3.el8_2 (hint from failing ovirt 4.5 deployment https://lists.ovirt.org/archives/list/users@ovirt.org/thread/FA6BLIAIYY7GOX…) did the trick. > dnf downgrade postgresql-jdbc > systemctl restart ovirt-engine sincerely André-Sebastian Liebe Zukunftslabor gematik GmbH | Friedrichstr. 136 | 10117 Berlin Tel +49 30 40041-197 | Fax +49 30 40041-111 andre.liebe(a)gematik.de | www.gematik.de Amtsgericht Charlottenburg HRB 96351 Geschäftsführer: Dr. med Markus Leyck Dieken -----Ursprüngliche Nachricht----- Von: Liebe, André-Sebastian Gesendet: Freitag, 6. Mai 2022 07:46 An: users(a)ovirt.org Betreff: could not start ovirt-engine: TagsDirector.init() fails Hello list, I'm unable to start ovirt-engine after switching from CentOS 8 to CentOS 8-stream, doing a system update and a reboot. A previously done ovirt update from 4.4.9 to 4.4.10 (w/o system reboot but with service restart) went smoothly, so I guess it's somehow caused by one oft he centOS updates? The root cause logged in server.log reads: > org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id' But according to ovirt-engine-setup-*.log a GettagsByparent_id(v_parent_id UUID) function ist created duging engine-setup (which I run after dnf update). When searching google for " org.ovirt.engine.core.bll.TagsDirector.init()" and "'gettagsbyparent_id" I got some results hinting for a faulty PosgreSQL jdbc driver from 2018 Any hints? sincerely André-Sebastian Liebe Zukunftslabor gematik GmbH | Friedrichstr. 136 | 10117 Berlin Tel +49 30 40041-197 | Fax +49 30 40041-111 andre.liebe(a)gematik.de | www.gematik.de Amtsgericht Charlottenburg HRB 96351 Geschäftsführer: Dr. med Markus Leyck Dieken

1 0

Virt group has no storage.owner-uid/gid anymore
by Strahil Nikolov 06 May '22

06 May '22

Hi All, is there any reason why the virt group is no longer having the storage.owner-uid & storage.owner-gid set to 36 ?I've opened an issue to track the reasons/bugfix at https://github.com/gluster/glusterfs/issues/3503 Best Regards,Strahil Nikolov

1 0

Re: [IMPORTANT] Upgrade to postgresql-jdbc-42.2.14-1 breaks oVirt Engine 4.4/4.5
by laj811＠gmail.com 05 May '22

05 May '22

I'm surprised this hasn't been fixed yet. This bug causes the engine setup on new node 4.5 installs to fail. Had I not found this post, I wouldn't have figured out what was going on during the engine setup process. This really needs to be fixed. -Lucas

1 0

ovirt engine restore: Failed to construct component instance
by Rafhael Almeida 05 May '22

05 May '22

Please your help, I restore a engine db correctly in a Fresh Installation on my same server: engine-backup --mode=restore --file=ovirt.2022-04-29_12h00.tar.gz --log=ovirt_log.2022-04-29_12h00.out --restore-permissions --provision-all-databases after engine-setup (I dont' see any warning o error, everything is correct) but when try to accces in my private domain, to access to ovirt-engine, don't work, I see in the files: /etc/ovirt-engine/engine.conf.d/10-setup-cinderlib-database.conf /etc/ovirt-engine/engine.conf.d/10-setup-database.conf /etc/ovirt-engine/engine.conf.d/10-setup-dwh-database.conf another password, in my last engine db, I have another passw to connect to db when i restart the service systemctl restart ovirt-engine y see this logs: *------------my server.log ----------------* Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed 2022-05-04 16:09:25,234-05 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-05-04 16:09:25,238-05 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started (with errors) in 15182ms - Started 1668 of 1888 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-05-04 16:09:25,240-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-05-04 16:09:25,241-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 *--------------------------------------------------* pd. my logs: https://filedn.com/lYVRQ0f0QUTQVmMCo3Bk7DY/server.log my ideas ran out, Please your help !!

2 2

Re: Ovirt 4.5.0.1 self-hosted deployment fails - jboss errors
by hans＠jiflin.nl 05 May '22

05 May '22

Hi, did you resolve this? I am trying to setup a new environment also and can't get past the errors anymore... > Hello, > > I’m trying to deploy a self-hosted engine on Ovirt node v4.5.0.1, but the deployment fails > in the final stages with the following errors in “Server.log” file. > > > I hope that you have an Idea about that. I ran the installer 3 times (cockpit installer. > > Thank you,

2 1

Async release for ovirt-engine (4.5.0.6) is now available
by Lev Veyde 04 May '22

04 May '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.0.6) that fixes a few important bugs: - Bug 2055136 <https://bugzilla.redhat.com/2055136> - virt module is not changed to the correct stream during host upgrade - Bug 2074112 <https://bugzilla.redhat.com/2074112> - VM does not have a disk after restored from backup - Bug 2076465 <https://bugzilla.redhat.com/2076465> - OVA import: importing OVA of Q35/UEFI VM failed with 'Duplicate key nvram' The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0