Damans227 commented on PR #12426:
URL: https://github.com/apache/cloudstack/pull/12426#issuecomment-5623143558

   @kiranchavala fixed. Retested on a fresh `4.20.4.0` env with the latest 
packages, KVM/ol8, MinIO as the S3 store.
   
   I set the KVM template URL back to the old 4.6 one by hand to get your exact 
starting state, then added the S3 store. It corrected itself.
   
   Before:
   
`http://download.cloudstack.org/systemvm/4.6/systemvm64template-4.6.0-kvm.qcow2.bz2`
   
   After:
   
`https://download.cloudstack.org/systemvm/4.20/systemvmtemplate-4.20.2-x86_64-kvm.qcow2.bz2`
   
   And that is what went into the bucket:
   
   ```
   mysql> select url from vm_template where id=3;
   
https://download.cloudstack.org/systemvm/4.20/systemvmtemplate-4.20.2-x86_64-kvm.qcow2.bz2
   
   # mc ls --recursive local/cloudstack-sec
   [2026-09-10 17:35:36 UTC] 504MiB 
template/tmpl/1/3/routing-3/systemvmtemplate-4.20.2-x86_64-kvm.qcow2.bz2
   ```
   
   `template_store_ref` shows `DOWNLOADED` / `Ready`.
   
   I also redid the case from your Feb 19 comment. Deleted the SSVM first, then 
added another S3 store. The management server did the download itself and got 
the right file again:
   
   ```
   17:36:54 DEBUG [o.a.c.s.r.NfsSecondaryStorageResource] (pool-17-thread-1) 
Executing command "DownloadCommand"
      url: 
https://download.cloudstack.org/systemvm/4.20/systemvmtemplate-4.20.2-x86_64-kvm.qcow2.bz2
   17:36:54 INFO  [c.c.s.t.S3TemplateDownloader] Starting download from 
.../systemvmtemplate-4.20.2-x86_64-kvm.qcow2.bz2 to S3 bucket cloudstack-sec2
   
   [2026-09-10 17:37:30 UTC] 504MiB 
template/tmpl/1/3/routing-3/systemvmtemplate-4.20.2-x86_64-kvm.qcow2.bz2
   ```
   
   No `There is no secondary storage VM` message this time.
   


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