Hi Vladislav,
As per the bug you mentioned, its fixed in 4.2.
Which version of cloudstack are you using? If its not working in 4.2+, can
you reopen the bug?

~Rajani

On Wed, May 20, 2015 at 10:39 PM, Vladislav Nazarenko <
vladislav.nazare...@gmail.com> wrote:

> Found the problem by googling .... renamed network interfaces rom pXpY to
> ethZ
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-3959
>
>
>
> On 20.05.2015 18:30, Vladislav Nazarenko wrote:
>
>> Hi Vadim,
>>
>> thanx for your response ...
>>
>> my setup:
>>
>> 1. KVM
>>
>> 2. Network
>>
>> eth0
>>   cloudbr0 (mgmt) (X.X.X.176/28)
>>     public (X.X.X.0/24)
>>
>> eth1
>>   cloudbr1
>>     guest 10.0.30.0/21 VLAN 20-39
>>     storage  10.0.40.0/24 VLAN 40
>>
>> 3. Cloudstack 4.4.3 on centos 7
>>    Advanced zone
>>
>> 4. Agent Conf
>> #Storage
>> #Wed May 20 18:27:31 CEST 2015
>> guest.network.device=cloudbr1
>> workers=5
>> private.network.device=cloudbr0
>> port=8250
>> resource=com.cloud.hypervisor.kvm.resource.LibvirtComputingResource
>> pod=1
>> zone=1
>> hypervisor.type=kvm
>> guid=f6ce77af-ebe3-31b7-b8b6-fcc58dad925e
>> public.network.device=cloudbr0
>> cluster=1
>> local.storage.uuid=c37e767f-911b-4503-816a-7b965a962661
>> domr.scripts.dir=scripts/network/domr/kvm
>> LibvirtComputingResource.id=0
>> host=X.X.X.178
>>
>>
>> Logs on the compute node:
>> 2015-05-20 18:28:44,327{GMT} INFO  [utils.nio.NioClient]
>> (Agent-Selector:) SSL: Handshake done
>> 2015-05-20 18:28:44,328{GMT} INFO  [utils.nio.NioClient]
>> (Agent-Selector:) Connected to X.X.X.178:8250
>> 2015-05-20 18:28:44,452{GMT} INFO  [cloud.agent.Agent] (Agent-Handler-2:)
>> Proccess agent startup answer, agent id = 0
>> 2015-05-20 18:28:44,452{GMT} INFO  [cloud.agent.Agent] (Agent-Handler-2:)
>> Set agent id 0
>> 2015-05-20 18:28:44,453{GMT} INFO  [cloud.agent.Agent] (Agent-Handler-2:)
>> Startup Response Received: agent id = 0
>> 2015-05-20 18:28:44,638{GMT} INFO  [agent.transport.Request]
>> (UgentTask-5:) not building log message for '[{}]', _cmds.length == 1
>> 2015-05-20 18:28:44,639{GMT} WARN  [cloud.agent.Agent] (UgentTask-5:)
>> Unable to send request: null
>> 2015-05-20 18:28:44,726{GMT} INFO  [agent.transport.Request]
>> (Agent-Handler-4:) not building log message for '[{}]', _cmds.length == 1
>> 2015-05-20 18:28:44,726{GMT} WARN  [cloud.agent.Agent] (Agent-Handler-4:)
>> Unable to send response: null
>> 2015-05-20 18:28:49,329{GMT} INFO  [cloud.agent.Agent] (Agent-Handler-1:)
>> Connected to the server
>> 2015-05-20 18:28:49,600{GMT} INFO  [cloud.agent.Agent] (Agent-Handler-1:)
>> Lost connection to the server. Dealing with the remaining commands...
>>
>>
>>
>> Alerts in the dashboard
>>
>> Incorrect Network setup on agentReinitialize agent after network names
>> are setupdetails : Can not find network: cloudbr0
>>
>> 20 May 2015 18:11:52
>>
>>
>>
>> On 19.05.2015 21:39, Vadim Kimlaychuk wrote:
>>
>>> Vlad,
>>>
>>>            You should provide a little bit more than that.  At least the
>>> following:
>>> 1. Hypervisor type and version.
>>> 2. Network setup (physical and logical). In brief. I guess you use KVM,
>>> so do you have openvswitch or do you use linux bridge?
>>> 3. Cloudstack version and type of zone you are trying to configure
>>> (basic, advanced) ?
>>> 4. Agent conf file would be also great
>>>
>>> Vadim
>>> ________________________________________
>>> From: Vladislav Nazarenko <vladislav.nazare...@gmail.com>
>>> Sent: Tuesday, May 19, 2015 19:09
>>> To: users@cloudstack.apache.org
>>> Subject: Incorrect Network setup on agent
>>>
>>> Hi Everybody,
>>>
>>> getting the following error trying to install a cloudstack agent. Can
>>> anybody help?
>>>
>>> Incorrect Network setup on agent, Reinitialize agent after network names
>>> are setup, details : Can not find network: mgmtbr
>>>
>>> Please advice
>>> Vlad
>>>
>>>
>>>
>>
>

Reply via email to