You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Evan McGee <ev...@ringplus.net> on 2013/04/19 03:04:02 UTC
Unable to find provider VpcVirtualRouter in physical network
Hello,
We recently upgraded our from 3.0.2 to 4.0.1 (all servers/agents running under CentOS 6.3) and everything went swimmingly. But now we're hitting an issue: we're attempting to create a VPC but keep getting this error when attempting to add it: "Provider VpcVirtualRouter should be enabled in at least one physical network of the zone specified"
From: /var/log/cloud/management/management-server.log:
2013-04-18 19:00:31,316 WARN [cloud.network.NetworkManagerImpl] (catalina-exec-19:null) Unable to find provider VpcVirtualRouter in physical network id=1
We're running a single Advanced Zone with a single physical network.
The default 4.0.1 VPC network offerings exist and are enabled. One interesting thing to note: when I head to Zones--->...--->Network Service Providers --> VPC Virtual Router, it marked as "Disabled" but when I click on the link it brings up the [Network | Instances] screen it never resolves past the pulsating "loading" graphic.
From: /var/log/cloud/management/api-server.log:
GET command=listNetworkServiceProviders&physicalnetworkid=XXXXX&name=VpcVirtualRouter&response=json&sessionkey=XXXX1366332171874 200 { "listnetworkserviceprovidersresponse" : { } }
Does anyone have an idea of how to get the provider enabled in our existing zone?
Cheers,
Evan
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Prasanna Santhanam <ts...@apache.org>.
On Wed, Apr 24, 2013 at 11:40:16PM -0700, Evan McGee wrote:
> 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
You should do a configureVirtualRouterElement&nspid=<yourid>&enabled=true since the provider is already present.
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Evan McGee <ev...@ringplus.net>.
Hmm.. getting closer. I managed to get the virtual router element added & enabled via createVirtualRouterElement and configureVirtualRouterElement. I upgraded to 4.0.2 and perhaps that helped.
However, when trying to change state=Enabled with updateNetworkServiceProvider I'm still getting the "Provider is not ready" error: https://gist.github.com/emcgee/a2e70733e898625dfa38
FWIW, here's a gist of the output from listVirtualRouterElements, listNetworkServiceProviders, and listPhysicalNetworks: https://gist.github.com/emcgee/0c579f5bb250fc7261e0
- Evan
On Apr 25, 2013, at 9:23 AM, Alena Prokharchyk wrote:
> Evan, can you check the log file to see what exception happened when you
> tried to add vpc virtual router element? 530 usually means NPE
>
> -Alena.
>
> On 4/24/13 11:40 PM, "Evan McGee" <ev...@ringplus.net> wrote:
>
>> 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" <ts...@apache.org> 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
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Alena Prokharchyk <Al...@citrix.com>.
Evan, can you check the log file to see what exception happened when you
tried to add vpc virtual router element? 530 usually means NPE
-Alena.
On 4/24/13 11:40 PM, "Evan McGee" <ev...@ringplus.net> wrote:
>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" <ts...@apache.org> 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
>>>
>>>
>>
>>
>
>
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Evan McGee <ev...@ringplus.net>.
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" <ts...@apache.org> 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
>>
>>
>
>
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Alena Prokharchyk <Al...@citrix.com>.
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" <ts...@apache.org> 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
>
>
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Prasanna Santhanam <ts...@apache.org>.
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
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Evan McGee <ev...@ringplus.net>.
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.
On Apr 21, 2013, at 9:20 PM, Venkata SwamyBabu Budumuru wrote:
> Hi Evan,
>
> What do you see in cloud. virtual_router_providers? Does it contain entry for vpcVR? If yes, what is the enabled flag value?
>
> If enabled is set to "0" then try the following api to configure VPCVR
>
> http://SERVER IP:8096/client/api?command=configureVirtualRouterElement&enabled=true&id=
>
> Thanks,
> SWAMY
>
> -----Original Message-----
> From: Evan McGee [mailto:evan@ringplus.net]
> Sent: Monday, 22 April 2013 12:30 AM
> To: users@cloudstack.apache.org
> Subject: Re: Unable to find provider VpcVirtualRouter in physical network
>
> Hey everyone,
>
> Any ideas of what's happening here? Even gentle nudges would be hugely appreciated.
>
> On Apr 18, 2013, at 6:04 PM, Evan McGee wrote:
>
>> Hello,
>>
>> We recently upgraded our from 3.0.2 to 4.0.1 (all servers/agents running under CentOS 6.3) and everything went swimmingly. But now we're hitting an issue: we're attempting to create a VPC but keep getting this error when attempting to add it: "Provider VpcVirtualRouter should be enabled in at least one physical network of the zone specified"
>>
>> From: /var/log/cloud/management/management-server.log:
>> 2013-04-18 19:00:31,316 WARN [cloud.network.NetworkManagerImpl] (catalina-exec-19:null) Unable to find provider VpcVirtualRouter in physical network id=1
>>
>> We're running a single Advanced Zone with a single physical network.
>>
>> The default 4.0.1 VPC network offerings exist and are enabled. One interesting thing to note: when I head to Zones--->...--->Network Service Providers --> VPC Virtual Router, it marked as "Disabled" but when I click on the link it brings up the [Network | Instances] screen it never resolves past the pulsating "loading" graphic.
>>
>> From: /var/log/cloud/management/api-server.log:
>> GET command=listNetworkServiceProviders&physicalnetworkid=XXXXX&name=VpcVirtualRouter&response=json&sessionkey=XXXX1366332171874 200 { "listnetworkserviceprovidersresponse" : { } }
>>
>> Does anyone have an idea of how to get the provider enabled in our existing zone?
>>
>> Cheers,
>> Evan
>>
>>
>
RE: Unable to find provider VpcVirtualRouter in physical network
Posted by Venkata SwamyBabu Budumuru <ve...@citrix.com>.
Hi Evan,
What do you see in cloud. virtual_router_providers? Does it contain entry for vpcVR? If yes, what is the enabled flag value?
If enabled is set to "0" then try the following api to configure VPCVR
http://SERVER IP:8096/client/api?command=configureVirtualRouterElement&enabled=true&id=
Thanks,
SWAMY
-----Original Message-----
From: Evan McGee [mailto:evan@ringplus.net]
Sent: Monday, 22 April 2013 12:30 AM
To: users@cloudstack.apache.org
Subject: Re: Unable to find provider VpcVirtualRouter in physical network
Hey everyone,
Any ideas of what's happening here? Even gentle nudges would be hugely appreciated.
On Apr 18, 2013, at 6:04 PM, Evan McGee wrote:
> Hello,
>
> We recently upgraded our from 3.0.2 to 4.0.1 (all servers/agents running under CentOS 6.3) and everything went swimmingly. But now we're hitting an issue: we're attempting to create a VPC but keep getting this error when attempting to add it: "Provider VpcVirtualRouter should be enabled in at least one physical network of the zone specified"
>
> From: /var/log/cloud/management/management-server.log:
> 2013-04-18 19:00:31,316 WARN [cloud.network.NetworkManagerImpl] (catalina-exec-19:null) Unable to find provider VpcVirtualRouter in physical network id=1
>
> We're running a single Advanced Zone with a single physical network.
>
> The default 4.0.1 VPC network offerings exist and are enabled. One interesting thing to note: when I head to Zones--->...--->Network Service Providers --> VPC Virtual Router, it marked as "Disabled" but when I click on the link it brings up the [Network | Instances] screen it never resolves past the pulsating "loading" graphic.
>
> From: /var/log/cloud/management/api-server.log:
> GET command=listNetworkServiceProviders&physicalnetworkid=XXXXX&name=VpcVirtualRouter&response=json&sessionkey=XXXX1366332171874 200 { "listnetworkserviceprovidersresponse" : { } }
>
> Does anyone have an idea of how to get the provider enabled in our existing zone?
>
> Cheers,
> Evan
>
>
Re: Unable to find provider VpcVirtualRouter in physical network
Posted by Evan McGee <ev...@ringplus.net>.
Hey everyone,
Any ideas of what's happening here? Even gentle nudges would be hugely appreciated.
On Apr 18, 2013, at 6:04 PM, Evan McGee wrote:
> Hello,
>
> We recently upgraded our from 3.0.2 to 4.0.1 (all servers/agents running under CentOS 6.3) and everything went swimmingly. But now we're hitting an issue: we're attempting to create a VPC but keep getting this error when attempting to add it: "Provider VpcVirtualRouter should be enabled in at least one physical network of the zone specified"
>
> From: /var/log/cloud/management/management-server.log:
> 2013-04-18 19:00:31,316 WARN [cloud.network.NetworkManagerImpl] (catalina-exec-19:null) Unable to find provider VpcVirtualRouter in physical network id=1
>
> We're running a single Advanced Zone with a single physical network.
>
> The default 4.0.1 VPC network offerings exist and are enabled. One interesting thing to note: when I head to Zones--->...--->Network Service Providers --> VPC Virtual Router, it marked as "Disabled" but when I click on the link it brings up the [Network | Instances] screen it never resolves past the pulsating "loading" graphic.
>
> From: /var/log/cloud/management/api-server.log:
> GET command=listNetworkServiceProviders&physicalnetworkid=XXXXX&name=VpcVirtualRouter&response=json&sessionkey=XXXX1366332171874 200 { "listnetworkserviceprovidersresponse" : { } }
>
> Does anyone have an idea of how to get the provider enabled in our existing zone?
>
> Cheers,
> Evan
>
>