Hi Wei, We are currently in a situation where, upon checking the link https://download.cloudstack.org/systemvm/4.19/, we noticed that there is no SystemVM template available specifically for version 4.19.3. The latest available template listed is for version 4.19.1, with the last update dated 2024-07-08. Additionally, according to the official documentation https://docs.cloudstack.apache.org/en/4.19.3.0/upgrading/upgrade/upgrade-4.19.html, the SystemVM template referenced is also version 4.19.1.
On Thu, Jun 19, 2025 at 2:51 PM Raghava Yerubandi < raghavayeruba...@gmail.com> wrote: > Hello Wei, > > Thanks for the update. After downloading the updated SystemVM, should we > remove the old SystemVM template (4.19.1). > > > On Thu, Jun 19, 2025 at 12:32 PM Wei ZHOU <ustcweiz...@gmail.com> wrote: > >> Hi, >> >> The version of systemvm template for ACS 4.19.3 is still 4.19.1 >> You can find the systemvm templates on >> https://download.cloudstack.org/systemvm/4.19/ >> >> -Wei >> >> >> >> On Thu, Jun 19, 2025 at 8:43 AM Raghava Yerubandi < >> raghavayeruba...@gmail.com> wrote: >> >> > Hello Community, >> > >> > I need some clarification regarding a few observations after our recent >> > upgrade. >> > >> > We recently upgraded our CloudStack environment from version *4.19.1* to >> > *4.19.3* by following the official documentation. >> > >> > 1. >> > >> > *SystemVM Template:* >> > Is it necessary to download a new SystemVM template for this upgrade? >> > We noticed that the existing SystemVM templates from 4.19.1 and >> 4.19.3 look >> > the same. >> > 2. >> > >> > *SystemVM Version Mismatch:* >> > After the upgrade, we recreated the SystemVMs (Console Proxy VM and >> > Secondary Storage VM). While the SystemVM version displayed in the >> > dashboard shows 4.19.3, after logging into the VMs, it shows the >> internal >> > version as 4.19.1. Is this behavior expected? >> > 3. >> > >> > *Virtual Router Versioning:* >> > Post-upgrade, we patched the Virtual Router from the dashboard, the >> > software version shows as 4.19.3.0, and the version still displays as >> > 4.19.1. Is this the correct behavior? >> > >> > Below are the screenshots attached. >> > >> > [image: image.png] >> > [image: image.png] >> > >> > [image: image.png] >> > >> > >> > >> >
