[ovirt-users] Re: ClassNotFoundException after upgrade to 4.5
On Tue, Jun 7, 2022 at 10:11 AM Alireza Eskandari wrote: > Thank you for your reply. > I have found the root cause. > There was a manually created file in the > "/etc/ovirt-engine/engine-conf.d/" that inserts a path on top of the > "ENGINE_JAVA_MODULEPATH" variable. > I removed the file and fixed the problem. > Thanks > Great to hear! Regards, Martin > > On Mon, Jun 6, 2022 at 9:53 AM Martin Perina wrote: > >> Hi, >> >> have you followed the upgrade guide? Especially the part to upgrade >> engine setup packages and then run engine-setup to upgrade the rest of >> engine? >> >> >> https://www.ovirt.org/documentation/upgrade_guide/index.html#Updating_the_Red_Hat_Virtualization_Manager_4-4_local_db >> >> If so, could you please provide output of following commands: >> >> rpm -q ovirt-engine >> rpm -q apache-sshd >> >> Thanks, >> Martin >> >> >> On Sat, Jun 4, 2022 at 7:01 PM wrote: >> >>> Hi all, >>> I tried to upgrade my ovirt engine from 4.3.10 to 4.5.0. After restore >>> backup, everything seems ok. I can login to admin panel. >>> But when I want to add new host, I get this exception: >>> >>> 2022-06-01 12:13:04,987-04 ERROR [org.jboss.as.ejb3.invocation] (default >>> task-32) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on >>> component Backend for method public abstract >>> org.ovirt.engine.core.common.queries.QueryReturnValue >>> org.ovirt.engine.core.common.interfaces.BackendLocal.runQuery(org.ovirt.engine.core.common.queries.QueryType,org.ovirt.engine.core.common.queries.QueryParametersBase): >>> javax.ejb.EJBException: WFLYEJB0442: Unexpected Error >>> at org.jboss.as.ejb3@24.0.1.Final >>> //org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:234) >>> 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.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:164) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) >>> at org.jboss.weld.core@3.1.7.SP1 >>> //org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) >>> at org.jboss.as.weld.common@24.0.1.Final >>> //org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.as.ejb3@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.ejb3@24.0.1.Final >>> //org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.as.ejb3@24.0.1.Final >>> //org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.as.ejb3@24.0.1.Final >>> //org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.as.ejb3@24.0.1.Final >>> //org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.as.ejb3@24.0.1.Final >>> //org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) >>> at org.jboss.invocation@1.6.0. >>> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >>> at org.jboss.as.ee@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.invocation@1.6.0. >>>
[ovirt-users] Re: ClassNotFoundException after upgrade to 4.5
Thank you for your reply. I have found the root cause. There was a manually created file in the "/etc/ovirt-engine/engine-conf.d/" that inserts a path on top of the "ENGINE_JAVA_MODULEPATH" variable. I removed the file and fixed the problem. Thanks On Mon, Jun 6, 2022 at 9:53 AM Martin Perina wrote: > Hi, > > have you followed the upgrade guide? Especially the part to upgrade engine > setup packages and then run engine-setup to upgrade the rest of engine? > > > https://www.ovirt.org/documentation/upgrade_guide/index.html#Updating_the_Red_Hat_Virtualization_Manager_4-4_local_db > > If so, could you please provide output of following commands: > > rpm -q ovirt-engine > rpm -q apache-sshd > > Thanks, > Martin > > > On Sat, Jun 4, 2022 at 7:01 PM wrote: > >> Hi all, >> I tried to upgrade my ovirt engine from 4.3.10 to 4.5.0. After restore >> backup, everything seems ok. I can login to admin panel. >> But when I want to add new host, I get this exception: >> >> 2022-06-01 12:13:04,987-04 ERROR [org.jboss.as.ejb3.invocation] (default >> task-32) WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on >> component Backend for method public abstract >> org.ovirt.engine.core.common.queries.QueryReturnValue >> org.ovirt.engine.core.common.interfaces.BackendLocal.runQuery(org.ovirt.engine.core.common.queries.QueryType,org.ovirt.engine.core.common.queries.QueryParametersBase): >> javax.ejb.EJBException: WFLYEJB0442: Unexpected Error >> at org.jboss.as.ejb3@24.0.1.Final >> //org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:234) >> 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.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:164) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) >> at org.jboss.weld.core@3.1.7.SP1 >> //org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) >> at org.jboss.as.weld.common@24.0.1.Final >> //org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.as.ejb3@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.ejb3@24.0.1.Final >> //org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.as.ejb3@24.0.1.Final >> //org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.as.ejb3@24.0.1.Final >> //org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.as.ejb3@24.0.1.Final >> //org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.as.ejb3@24.0.1.Final >> //org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) >> at org.jboss.invocation@1.6.0. >> Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) >> at org.jboss.as.ee@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.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
[ovirt-users] Re: local on host storage domain full, how to clean up
On Sun, Jun 5, 2022 at 7:00 PM Patrick Hibbs wrote: > You can use the all_disks_for_vms view, instead of all_disks. Then add the > vm_id and / or vm_names columns. > > For example: > > /usr/share/ovirt-engine/dbscripts/engine-psql.sh -c "select > disk_id,image_guid,disk_alias,disk_profile_name,vm_id,vm_names from > all_disks_for_vms where disk_content_type='0' order by disk_alias" > > /root/disk_ids-to_vms.txt > > -Patrick Hibbs > > > Thas seems indeed better, thanks! engine=# select disk_id,image_guid,disk_alias,disk_profile_name,vm_id,vm_names from all_disks_for_vms where disk_content_type='0' and disk_alias='ostack-ceph1_Disk3'; disk_id| image_guid | disk_alias | disk_profile_name |vm_id | vm_names --+--++- --+--+-- 1093ada3-65b2-407a-a6b8-fd9529f4a0db | ded7c7c7-477f-44e3-8ac5-8908bde6340c | ostack-ceph1_Disk3 | 2t_1 | 711e5dc6-04a1-42a4-b52c-96685bc19b1f | ostack-ceph1 (1 row) so that I can link the directory and disk file under /2t_1/images/caa6fd69-e371-4476-89eb-cbbae82c2add/images 1093ada3-65b2-407a-a6b8-fd9529f4a0db/ded7c7c7-477f-44e3-8ac5-8908bde6340c with the disk alias ostack-ceph1_Disk3 and with the corresponding vm id as seen from GUI 711e5dc6-04a1-42a4-b52c-96685bc19b1f and its name ostack-ceph1 I'm going to crosscheck in a SAN based configuration if any sort of"translation" is to be done, due to the layout based on LVM and not on filesystem Gianluca ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZZY7DOYGCDVEIKM4Y2OXEVQFIQXRKOKO/
