Hi Alena,
Thanks for the tips - very useful. It appears as though the VpcVirtualRouter
was inserted correctly during the upgrade (which we followed, using the repos
for kvm upgrade, from
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Release_Notes/upgrade-instructions.html#upgrade-from-3.0.2-to-4.0.1).
Executing addNetworkServiceProvider returns:
"com.cloud.utils.exception.CloudRuntimeException: The 'VpcVirtualRouter'
provider already exists on physical network : 1"
The return:
<listnetworkserviceprovidersresponse cloud-stack-version='4.0.1.20130201075054'>
<networkserviceprovider>
<name>VpcVirtualRouter</name>
<physicalnetworkid>d476a2f1-bd3d-4abe-9d8e-2ca0eebdf1e2</physicalnetworkid>
<destinationphysicalnetworkid>0</destinationphysicalnetworkid>
<state>Disabled</state>
<id>4b13f9ba-2431-4a9e-e4fd-b8346bedf83b</id>
</networkserviceprovider>
<SNIP>
</listnetworkserviceprovidersresponse>
So that's good - it appears the upgrade did add it to the physical network.
However running the next command fails with a very non-descriptive error:
Executing: createVirtualRouterElement&nspid=
4b13f9ba-2431-4a9e-e4fd-b8346bedf83b&apikey= .... 530 Failed to add Virtual
Router entity to physical network"
catalina.out: WARN [cloud.api.ApiDispatcher] (catalina-exec-8:) class
com.cloud.api.ServerApiException : Failed to add Virtual Router entity to
physical network
Obviously, running the next step to enable throws an error saying
"com.cloud.utils.exception.CloudRuntimeException: Provider is not ready, cannot
Enable the provider, please configure the provider first."
Any idea of why it would fail to add the virtual router to the physical network?
-Evan
On Apr 22, 2013, at 9:41 AM, Alena Prokharchyk wrote:
> The entry for the vpc virtual router provider should have been inserted to
> the DB for all existing physical networks as a part of the DB upgrade
> (Upgrade302to40.java, addVpcProvider call). If the vpc provider is
> missing, it means that the upgrade wasn't performed completely and the DB
> might miss other stuff.
>
> To add/enable the provider with the APIs, execute the following calls:
>
> 1) Add vpc virtual router provider
>
> addNetworkServiceProvider&<list of parameters, check the API docs>
>
>
>
> 2) Add vpc virtual router element
>
> createVirtualRouterElement&nspid=<the id of the VPC VR provider created on
> step #1>
>
>
>
> 3) Enable the element using API
>
> configureVirtualRouterElement&id=<id of vpc vr element>&enabled=true
>
> 4) enable the vpc vr provider
>
> updateNetworkServiceProvider&id=<id of the physical network vr
> provider>&state=Enabled
>
>
> -Alena.
>
>
>
>
> On 4/22/13 6:43 AM, "Prasanna Santhanam" <[email protected]> wrote:
>
>>
>> On Sun, Apr 21, 2013 at 10:55:58PM -0700, Evan McGee wrote:
>>> Hi Swamy,
>>>
>>> Thanks for getting back. cloud.virtual_router_providers is populated
>>> and has one entry:
>>>
>>> id: 1
>>> nsp_id: 1
>>> uuid: a82918427-80bf-8719-baa5-acdf88a9c026
>>> type: VirtualRouter
>>> enabled: 1
>>> removed: NULL
>>>
>>> Looks like this is enabled -- should the type be set to
>>> VirtualRouter? Ran the API call below anyway just to be sure, but
>>> got back the same result when trying to add a new VPC.
>>
>> For VPC the provider is called VpcVirtualRouter.
>>
>> --
>> Prasanna.,
>>
>> ------------------------
>> Powered by BigRock.com
>>
>>
>
>
