So, I think it's ok to leave this issue aside. I have a suspicion why the templates don't get upgraded, but since we know how to fix them manually, it's not release critical.
We'll open a ticket later. ________________________________ From: Rohit Yadav <rohit.ya...@shapeblue.com> Sent: 13 June 2019 12:49:40 To: dev; users@cloudstack.apache.org Subject: Re: [VOTE] 4.11.3.0 RC1 Gregor, Please follow the following guide, but use the systemvmtemplate URL from the mirror shared on this thread and register the template with the name as "systemvm-<hypervisor>-4.11.3" before upgrading to 4.11.3.0-rc1: http://docs.cloudstack.apache.org/en/4.11.2.0/upgrading/upgrade/upgrade-4.11.html Regards, Rohit Yadav Software Architect, ShapeBlue https://www.shapeblue.com ________________________________ From: Andrija Panic <andrija.pa...@gmail.com> Sent: Thursday, June 13, 2019 2:45:50 AM To: dev Cc: users@cloudstack.apache.org Subject: Re: [VOTE] 4.11.3.0 RC1 Gregor, can you confirm if you followed the steps exactly in regards to template flags and more importantly the actual name - I believe in the code, during upgrading, it will search for specific template name (i.e. systemvm-vmware-4.11.3) and update it's DB values so it becomes a "SYSTEM" instead of "USER" type that it was initially. Andrija On Wed, 12 Jun 2019 at 16:46, Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > Hi Paul, > > > The release notes are still work-in-progress, but the systemvm > > template upgrade section has been updated. You may refer the > > following for systemvm template upgrade testing: > > > http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html > > Thanks! > > We're doing our own tests right now, but ran into problems when > updating the system VMs. > > For one, after registering the new VMware systemvm template, it is > shown as a "USER" template. I'm not sure if this is correct. Is there > an additional step to ensure it is considered a "SYSTEM" template? > I believe this is important so the SSVM and Console Proxy get upgraded. > > Secondly, the upgrade instructions do not mention updating > minreq.sysvmtemplate.version > and > router.template.<hypervisor> > to the > version/name of the new template. > > Without this step, routers won't be upgraded to the new template. > IMHO, it should be mentioned in all upgrade instructions. > > Should I prepare a PR against the documentation? > > Best regards, > Gregor > -- Andrija Panić rohit.ya...@shapeblue.com www.shapeblue.com<http://www.shapeblue.com> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
