Bug 1890010 - Exception when listing disk snapshots under storage domain
Summary: Exception when listing disk snapshots under storage domain
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.3
: ---
Assignee: Ahmad Khiet
QA Contact: Evelina Shames
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-21 08:15 UTC by Ahmad Khiet
Modified: 2020-11-11 06:42 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-11 06:39:26 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+
pm-rhel: blocker?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 111806 0 master MERGED webadmin: use DiskSnapshotsQueryParameters to list disk snapshots 2021-01-12 22:18:26 UTC

Description Ahmad Khiet 2020-10-21 08:15:41 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ahmad Khiet 2020-10-21 08:15:53 UTC
Description of problem:
Exception when listing disk snapshots under storage domain, error messages in the UI, and logs. listing snapshots will not work.

2020-10-20 19:30:22,466+03 ERROR [org.ovirt.engine.core.bll.aaa.SessionDataContainer] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-21) [] Exception in cleanExpiredUsersSessions: ContextNotActiveException: WELD-001303: No active contexts for scope type javax.inject.Singleton
2020-10-20 19:30:24,099+03 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-32) [] Timer update runtime info failed. Exception: ComponentIsStoppedException: WFLYEE0043: Component is stopped
2020-10-20 19:30:24,101+03 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-24) [] Timer update runtime info failed. Exception: ComponentIsStoppedException: WFLYEE0043: Component is stopped
2020-10-20 19:30:26,871+03 ERROR [org.ovirt.engine.core.bll.dwh.DwhHeartBeat] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-76) [] Error updating DWH Heart Beat: IllegalStateException: WFLYWELD0039: Singleton not set for ModuleClassLoader for Module "deployment.engine.ear.bll.jar" from Service Module Loader. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
2020-10-20 19:30:27,101+03 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-69) [] Timer update runtime info failed. Exception: ComponentIsStoppedException: WFLYEE0043: Component is stopped
2020-10-20 19:30:27,103+03 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-77) [] Timer update runtime info failed. Exception: ComponentIsStoppedException: WFLYEE0043: Component is stopped
2020-10-20 19:30:30,104+03 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-41) [] Timer update runtime info failed. Exception: ComponentIsStoppedException: WFLYEE0043: Component is stopped
2020-10-20 19:30:30,105+03 ERROR [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-79) [] Timer update runtime info failed. Exception: ComponentIsStoppedException: WFLYEE0043: Component is stopped
2020-10-20 19:30:31,984+03 ERROR [org.ovirt.engine.core.vdsbroker.ResourceManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-82) [] createCommand failed: WFLYWELD0039: Singleton not set for ModuleClassLoader for Module "deployment.engine.ear.bll.jar" from Service Module Loader. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
2020-10-20 19:30:31,984+03 ERROR [org.ovirt.engine.core.vdsbroker.ResourceManager] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-82) [] Exception: java.lang.reflect.InvocationTargetException
	at jdk.internal.reflect.GeneratedConstructorAccessor123.newInstance(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager.instantiateInjectedCommand(ResourceManager.java:365)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager.createCommand(ResourceManager.java:349)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:395)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source)
	at jdk.internal.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.jboss.weld.core.3.Final//org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51)
	at org.jboss.weld.core.3.Final//org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78)
	at org.ovirt.engine.core.common//org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12)
	at jdk.internal.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.jboss.weld.core.3.Final//org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73)
	at org.jboss.weld.core.3.Final//org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84)
	at org.jboss.weld.core.3.Final//org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72)
	at org.jboss.weld.core.3.Final//org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56)
	at org.jboss.weld.core.3.Final//org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79)
	at org.jboss.weld.core.3.Final//org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyImpl.proceedStoragePoolStats(IrsProxyImpl.java:298)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyImpl.lambda$updatingTimerElapsed$0(IrsProxyImpl.java:258)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyImpl.runInControlledConcurrency(IrsProxyImpl.java:275)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyImpl.updatingTimerElapsed(IrsProxyImpl.java:239)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
	at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:360)
	at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:511)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
	at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:227)
Caused by: java.lang.IllegalStateException: WFLYWELD0039: Singleton not set for ModuleClassLoader for Module "deployment.engine.ear.bll.jar" from Service Module Loader. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
	at org.jboss.as.weld.0.Final//org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:77)
	at org.jboss.as.weld.0.Final//org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:134)
	at org.jboss.weld.core.3.Final//org.jboss.weld.Container.instance(Container.java:57)
	at org.jboss.as.weld.0.Final//org.jboss.as.weld.WeldProvider.getCDI(WeldProvider.java:69)
	at javax.enterprise.api//javax.enterprise.inject.spi.CDI.current(CDI.java:64)
	at deployment.engine.ear//org.ovirt.engine.core.di.Injector.get(Injector.java:55)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.initializeVdsBroker(VdsBrokerCommand.java:65)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.<init>(VdsBrokerCommand.java:46)
	at deployment.engine.ear//org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStatusVDSCommand.<init>(SpmStatusVDSCommand.java:17)
	... 35 more


How reproducible:
always

Steps to Reproduce:
1.storage domain
2.select a storage domain
3. go to Disk Snapshots

Actual results:
Exceptions in the logs, UI errors, and snapshots will not be listed.

Expected results:
getting a table of the snapshots

Comment 2 Nir Soffer 2020-10-21 08:26:22 UTC
Since this is a regression introduced in 4.4.3.7, this must be included
in 4.4.3.

Comment 3 RHEL Program Management 2020-10-21 08:26:31 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 4 Evelina Shames 2020-10-25 13:47:13 UTC
Verified on engine-4.4.3.8-0.1.el8ev

Comment 5 Sandro Bonazzola 2020-11-11 06:39:26 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.