April 2022 - Users - oVirt List Archives

ERROR! couldn't resolve module/action 'vdo'
by yp414＠163.com 30 Apr '22

30 Apr '22

My newly installed version ovirt-node-ng-installer-4.5.0-2022042607 el8 Deploy the run gluster wizard for single node and the error is as follows: Apr 30 20:03:12 pm-1 cockpit-ws[6288]: ERROR! couldn't resolve module/action 'vdo'. This often indicates a misspelling, missing collection, or incorrect module path. Apr 30 20:03:12 pm-1 cockpit-ws[6288]: The error appears to be in '/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml': line 53, column 3, but may Apr 30 20:03:12 pm-1 cockpit-ws[6288]: be elsewhere in the file depending on the exact syntax problem. Apr 30 20:03:12 pm-1 cockpit-ws[6288]: The offending line appears to be: Apr 30 20:03:12 pm-1 cockpit-ws[6288]: - name: Create VDO with specified size Apr 30 20:03:12 pm-1 cockpit-ws[6288]: ^ here

2 1

hosted engine ovirt-engine-appliance-4.5-20220419162115.1.el8.x86_64 doesn't deploy
by diego.ercolani＠ssis.sm 30 Apr '22

30 Apr '22

I have a full installation of ovirt hosted-engine but it always stop telling: [ ERROR ] fatal: [localhost -> 192.168.222.15]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Sat, 30 Apr 2022 06:56:58 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"} and it's true, I can access the engine via the temporary address (192.168.1.69 or 192.168.222.69) and issuing a curl: [root@ovirt-engine ~]# curl http://localhost/ovirt-engine/services/health <html><head><title>Error</title></head><body>500 - Internal Server Error</body></html>[root@ovirt-engine ~]# it give back an Internal server error. I can not deploy how it's possible to fix? currently the engine is running.. should I try something from inside the engine? Thank you

2 2

HTTP Error 500: Internal Server Error
by yp414＠163.com 30 Apr '22

30 Apr '22

Deploy ovirt-engine-appliance-4.5-20220419162115.1 el8. x86_ 64. The error is reported as follows: INFO ] TASK [ovirt.ovirt.engine_setup : Make sure `ovirt-engine` service is running] [ INFO ] ok: [localhost -> 192.168.222.237] [ 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.222.237]: FAILED! => {"attempts": 30, "changed": false, "connection": "close", "content_encoding": "identity", "content_length": "86", "content_type": "text/html; charset=UTF-8", "date": "Sat, 30 Apr 2022 05:26:11 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.237] [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine] [ INFO ] changed: [localhost -> 192.168.222.237] [ 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"}

3 2

Cannot start ovirt-engine java server - 500 Internal Server Error - after update to 4.4.10
by Jan Burian 30 Apr '22

30 Apr '22

Hi there, I updated hosted ovirt engine from within VM. At first I updated OS - yum update. Then rebooted VM. After VM booted again, I found out I cannot access GUI. Then I found out I had to run engine-setup even when updating between releases. So then I put cluster in global maintenance mode. And run engine-setup. The setup finished successfully. But the GUI is still not accessible. I got 500 Internal server error. Even after reboot or if I run engine-setup again. The errors are the same. In the engine.log is no error. There are errors in server.log. I updated from ovirt-engine-4.4.9.5-1.el8.noarch to ovirt-engine-4.4.10.7-1.el8.noarch. I tried to find some solution, but no luck. The part of error about failing to start engine.ear is common. But the java Caused by: error looks like different then I was able to find. Anyone who is able to find out where the problem lies and any tips for possible solution? Thanks. Regards Honza The errors from server.log: ---------------------------------------------------------------------- 2022-04-29 17:17:44,924+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' 2022-04-29 17:17:45,110+02 INFO [org.springframework.jdbc.support.SQLErrorCodesFactory] (ServerService Thread Pool -- 54) SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase, Hana] 2022-04-29 17:17:45,187+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 54) 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@3d922f2d 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@3d922f2d 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 2022-04-29 17:17:47,922+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 56) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2022-04-29 17:17:47,929+02 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance 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@3d922f2d 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@3d922f2d Caused by: java.lang.reflect.InvocationTargetException Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id'"}} 2022-04-29 17:17:47,948+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-04-29 17:17:48,020+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-04-29 17:17:48,020+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-04-29 17:17:48,020+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-04-29 17:17:48,031+02 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: 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-04-29 17:17:48,076+02 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-04-29 17:17:48,081+02 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started (with errors) in 15315ms - Started 1668 of 1888 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-04-29 17:17:48,083+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-04-29 17:17:48,083+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 ----------------------------------------------------------------------

3 3

Remove ovirt 4.4 repos after upgrade on the engine?
by David White 30 Apr '22

30 Apr '22

Hello, After an update from 4.4 to 4.5 on the Engine, I noticed that the 4.4 repos still exist: Is it safe to run "yum autoremove" on the Engine, followed by removing all of the 4.4 repositories from /etc/yum.repos.d/ ? ovirt-4.4 Latest oVirt 4.4 Releaseovirt-4.4-centos-advanced-virtualization CentOS-8 - Advanced Virtualizationovirt-4.4-centos-ceph-pacific CentOS-8-stream - Ceph Pacificovirt-4.4-centos-gluster8 CentOS-8-stream - Gluster 8ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitchovirt-4.4-centos-openstack-victoria CentOS-8 - OpenStack victoriaovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectdovirt-4.4-centos-opstools-vault CentOS-8 - OpsTools - collectd - vaultovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sacovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzoovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL Sent with ProtonMail secure email.

1 0

[Guide] PXE Booting the oVirt Node 4.5 installer
by nroach44＠nroach44.id.au 30 Apr '22

30 Apr '22

Hi All, I thought I'd post this since there's a few extra steps specific to oVirt Node. Note: This will install in BIOS / MBR / CSM mode, not EFI, so you won't get Secure Boot. Assuming that you already have a DHCP, TFTP, HTTP servers configured to PXE boot. Extract the oVirt Node 4.5 ISO to a folder in your TFTP and HTTP server's working folders - images/pxeboot/vmlinuz, images/pxeboot/initrd.img need to be accessible via TFTP, and the whole ISO (more or less) needs to be accessible via HTTP. I've setup the HTTP and TFTP servers to point at /srv/data/tftp/root, and then extracted the ISO to os/onn45. Copy / edit the interactive-defaults.ks to update the liveimg line to point to the squashfs.img via http: liveimg --url=http://192.168.0.2/os/onn45/ovirt-node-ng-image.squashfs.img You can add things in here to set defaults, if you want: # Keyboard layouts keyboard --xlayouts='au' # System language lang en_AU.UTF-8 # Set starting timezone and NTP server timezone Australia/Perth --isUtc --ntpservers=192.168.0.1 Once that is saved, edit your pxelinux.cfg/default: LABEL onn45 MENU LABEL ^oVirt Node 4.5 KERNEL os/onn45/images/pxeboot/vmlinuz APPEND initrd=os/onn45/images/pxeboot/initrd.img inst.stage2=http://192.168.0.2/os/onn45/ inst.ks=http://192.168.0.2/os/onn45/interactive-defaults-haven.ks Make sure you set the IP addresses and paths are updated to match your setup. Once that's done, you should be able to boot the installer over PXE and install oVirt Node on the machine.

1 0

Ovirt node Virus scan
by marcel d'heureuse 29 Apr '22

29 Apr '22

Hi, I have to scan our 18 nodes with a virus scanner and I have to provide the report to our ito. This nodes have no internet connection and they will not get it. Which software I should use? Clamav? I can shutdown each single node and can scan but I would prefer to have it as cmd running and generate monthly or weekly reports. I don't want to have the daemon running. How did you do this? Br Marcel

2 1

4.5.0.1 ovirt hosted-engine deployment fails
by Mohamed Roushdy 29 Apr '22

29 Apr '22

Hello, I’ve researched a bit about this problem, but none of the proposed solutions fixed it. I’m trying to deploy Ovirt 4.5.0.1 in my lab, and the installation fails with the following error: [cid:image001.png@01D85BDF.87978B40] I’ve even tried to delete the default network bridge (as suggested in some articles), but this didn’t help either. The node has 3 network interfaces, and the hosts file points only to the management interface. Thank you,

1 0

I'm having problems deploying hosted-engine ovirt4.3 on oracle linux 7.9 OS.
by natchawi28＠gmail.com 29 Apr '22

29 Apr '22

I'd like to attach a picture for you to look at. message in log ======================================== TASK [ovirt.engine-setup : Run engine-setup with answerfile] changed: [localhost -> engine.testlab.local] TASK [ovirt.engine-setup : Make sure `ovirt-engine` service is running] ok: [localhost -> engine.testlab.local] TASK [ovirt.engine-setup : Check if Engine health page is up] ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost -> engine.testlab.local]: 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 platform: /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"} Is there anything that I need to change Or what do I need to prepare? Thank.

2 1

unable to upgrade engine to 4.4.10 from 4.4.8
by Diggy Mc 29 Apr '22

29 Apr '22

I am unable to upgrade my hosted engine from version 4.4.8 to 4.4.10. I suspect the problem is because of the obsolescence of CentOS Linux 8. DNF gives me the following error: CentOS Linux 8 - AppStream Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist This is the list of repositories on my engine: appstream CentOS Linux 8 - AppStream baseos CentOS Linux 8 - BaseOS extras CentOS Linux 8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-advanced-virtualization Advanced Virtualization packages for x86_64 ovirt-4.4-centos-ceph-pacific Ceph packages for x86_64 ovirt-4.4-centos-gluster8 CentOS-8 - Gluster 8 ovirt-4.4-centos-nfv-openvswitch CentOS-8 - NFV OpenvSwitch ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-openstack-victoria OpenStack Victoria Repository ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL powertools CentOS Linux 8 - PowerTools Your guidance on how to proceed is much appreciated. Thanks.

4 10

Cannot perform ovirt engine upgrade from ovirt 4.4.10 to 4.5 (ansible conflict)
by ralmeida＠prefecturaloja.gob.ec 29 Apr '22

29 Apr '22

OS: centos stream 8.6 after safe procedure: dnf install -y centos-release-ovirt45 dnf update -y --nobest engine-setup have many errors: nothing provides ansible-core >= 2.12.0 needed by ovirt-engine-4.5.0.5-1.el8.noarch - nothing provides scap-security-guide >= 0.1.60-4 needed by ovirt-engine-4.5.0.5-1.el8.noarch - nothing provides fapolicyd >= 1.1 needed by ovirt-engine-4.5.0.5-1.el8.noarch and i can't finish the engine upgrade... I see many sites like: https://access.redhat.com/solutions/5480561, but not work Please your help pd. logs: https://filedn.com/lYVRQ0f0QUTQVmMCo3Bk7DY/ovirt-engine-setup-2022042612332…

2 1

Q: Cluster compatibility Level and Old v4.2 Nodes
by Andrei Verovski 28 Apr '22

28 Apr '22

Hi, I have quite old nodes from early 4.x era (with CentOS 7.6, cluster compatibility 4.2 level), and oVirt Engine 4.4. 2 nodes have ovirt-release42. Upgrade to oVirt Engine 4.5 engine required cluster compatibility >= 4.3 level. Nodes have been installed with stock CentOS 7.6, not oVirt node image, their upgrade is quite problematic right now. Is it possible to upgrade to cluster compatibility 4.3 while having old 4.2 nodes? Thanks in advance. Andrei

2 1

Storage Domain cloned on iscsi storage and import into oVirt
by Gianluca Gargiulo 28 Apr '22

28 Apr '22

Hi, we have this problem: - Storage Domain iSCSI with a lot of VMs - on iSCSI SAN there is a iSCSI Target with LUN, snapshotted We need to revert only one VM from snapshot. If i revert the snapshot on LUN we revert also other VMs. If i clone the snapshot in the other LUN and attach it to another iscsi target, oVirt can't import "new" storage domain, becouse the VolumeGroupID is same, also

1 0

oVirt Engine Deployment, Networking and Nested Virtualization with VMware Fusion 12.x
by mail＠sunilpatel.co.uk 28 Apr '22

28 Apr '22

Hello, I'm just writing my experiences in case others have come across similar issues or have a similar configuration. I have a single PC, well iMac, home lab environment with VMware Fusion 12.x for Virtualisation. I have tried to setup oVirt 4.5 as a self-hosted engine, deployed on an oVirt 4.5.0 node VM (with nested virtualisation) and the engine deployment fails at this point: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Get local VM IP] [ ERROR ] fatal: [localhost]: FAILED! => {"attempts": 90, "changed": true, "cmd": "virsh -r net-dhcp-leases default | grep -i 00:16:3e:36:90:88 | awk '{ print $5 }' | cut -f1 -d'/'", "delta": "0:00:00.052065", "end": "2022-04-27 21:12:08.176323", "msg": "", "rc": 0, "start": "2022-04-27 21:12:08.124258", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} This seems to be the point where the oVirt Engine has gone though an initial deployment and Ansible is trying to get the IP of the ovirt engine to resume configuration and testing. I believe the VM is running on the oVirt node at this point and there is a Linux bridge between the oVirt node and engine VM. The oVirt node itself has two vNICs, one as the oVirt management network and a second unconfigured NIC to be used for Gluster storage. I access oVirt nodes and Cockpit via a "client" linux VM also on the oVirt management network. It feels like it's this Linux bridge and networking which is not working correctly and causing the deployment to fail. This could be due to the fact that I'm using a virtualised NIC and while promiscuous mode and perhaps some other features are sort-of supported, features needed for this kind of complex networking are not. This is despite the network I'm using being an internal one without the iMAC host connected. WAN connections for oVirt are via a NAT gateway/firewall VM that has the LAN side on the oVirt management network and the WAN side using a bridge with the hosts's NIC (wifi in my case). I did get similar results when I tried to set up OpenStack Neutron Networking; I could not get traffic to cross the Linux Bridge from one Compute Node VM to another. There are a small handful of results of other people coming across this same issue/error and many of them are also using nested Virtualisation either in ESXi, VirtualBox etc The Linux Bridge created by the oVirt engine deployment is (from Cockpit): virbr0Bridge 52:54:00:8F:28:3A Status 192.168.222.1/24, fe80:0:0:0:5054:ff:fe8f:283a/64, fd00:1234:5678:900:0:0:0:1/64 Carrier Yes General Connect automatically IPv4 Address 192.168.222.1/24 IPv6 Address fd00:1234:5678:900:0:0:0:1/64 Bridge Spanning tree protocol Forward delay 2 I have actually seen traffic cross this bridge while watching the stats as the engine was being deployed. If anyone has experienced this problem before and is certain it is due to having a virtualised network, then please let me know. Alternatively, if there is a workaround, that would be great, otherwise I can do more troubleshooting on request but it does feel like this is ultimately a problem related to the platform I'm using - which would not be encountered in a production environment. Thanks

1 0

Q: Non-Operational Node Hosts - Ghost Network Problem
by Andrei Verovski 28 Apr '22

28 Apr '22

Hi, I run into nasty and unexpected problem (oVirt 4.4.7.6-1.el8 ) and 2 non-operational node hosts, which seem relate to ghost network glitch. Everything worked fine for a very long time until I did the following. 1) Made a backup of several VMs which have network “CloudLink-ISP2”. 2) Moved VM disks into another node hosts, which don’t have link “CloudLink-ISP2”, and forgot (preliminary to move) to re-configure network interface (remove link to “CloudLink-ISP2”) as I did before.. 3) Now I have 2 hosts in non-operational mode which is a really big problem - there are only 3 nodes total in a cluster. I tried to fix this by adding 3rd network “CloudLink-ISP2” to each non-operational hosts, and connected ethernet interfaces to a switch. Unfortunately, it didn’t helped either because for whatever reason link did not go up. How I can remove any reference to “CloudLink-ISP2” from node11 and node14? They don’t have any VMs needed that “CloudLink-ISP2”. I edited even inactive VMs and removed “CloudLink-ISP2”. May be there is an option to ignore missing or downed links whn activating node hosts? Thanks in advance for any help. —————————— Logs: 2022-04-27 11:16:59,769+03 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [5ab20328] Host 'node14' is set to Non-Operational, it is missing the following networks: 'CloudLink-ISP2' 2022-04-27 11:16:59,790+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [5ab20328] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node14 does not comply with the cluster ClusterRiga11 networks, the following networks are missing on host: 'CloudLink-ISP2' 2022-04-27 11:16:59,884+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [55610e1e] EVENT_ID: VDS_DETECTED(13), Status of host node14 was set to NonOperational. 2022-04-27 11:16:59,907+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) [5d6ef791] Host 'node14'(aa871d44-94e2-4fdb-aeb3-ca0ae8dc568f) is already in NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds command is skipped. 2022-04-27 11:12:26,050+03 ERROR [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [5400352e] Host 'node11' is set to Non-Operational, it is missing the following networks: 'CloudLink-ISP2' 2022-04-27 11:12:26,070+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [5400352e] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node11 does not comply with the cluster ClusterRiga11 networks, the following networks are missing on host: 'CloudLink-ISP2' 2022-04-27 11:12:26,192+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [57d79e54] EVENT_ID: VDS_DETECTED(13), Status of host node11 was set to NonOperational. 2022-04-27 11:12:26,214+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) [151821e3] Host 'node11'(3c854f9c-2cdd-423e-bca0-37964ba76702) is already in NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds command is skipped. 2022-04-27 11:51:10,539+03 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] Clearing domains data for host node14 2022-04-27 11:51:10,539+03 INFO [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] Host 'node14' moved to Non-Operational state because interface/s which are down are needed by required network/s in the current cluster: 'eno3 (CloudLink-ISP2)' 2022-04-27 11:51:10,569+03 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] EVENT_ID: VDS_SET_NONOPERATIONAL_IFACE_DOWN(603), Host node14 moved to Non-Operational state because interfaces which are down are needed by required networks in the current cluster: 'eno3 (CloudLink-ISP2)'.

2 2

renewing hosts certs when they have expired
by Nathanaël Blanchet 28 Apr '22

28 Apr '22

Hello, I have read some posts about renewing ovirt CA on the engine when it has expired with engine-setup --offline, but nothing about renewing hosts certificates when they have expired. In such a case, we can't interact anymore with hosts and vms are in an unknown state. The formal solution is to put the concerned host into maintenance and enroll certificate, but it implies to stop vms. Here are some messages we can find For those who are concerned, I wrote an ansible role following https://access.redhat.com/solutions/3532921 https://galaxy.ansible.com/natman/ovirt_renew_certs Let me know if it fits to your needs. -- Nathanaël Blanchet Supervision réseau SIRE 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 0

Re: [Ext.] Re: convert disk image to thin-provisioned - Ovirt 4.1
by Arik Hadas 28 Apr '22

28 Apr '22

On Thu, Apr 28, 2022 at 11:11 AM Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> wrote: > > Thanks for responding. > > So, this feature isn't available in 4.4.10 as we are intending to move to that version? It's not available in 4.4.10 See https://bugzilla.redhat.com/show_bug.cgi?id=977778 (introduced in 4.5) > Storage used for that VM is NFS. > > Thanks, > > -----Original Message----- > From: Nir Soffer <nsoffer(a)redhat.com> > Sent: Wednesday, April 27, 2022 10:53 PM > To: Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> > Cc: users(a)ovirt.org; Benny Zlotnik <bzlotnik(a)redhat.com> > Subject: [Ext.] Re: [ovirt-users] convert disk image to thin-provisioned - Ovirt 4.1 > > [CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe] > > On Wed, Apr 27, 2022 at 1:02 PM Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> wrote: > > > > Hello, > > > > I’ve researched a bit on how to convert a disk image from pre-allocated to thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this please? > > Yes! > > 1. Install ovirt 4.5.0 > 2. Use the new convert disk feature > > With oVirt 4.1 you can do this manually. What kind storage are you using? > (NFS, iSCSI?) > > Nir > > _______________________________________________ > 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/KNYUTOLPAUZOX…

1 0

Re: convert disk image to thin-provisioned - Ovirt 4.1
by Nir Soffer 28 Apr '22

28 Apr '22

On Wed, Apr 27, 2022 at 1:02 PM Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> wrote: > > Hello, > > I’ve researched a bit on how to convert a disk image from pre-allocated to thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this please? Yes! 1. Install ovirt 4.5.0 2. Use the new convert disk feature With oVirt 4.1 you can do this manually. What kind storage are you using? (NFS, iSCSI?) Nir

2 1

Zanata user request
by Temuri Doghonadze 27 Apr '22

27 Apr '22

Hello, My name is Temuri and I'd like to ask for account for Zanata to help with translation of ovirt to Georgian. I've done translation of zoiper, FreeCAD, part of gitlab, protonmail, parts of gnome and KDE, etc etc etc. In case of questions feel free to ask. BR, Temuri

4 12

upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
by ingvar.jungenas＠zebware.com 27 Apr '22

27 Apr '22

- having a 4,3 ovirt-engine up and running on centos 7 - Create a new engine machine with centos 8 stream, latests updates - installing packages, restoring ovirt-engine backup from previous host and running ovirt-setup, - When started, no access to the admin console at https://<fqdn>/ovirt-engine. The web proxy will return: 500 Internal error"" - I can access the Grafana login - ovirt-engine.service is started without any systemd errors Any Ideas how to proceed? Log files: /var/log/ovirt-engine/boot.log # No Errors /var/log/ovirt-engine/engine.log # No Errors /var/log/ovirt-engine/server.log # Errors found If I just grep for "ERROR" in server.log 2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 51) 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 2022-04-26 13:52:42,231+02 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance 2022-04-26 13:52:42,568+02 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started (with errors) in 24096ms - Started 1668 of 1888 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) The complete starting sequence from server.log 2022-04-26 13:52:23,322+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "restapi.war" (runtime-name: "restapi.war") 2022-04-26 13:52:24,074+02 INFO [org.jboss.as.remoting] (MSC service thread 1-2) WFLYRMT0001: Listening on 127.0.0.1:8707 2022-04-26 13:52:24,247+02 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0098: Bound non-transactional data source: java:/ENGINEDataSourceNoJTA 2022-04-26 13:52:24,901+02 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete 2022-04-26 13:52:25,194+02 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:/ENGINEDataSource] 2022-04-26 13:52:25,195+02 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:/DWHDataSource] 2022-04-26 13:52:25,530+02 INFO [org.wildfly.security] (MSC service thread 1-3) ELY00001: WildFly Elytron version 1.15.3.Final 2022-04-26 13:52:25,741+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment restapi.war 2022-04-26 13:52:25,999+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "services.war") 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "root.war") 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "docs.war") 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "welcome.war") 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "bll.jar") 2022-04-26 13:52:26,001+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "enginesso.war") 2022-04-26 13:52:26,001+02 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "webadmin.war") 2022-04-26 13:52:26,368+02 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 6.0.22.Final 2022-04-26 13:52:26,752+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 40) WFLYUT0021: Registered web context: '/ovirt-engine/apidoc' for server 'default-server' 2022-04-26 13:52:26,751+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 41) WFLYUT0021: Registered web context: '/ovirt-engine/web-ui' for server 'default-server' 2022-04-26 13:52:26,983+02 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 3.1.6 (Final) 2022-04-26 13:52:28,596+02 WARN [org.jboss.as.dependency.deprecated] (MSC service thread 1-1) WFLYSRV0221: Deployment "deployment.engine.ear.bll.jar" is using a deprecated module ("sun.jdk") which may be removed in future versions without notice. 2022-04-26 13:52:28,604+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment engine.ear 2022-04-26 13:52:28,713+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment root.war 2022-04-26 13:52:28,747+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment docs.war 2022-04-26 13:52:28,863+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment enginesso.war 2022-04-26 13:52:28,929+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment services.war 2022-04-26 13:52:28,978+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment webadmin.war 2022-04-26 13:52:29,007+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment welcome.war 2022-04-26 13:52:29,042+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment bll.jar 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'LockManager' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'Backend' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'OvirtGlusterSchedulingService' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'InitBackendServicesOnStartupBean' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,068+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'ManagedBlockStorageDiskUtil' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,068+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'MacPoolPerCluster' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:30,878+02 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 51) ISPN000128: Infinispan version: Infinispan 'Corona Extra' 11.0.9.Final 2022-04-26 13:52:31,074+02 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 41) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller' 2022-04-26 13:52:31,462+02 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0002: Started dashboard cache from ovirt-engine container 2022-04-26 13:52:31,465+02 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0002: Started inventory cache from ovirt-engine container 2022-04-26 13:52:35,426+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.JsonExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002220: Adding singleton resource org.ovirt.engine.api.restapi.resource.BackendApiResource from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.MappingExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.IOExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.MalformedIdExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,437+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,615+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 45) WFLYUT0021: Registered web context: '/ovirt-engine/api' for server 'default-server' 2022-04-26 13:52:40,024+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type org.codehaus.jackson.map.deser.std.StdScalarDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-04-26 13:52:40,031+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type class org.codehaus.jackson.map.JsonDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-04-26 13:52:40,031+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type class org.codehaus.jackson.map.deser.std.StdDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-04-26 13:52:40,350+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.DefaultGenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type class org.ovirt.engine.core.dao.DefaultReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ModificationDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.SearchDao<org.ovirt.engine.core.common.businessentities.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,352+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.GenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,424+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.springframework.jdbc.core.RowMapper<org.ovirt.engine.core.common.businessentities.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper 2022-04-26 13:52:41,564+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: '/' for server 'default-server' 2022-04-26 13:52:41,603+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) WFLYUT0021: Registered web context: '/ovirt-engine/docs' for server 'default-server' 2022-04-26 13:52:41,659+02 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 47) IJ000407: No lazy enlistment available for ENGINEDataSource 2022-04-26 13:52:41,673+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: '/ovirt-engine/services' for server 'default-server' 2022-04-26 13:52:41,687+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 56) WFLYUT0021: Registered web context: '/ovirt-engine' for server 'default-server' 2022-04-26 13:52:41,825+02 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (ServerService Thread Pool -- 51) Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] 2022-04-26 13:52:41,889+02 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 47) IJ000407: No lazy enlistment available for DWHDataSource 2022-04-26 13:52:41,934+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' 2022-04-26 13:52:41,938+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 44) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2022-04-26 13:52:42,093+02 INFO [org.springframework.jdbc.support.SQLErrorCodesFactory] (ServerService Thread Pool -- 51) SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase, Hana] 2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 51) 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 2022-04-26 13:52:42,231+02 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance 2022-04-26 13:52:42,240+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-04-26 13:52:42,241+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-04-26 13:52:42,241+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-04-26 13:52:42,241+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-04-26 13:52:42,254+02 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report 2022-04-26 13:52:42,564+02 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-04-26 13:52:42,568+02 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started (with errors) in 24096ms - Started 1668 of 1888 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-04-26 13:52:42,574+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-04-26 13:52:42,575+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706

4 5

500 - Internal Server Error
by suporte＠logicworks.pt 27 Apr '22

27 Apr '22

When upgrading from 4.5 to 4.5.0.5 have this 500 - Internal Server Error Engine service is running, postgresql service is running. Maybe wrong postgresql version? # rpm -qa |grep postgr* postgresql-contrib-12.9-3.module_el8.6.0+1043+60b632d3.x86_64 postgresql-server-12.9-3.module_el8.6.0+1043+60b632d3.x86_64 postgresql-jdbc-42.2.14-1.el8.noarch postgresql-12.9-3.module_el8.6.0+1043+60b632d3.x86_64 collectd-postgresql-5.12.0-7.el8s.x86_64 Found this error on /var/log/ovirt-engine/server.log 2022-04-27 11:20:16,003+01 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (ServerService Thread Pool -- 47) Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] 2022-04-27 11:20:16,078+01 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 58) IJ000407: No lazy enlistment available for DWHDataSource 2022-04-27 11:20:16,103+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' 2022-04-27 11:20:16,302+01 INFO [org.springframework.jdbc.support.SQLErrorCodesFactory] (ServerService Thread Pool -- 47) SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase, Hana] 2022-04-27 11:20:16,418+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 57) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2022-04-27 11:20:16,479+01 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 47) 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@24.0.1.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@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:170) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) at org.jboss.as.ee@24.0.1.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@c153250 at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:239) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@24.0.1.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@24.0.1.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@24.0.1.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@24.0.1.Final//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.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@24.0.1.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@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:168) ... 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@c153250 at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:85) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:66) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:122) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:174) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:794) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.util.Beans.injectBoundFields(Beans.java:345) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:356) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.DynamicInjectionPointInjector.inject(DynamicInjectionPointInjector.java:61) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:138) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39) at org.jboss.as.weld@24.0.1.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@24.0.1.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@24.0.1.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@24.0.1.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@24.0.1.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@24.0.1.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@24.0.1.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.7.SP1//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 2022-04-27 11:20:16,506+01 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START" => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance 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@c153250 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@c153250 Caused by: java.lang.reflect.InvocationTargetException Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id'"}} 2022-04-27 11:20:16,545+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-04-27 11:20:16,545+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-04-27 11:20:16,546+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-04-27 11:20:16,546+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-04-27 11:20:16,571+01 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: 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-04-27 11:20:16,785+01 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-04-27 11:20:16,794+01 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 35078ms - Started 1670 of 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-04-27 11:20:16,798+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-04-27 11:20:16,798+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 -- Jose Ferradeira http://www.logicworks.pt

2 2

convert disk image to thin-provisioned - Ovirt 4.1
by Mohamed Roushdy 27 Apr '22

27 Apr '22

Hello, I’ve researched a bit on how to convert a disk image from pre-allocated to thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this please? Thank you,

1 0

4.4 to 4.5, lost Gluster Mounts for data and engine
by Abe E 27 Apr '22

27 Apr '22

Seems the Gluster Node that booted from 4.5 into emergency mode was due to not finding the mounts for gluster_bricks data and engine, its as if it cant see them any more. Once i removed the mounts from /etc/fstab it lets me in, I could boot up. This is node 3 of the Gluster, Arbiter. [root@ovirt-3 ~]# mount -a mount: /gluster_bricks/engine: can't find UUID=45349e37-7a97-4a64-81eb-5fac3fec6477. mount: /gluster_bricks/data: can't find UUID=c0fa1111-0db2-4e08-bb79-be677530aeaa. SDA4 is where the Data and Engine glusters are, although If I try to make a new volumegroup for the gluster, I get this serror If I try try to make a new vgroup I get the following error, it almost sounds as if the partition is corrupted or something, basically i was trying to get it a new UUID. Physical volume '/dev/sda4' is already in volume group 'gluster_vg_sda4' Unable to add physical volume '/dev/sda4' to volume group 'gluster_vg_sda4' /dev/sda4: physical volume not initialized. [root@ovirt-3 ~]# dnf -q list installed centos-release\* ovirt-release\* ovirt-engine Installed Packages centos-release-advanced-virtualization.noarch 1.0-4.el8 @@commandline centos-release-ceph-pacific.noarch 1.0-2.el8 @System centos-release-gluster10.noarch 1.0-1.el8s @System centos-release-messaging.noarch 1-3.el8 @@commandline centos-release-nfv-common.noarch 1-3.el8 @System centos-release-nfv-openvswitch.noarch 1-3.el8 @System centos-release-openstack-xena.noarch 1-1.el8 @@commandline centos-release-opstools.noarch 1-12.el8 @System centos-release-ovirt45.noarch 8.6-1.el8 @@commandline centos-release-rabbitmq-38.noarch 1-3.el8 @@commandline centos-release-storage-common.noarch 2-2.el8 @System centos-release-virt-common.noarch 1-2.el8 @System ovirt-release-host-node.x86_64 4.5.0.1-1.el8 @System [root@ovirt-3 ~]# rpm -qa | grep gluster glusterfs-server-10.1-1.el8s.x86_64 glusterfs-selinux-2.0.1-1.el8s.noarch glusterfs-client-xlators-10.1-1.el8s.x86_64 qemu-kvm-block-gluster-6.2.0-5.module_el8.6.0+1087+b42c8331.x86_64 vdsm-gluster-4.50.0.13-1.el8.x86_64 gluster-ansible-maintenance-1.0.1-12.el8.noarch centos-release-gluster10-1.0-1.el8s.noarch libvirt-daemon-driver-storage-gluster-8.0.0-2.module_el8.6.0+1087+b42c8331.x86_64 python3-gluster-10.1-1.el8s.x86_64 glusterfs-geo-replication-10.1-1.el8s.x86_64 gluster-ansible-cluster-1.0-4.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch libglusterfs0-10.1-1.el8s.x86_64 glusterfs-fuse-10.1-1.el8s.x86_64 glusterfs-events-10.1-1.el8s.x86_64 gluster-ansible-features-1.0.5-12.el8.noarch gluster-ansible-roles-1.0.5-26.el8.noarch glusterfs-10.1-1.el8s.x86_64 libglusterd0-10.1-1.el8s.x86_64 gluster-ansible-infra-1.0.4-20.el8.noarch glusterfs-cli-10.1-1.el8s.x86_64 [root@ovirt-3 ~]#

1 0

(no subject)
by Abe E 27 Apr '22

27 Apr '22

Seems the Gluster Node that booted from 4.5 into emergency mode was due to not finding the mounts for gluster_bricks data and engine, its as if it cant see them any more. Once i removed the mounts from /etc/fstab it lets me in, I could boot up to the node past emergency mode but odd issue. One of the errors: dependency failed for /gluster_bricks/data Subject: Unit gluster_bricks-data.mount has failed This is node 3 of the Gluster, Arbiter. [root@ovirt-3 ~]# mount -a mount: /gluster_bricks/engine: can't find UUID=45349e37-7a97-4a64-81eb-5fac3fec6477. mount: /gluster_bricks/data: can't find UUID=c0fa1111-0db2-4e08-bb79-be677530aeaa.

2 4

Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update
by peter.yu＠guest-tek.com 27 Apr '22

27 Apr '22

Hello, I'm trying to install Ovirt Node 4.4.10 to my server and it gets an error when I'm trying to install iso for my MPT SAS driver by using DUD. In the boot menu, I pressed tab to enter Kernel and added "inst,dd". After that I got a screen shows a list of disk devices and selected USB that has iso file for MPT SAS : "Device : sda1 / Type : Vfat / Label : OEMDRV / UUDI : 6837-8481" Then, I selected drivers to install : "/media/DD-2/rpms/x86_64/kmod-mptsas-3.04.20-6.e18_5.elrepo.x86_64.rpm" And I pressed "C" to continue and gets an error message below : "modprobe : ERROR : could not insert 'mptsas' : invalid argument" Could you please help me what's the next step I can try to fix the issue? Thank you

3 4