- Users - oVirt List Archives

Webadmin and API down with error 500 after updating from 4.4 to 4.5
by lists＠pequod.io 01 May '22

01 May '22

Hello, today i updated from 4.4 to 4.5 and i am no longer able to access my oVirt Cluster. Accessing oVirt Web Interface fails with "500 - Internal Server Error". The API is also dead, My Backup Software and Foreman is no longer able to talk to oVirt. I rebooted the host an ran engine-setup again, it completed without issues but Engine ist still dead. If i ran it again, it tells me now that my cluster is not in global maintanance mode, but "hosted-engine --vm-status" tells me it is still in maintanance mode. one suspect thing i found in server.log is this: 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-26 12:32:32,129+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2022-04-26 12:32:32,137+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@21c5d21d 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@21c5d21d 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-26 12:32:32,158+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-04-26 12:32:32,159+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-04-26 12:32:32,159+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-04-26 12:32:32,159+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-04-26 12:32:32,167+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-26 12:32:32,211+02 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-04-26 12:32:32,226+02 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 18363ms - Started 1670 of 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-04-26 12:32:32,230+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-04-26 12:32:32,231+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 Anyone got an idea whats may be the reason? i am a bit lost here.

4 4

Ovirt engine service fail to start after upgrading from 4.4.9 to 4.4.10
by gantonjo-ovirt＠yahoo.com 01 May '22

01 May '22

Good morning. I have an hosted engine in my VM cluster that fails to start after upgrading from 4.4.9 to 4.4.10. Looking at the ovirt-enginge boot.log, I can see the following: 06:19:46,860 ERROR [org.jboss.as.controller.management-operation] WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "logging")]): java.lang.IllegalArgumentException: Failed to instantiate class "org.ovirt.engine.core.logger.LoggerHandler" for handler "ovirt-logger" at org.jboss.logmanager@2.1.18.Final//org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.lambda$validate$2(AbstractPropertyConfiguration.java:122) at org.jboss.logmanager@2.1.18.Final//org.jboss.logmanager.config.WrappedAction.execute(WrappedAction.java:47) at org.jboss.logmanager@2.1.18.Final//org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:118) at org.jboss.logmanager@2.1.18.Final//org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:336) at org.jboss.logmanager@2.1.18.Final//org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:289) at org.jboss.as.logging@16.0.1.Final//org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:299) at org.jboss.as.logging@16.0.1.Final//org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.lambda$execute$0(LoggingOperations.java:131) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:1047) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:779) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1428) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:546) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:515) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:477) at org.jboss.as.server@16.0.1.Final//org.jboss.as.server.ServerService.boot(ServerService.java:459) at org.jboss.as.server@16.0.1.Final//org.jboss.as.server.ServerService.boot(ServerService.java:412) at org.jboss.as.controller@16.0.1.Final//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.jboss.logmanager@2.1.18.Final//org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.lambda$validate$2(AbstractPropertyConfiguration.java:120) ... 17 more Caused by: org.jboss.modules.ModuleLoadError: org.codehaus.jackson.jackson-core-asl at org.jboss.modules.Module.addPaths(Module.java:1288) at org.jboss.modules.Module.link(Module.java:1644) at org.jboss.modules.Module.getPaths(Module.java:1605) at org.jboss.modules.Module.getPathsUnchecked(Module.java:1628) at org.jboss.modules.Module.loadModuleClass(Module.java:748) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:555) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) at org.jboss.modules.Module.loadModuleClass(Module.java:753) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at org.ovirt.engine.core.logger//org.ovirt.engine.core.logger.LoggerHandler.<init>(LoggerHandler.java:20) ... 22 more Can anyone help me get past this error? Thanks in advance.

2 2

understanding if real engine offline deployment is possible
by vk＠itiviti.com 01 May '22

01 May '22

Hi Everyone, In my compagny, we try to deploy engine on 2 RHEL8 hosts we already installed. We don't have direct internet access, so the RHEL8 hosts have been setup using some internal EL repo (using redhat satellite) We have also duplicated internaly the necessary ovirt repositories, so all ovirt packages can be installed. Now the blocking part is the deployment of the engine. Is it really possible to deploy an engine without having internet connection? We tried several time but never succeeded. I tried with ansible extra var "he_offline_deployment=true", naively thinking it will download necessary packages for the engine through the repositories already configured on the physical hosts (like the physical host act as proxy) I also tried by specifying the ova file with he_appliance_ova=/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20211020135049.1.el8.ova both options have also been tried together (--ansible-extra-vars=he_appliance_ova=/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20211020135049.1.el8.ova --ansible-extra-vars=he_offline_deployment=true) But at the end, it seems the engine deployment process makes the engine to need to reach the ovirt internet repositories, as it always failed with: 2022-04-24 17:39:53,268+0100 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:110 fatal: [localhost -> 192.168.1.154]: FAILED! => {"changed": false, "msg": "Failed to download metadata for repo 'ovirt-4.4-centos-ceph-pacific': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried", "rc": 1, "results": []} FYI the pacific repo works fine when we download packages on physical hosts. ANother thing to know is that before being able to use our internal repo present on our redhat satellite, a system need to install the satellite crtificate, and register to satellite. it would be so nice if we can achieve a fully offline engine deploy (which mean no internet access at all, including the engine itself), but we start to lack of clues if it's really possible. Here are all the ovirt packages installed on the physical hosts: $rpm -qa | grep ovirt ovirt-ansible-collection-1.6.5-1.el8.noarch ovirt-imageio-daemon-2.3.0-1.el8.x86_64 ovirt-host-4.4.9-2.el8.x86_64 ovirt-engine-appliance-4.4-20211020135049.1.el8.x86_64 ovirt-imageio-common-2.3.0-1.el8.x86_64 python3-ovirt-engine-sdk4-4.4.15-1.el8.x86_64 ovirt-host-dependencies-4.4.9-2.el8.x86_64 ovirt-hosted-engine-setup-2.5.4-2.el8.noarch ovirt-imageio-client-2.3.0-1.el8.x86_64 ovirt-vmconsole-host-1.0.9-1.el8.noarch ovirt-provider-ovn-driver-1.2.34-1.el8.noarch cockpit-ovirt-dashboard-0.15.1-1.el8.noarch python3-ovirt-setup-lib-1.3.2-1.el8.noarch ovirt-hosted-engine-ha-2.4.9-1.el8.noarch ovirt-vmconsole-1.0.9-1.el8.noarch thanks a lot in advance

7 10

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