t of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error.
>>
>>
>> -Original Message-
>> From: kotipalli venkatesh [mailto:ve
Venkatesh,
Have you opened a jira issue on this? If not, please do -
https://issues.apache.org/jira/browse/CLOUDSTACK
- Si
From: kotipalli venkatesh
Sent: Thursday, March 17, 2016 4:29 AM
To: users@cloudstack.apache.org
Subject: unable to create a VPC
ate.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 wrote:
>
> > Venkatesh,
> >
> > Have you opened a jira issue on this? If not, please do -
&g
che.org/jira/browse/CLOUDSTACK
>
> - Si
>
>
> From: kotipalli venkatesh
> 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,
>
&
m: kotipalli venkatesh [mailto:venkateshcloudt...@gmail.com]
Sent: Thursday, 17 March 2016 2:07 PM
To: users@cloudstack.apache.org
Subject: Re: unable to create a VPC 4.8.0 after upgrading 4.3.1
Hi Glenn,
Thank you for your quick response.
1. Yes, we have upgrade the ssvm,console proxy and routers an
eceived this email in error.
-Original Message-
From: kotipalli venkatesh [mailto:venkateshcloudt...@gmail.com]
Sent: Thursday, 17 March 2016 11:30 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
Xens
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 log
