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

   If you have a failed upload of an ISO (or presumably a template as well), 
the failed iso upload does not delete itself from the iso view and you cannot 
delete it.
   
   
![image](https://user-images.githubusercontent.com/48737316/222212915-dff68da7-551f-4496-8309-64c92d10fd19.png)
   
   
   ##### ISSUE TYPE
   Bug report
   
   ##### COMPONENT NAME
   <!--
   UI
   -->
   ~~~
   
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   4.17.2.0
   -->
   
   ~~~
   
   ~~~
   
   ##### CONFIGURATION
   <!--
   Following install from install documents.
   
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Upload an ISO *BEFORE* you have done the SSL approval trick.  Upload fails 
due to network error (bad error message) and then the ISO entry in the ISO 
display remains and cannot be deleted from the UI.  
   
   ##### STEPS TO REPRODUCE
   <!--
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   Either failed ISO entry is auto-removed when the upload fails
   -or-
   Offer a method to remove the failed ISO from the ISO display
   ~~~
   
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   UI thinks that the upload is proceeding (see attached error message above) 
when it clearly isn't.
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   
   ~~~
   


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