g was to change the type of Xen Template.
>
> Cheers
> Grégoire
>
> -Message d'origine-
> De : Andrija Panic [mailto:andrija.pa...@gmail.com]
> Envoyé : vendredi 12 octobre 2018 20:48
> À : users
> Objet : Re: System VM version - CS 4.11.1
>
> Hi,
&g
12 octobre 2018 20:48
À : users
Objet : Re: System VM version - CS 4.11.1
Hi,
check the global variables router.template.kvm and
router.template.xenserver they should have the value of the exact name of
the new systemVM templates as you registered them...
Let us know if this fixes the issue
De : Grégoire Lamodière [mailto:g.lamodi...@dimsi.fr]
> Envoyé : vendredi 12 octobre 2018 18:31
> À : users@cloudstack.apache.org
> Objet : System VM version - CS 4.11.1
>
> Hi All,
>
> I have a strange behavior on a CS 4.11.1 deployment (upgraded from 4.11.0)
>
> This d
I think someone else already wrote the same workarround on this list (UPDATE DB
SET type='SYSTEM')
Cheers.
Grégoire
-Message d'origine-
De : Grégoire Lamodière [mailto:g.lamodi...@dimsi.fr]
Envoyé : vendredi 12 octobre 2018 18:31
À : users@cloudstack.apache.org
Objet : System VM version - C
Hi All,
I have a strange behavior on a CS 4.11.1 deployment (upgraded from 4.11.0)
This deployment has a mixed cluster (KVM / CXP-NG 7.4).
Both systemvm templates (KVM / XEN) have been deployed with proper URL
When systemvm are on one KVM host, they report proper version.
On XCP, they report
