Hi Andrija + Rohit,
Yes, as far as I can tell, we followed the upgrade instructions to the letter - except for the version. The instructions still mention systemvm-vmware-4.11.2, we named the new template systemvm-vmware-4.11.3 instead. After upgrading the packages, my colleague checked, and systemvm-vmware-4.11.3 was still a USER template. The mentioned global settings were also unchanged. We ran into the same problem when we upgraded our staging cloud to 4.11.2 a few weeks ago, by the way. Regards, Gregor ________________________________ From: Rohit Yadav <[email protected]> Sent: 13 June 2019 12:49:40 To: dev; [email protected] 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 <[email protected]> Sent: Thursday, June 13, 2019 2:45:50 AM To: dev Cc: [email protected] 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) < [email protected]> 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ć [email protected] www.shapeblue.com<http://www.shapeblue.com> Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue
