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

   ### problem
   
   After a clean default install on Rocky 9, trying to upload ISO results in 
"Not ready" status without explanation on the ISO list page. 
   
   The result is soo weird!
   
   1. The ISO events show "ISO Create" as "Completed" with no inkling as to the 
error. 
   2. The main "Events" shows "Error while creating iso. Id: 203 name: 
Rocky-9.5-x86_64-minimal.iso" with no further explanation. 
   3. Under ISO/Zones (??) there is another entry  saying "Timeout waiting for 
response from storage host", when I expand that there is a list of secondary 
storage hosts and each shows "DOWNLOAD ERROR"
   4. On the alerts, it shows "alert.upload.failed | Failed to register 
template: fcfe66dd-ef69-4e49-a9c9-43e4f9e66412 with error: Unable to resolve 
download.rockylinux.org."
   5. Secondary storage page doesn't show storage status like primary storage 
(Up/Down). In fact as far as I can see, there is no way to tell if secondary 
storage configuration is correct / if it's available / connected.
   
   So it seems like there is some sort of issue with DNS but I've tried on all 
machines and each was able to resolve hosts no problem. There is no inkling as 
to which machine failed to resolve download.rockylinux.org. Couldn't find a way 
to retry either.
   
   As a general note, I really didn't expect CloudStack to be so user-hostile. 
Way to many places to look for conflicting and unintelligible errors, alerts 
and notifications, it's just mind boggling. And this is just a very very basic 
use case of "uploading" an ISO (and I am dubios about why is that even 
necessary - when I need an ISO, why can't I just point to a file on one of the 
filesystems???).
   
   ### versions
   
   4.20
   
   ### The steps to reproduce the bug
   
   1. Fresh install on Rocky 9
   2. Try to upload ISO
   ...
   
   
   ### What to do about it?
   
   1. Default install should ensure basic functions like adding an ISO work 
   2. Default install should have reasonable defaults for fundamental things 
like DNS resolution
   3. Error should indicate which physical or virtual machine is failing (in 
this case to DNS resolve download.rockylinux.org) so that user has an inkling 
about what to do to resolve the problem.
   4. User shouldn't have to look at 10 different places to see 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