Hari - I guess you are also supposed to delete the old systemvm template by marking it removed in the DB. Also how would stop/start pick the new template ? I would say just destroy them. Does heart bleed affect VR ?
On 22/04/14 11:04 PM, "Harikrishna Patnala" <harikrishna.patn...@citrix.com> wrote: >Hi, > >1) Register new system vm template #### and change the type = ³SYSTEM² in >vm_template table. (update `cloud`.`vm_template` set type='SYSTEM' where >id = ####) >2) Update vm_template_id = ³####² for all system vm entries in >vm_instance table corresponding to the hypervisor. >3) Stop start the system vms > >-Harikrishna > >On 23-Apr-2014, at 1:15 am, Erik Weber <terbol...@gmail.com> wrote: > >> Hi, >> >> I have an installation that's been upgraded from 4.2.1 to 4.3. >> In light of the heartbleed exploit, I have the need to upgrade the >>system >> vm template. >> >> As part of the upgrade process from 4.2.1 to 4.3, I registered and >> downloaded a new system vm template, named systemvm-xenserver-4.3. >> >> Now when I want a newer systemvm template, what is the proper way of >>doing >> it? >> >> - should I add another template named systemvm-xenserver-4.3 >> - should I remove the old systemvm-xenserver-4.3 template and register a >> new? >> - something else? >> >> >> -- >> Erik Weber >
