[I] Template upload and ISO upload events are not generated and also not shown in the events [cloudstack]

Mon, 09 Oct 2023 00:39:33 -0700 


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

   ISSUE TYPE
   
   * Bug/Improvement request
   
   **COMPONENT NAME**
   
   Component: UI
   
   CLOUDSTACK VERSION
   
   Cloudstack version 4.18
   
   **SUMMARY**
   
   Template upload  and ISO upload events are not generated and also not shown 
in the events 
   
   **Steps to reproduce the issue**
   
   
   1. Upload a template/ISO  from local 
   
   2. Navigate to Image> Template/ISO> Event tab
   
   3. There are no events related to the upload template /ISO in the UI 
   
         name: ISO.UPLOAD
         name: TEMPLATE.UPLOAD
     
    **Only Template.CREATE is shown in the Events tab**
     
   ![Screenshot 2023-10-09 at 12 12 18 
PM](https://github.com/apache/cloudstack/assets/1401014/21172bde-9054-485c-b08d-a6ef8c737d5a)
   
   **No events present in the** 
   
   **Images> Template/ISO >Events**
   
   ![Screenshot 2023-10-09 at 12 12 05 
PM](https://github.com/apache/cloudstack/assets/1401014/dd5b72c5-6dcd-4fad-a119-fb3e6b5f8143)
   
   The behavior should be similar to Volume Upload
   
   ![Screenshot 2023-10-09 at 12 16 41 
PM](https://github.com/apache/cloudstack/assets/1401014/dae7f8c8-0e78-4231-8adb-98108fee9924)
   
   
   **Expected behavior**
   
   The event related to template/iso upload should be present both in the 
   
   Events tab and 
   Images> Template >Events
   Images >ISO > Events
   
   
   
   **Actual behavior**
   
   
   The events related to template/iso are not  present both in the 
   
   Events tab and 
   Images> Template >Events
   Images >ISO > Events
   


-- 
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