Hi Glenn,
Thank you for your quick response.
1. Yes, we have upgrade the ssvm,console proxy and routers and we have
checked the version also it is showing 4.6.0.
But the problem is when ever rebooted the existing router getting flask
error and router destroyed and we are unable to create a new network.
coming to 3 point your saying global settings :
Please let us know what changes we need to do in global settings regarding
router.template.xenserver.
please look in to this below messages in our present global settings
router.template.xenserver
*Name* *Description* *Value*
router.template.xenserver Name of the default router template on xenserver
SystemVMtemplate(Xenserver)
Regards,
Venkatesh.k
On Thu, Mar 17, 2016 at 5:13 PM, Simon Weller <swel...@ena.com> wrote:
> Venkatesh,
>
> Have you opened a jira issue on this? If not, please do -
> https://issues.apache.org/jira/browse/CLOUDSTACK
>
> - Si
>
> ________________________________________
> From: kotipalli venkatesh <venkateshcloudt...@gmail.com>
> Sent: Thursday, March 17, 2016 4:29 AM
> To: users@cloudstack.apache.org
> Subject: unable to create a VPC 4.8.0 after upgrading 4.3.1
>
> Hi All,
>
> Our cloud information:
>
> CS version: 4.3.1
> Xenserver Version : 6.2
>
> we are using 4.6 Template to upgrade from 4.3.1 to 4.8.0.
>
> After upgrade 4.3.1 to 4.8.0 we are unable to create a network(VPC) and if
> we are rebooting an existing VPC router is then we are getting below
> error:
>
> *r-14VM login: Traceback (most recent call last):*
>
> * File "/opt/cloud/bin/baremetal-vr.py", line 28, in <module>*
> * from flask import flask*
> *ImportError: No module named flask*
>
>
> Is there any one facing this type of same scenario please give me
> suggestions so we can step in to the next level.
>
> Since we are keep on posting 2 months back. but still we are facing the
> same issue now a days all guys are full busy to share the mutual
> knowledge.
>
> we are suspecting that instead of 4.8 template 4.6 template using it might
> be cause.
> Please release the 4.8.0 Template as soon as possible.
>
> Regards,
> Venkatesh.k
>
