abh1sar opened a new issue, #12397:
URL: https://github.com/apache/cloudstack/issues/12397

   ### problem
   
   <img width="473" height="437" alt="Image" 
src="https://github.com/user-attachments/assets/1b8fd111-0209-41a0-ac5d-cccd2bf56ec7";
 />
   
   ```
   2026-01-09 10:38:42,505 ERROR [o.a.c.f.m.MessageBusBase] 
(pool-22-thread-1:[]) (logid:) NO EVENT PUBLISH CAN BE WRAPPED WITHIN DB 
TRANSACTION! com.cloud.utils.exception.CloudRuntimeException: NO EVENT PUBLISH 
CAN BE WRAPPED WITHIN DB TRANSACTION!
           at 
org.apache.cloudstack.framework.messagebus.MessageBusBase.publish(MessageBusBase.java:168)
           at 
com.cloud.capacity.CapacityManagerImpl.updateCapacityForHost(CapacityManagerImpl.java:774)
           at 
com.cloud.alert.AlertManagerImpl$1.doInTransactionWithoutResult(AlertManagerImpl.java:301)
           at 
com.cloud.utils.db.TransactionCallbackNoReturn.doInTransaction(TransactionCallbackNoReturn.java:25)
           at 
com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:48)
           at com.cloud.utils.db.Transaction.execute(Transaction.java:38)
           at com.cloud.utils.db.Transaction.execute(Transaction.java:45)
           at 
com.cloud.alert.AlertManagerImpl.lambda$recalculateHostCapacities$0(AlertManagerImpl.java:297)
           at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
           at java.base/java.lang.Thread.run(Thread.java:840)
   
   ```
   Change added in https://github.com/apache/cloudstack/pull/11095
   
   
   ### versions
   
   4.20.2
   
   ### The steps to reproduce the bug
   
   1. Call listCapacity with fetchlatest parameter
   
   
   ### What to do about it?
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to