justinestruch commented on issue #11081:
URL: https://github.com/apache/cloudstack/issues/11081#issuecomment-3145633275
Hi @DaanHoogland that's correct I did end up getting everything working with
the new 4.20.2 template.
> 1. the old systemvm template is not removed from the primary storages when
all systemvms are destroyed.
This is correct. The VM template in Vsphere was not removed after the new
system template was imported into Cloudstack.
> 2. from the mail, "template_spool_ref seems to have the wrong local_path
and install_path for the systemvm template” is this indeed the problem you
found?
This is correct. When I looked at the DB table template_spool_ref, The
local_path and install_path were not correct. I deleted the entry from the DB
and then cloudstack created a new entry after some time with the new template
info that was proper.
> 3. the newly created VMs from the template show the old version number,
meaning they do not get it from the template. I am not sure this is avoidable
but and/or intended but it seems not right.>
Correct. In cloudstack if I go to Infrastructure > System VMs. The ssvm and
console proxy would show 4.20.1 as the version even though they are using the
4.20.2 template. I'm not sure if there is a way verify what version of the
template the VMs are using by SSHing into them and checking a file or
something. If you happen to know I can confirm this better.
--
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: commits-unsubscr...@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
