cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [cloudstack] shwstppr commented on issue #3480: engine, server, services: fix for respecting secondary storage threshold limit
Date Tue, 30 Jul 2019 07:57:39 GMT
shwstppr commented on issue #3480: engine, server, services: fix for respecting secondary storage
threshold limit
URL: https://github.com/apache/cloudstack/pull/3480#issuecomment-516309301
 
 
   > I think I'm hitting an issue with this one. I cannot sync the templates across a newly
added image store. Here's my steps:
   > 
   > Originally created environement with 4 secondary storages
   > deleted 3 of them so I just have 1 running.
   > On the deleted storages I've clean all files.
   > Registered a few templates in cloudstack and they ended up on the running storage
   > Added back one of the storages and destroyed the SSVM in a while
   > After a day I went back to the machine and the newly added templates were not on the
new image store, just the default ones were added. Also the new secondary storage is not being
mounted on any of the hosts
   
   @borisstoyanov I've verified, the issue you are facing is unrelated to this PR. Currently,
code skips downloading a template to new secondary store if is not public and not featured
and not a system template.
   https://github.com/apache/cloudstack/blob/master/engine/storage/image/src/main/java/org/apache/cloudstack/storage/image/TemplateServiceImpl.java#L517-L520
   If you can repeat your steps while making new template public/fetured(or remove your new
stores, edit template to make it public and re-add store) it will be downloaded instantly
after storage addition. There is no issue with template sync and it should start as soon as
a new storage is added. I fixed that with #3302 
   Not sure if it is by design that a normal template(not featured, not public) will remain
on a single secondary store for a zone. @rhtyd @nvazquez any thoughts?
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message