You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by GitBox <gi...@apache.org> on 2020/12/06 20:08:56 UTC

[GitHub] [cloudstack-primate] PaulAngus edited a comment on issue #835: [FEATURE] server: update template to another template type

PaulAngus edited a comment on issue #835:
URL: https://github.com/apache/cloudstack-primate/issues/835#issuecomment-739556047


   Thanks for clarifying @ravening, but that make might make it worse as:
   
   - The description does not suggest that the system VM template that was active is updated to inactive. - leaving the DB in an inconsistent state.
   - The testing description only says that only user -> system was tested.  
   - And I can't _see_ anything that looks like the backend operations like downloading system VM templates to all secondary storage pools. 
   - User VM templates are only supposed to be in one pool, so what happens there? Cloudstack isn't going to be expecting user templates in all sec storage pools - hows deletion and GC going to work?
   - Builtin templates should be in all secondary storage pools as well. do they get downloaded?
   
   


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