cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toshiaki Hatano (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3959) [KVM] agent setup failed when physical interface name is in pXpY format
Date Tue, 30 Jul 2013 22:19:49 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toshiaki Hatano updated CLOUDSTACK-3959:
----------------------------------------

    Status: Ready To Review  (was: In Progress)
    
> [KVM] agent setup failed when physical interface name is in pXpY format
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3959
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3959
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.2.0
>         Environment: master branch
>            Reporter: Toshiaki Hatano
>            Assignee: Toshiaki Hatano
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> In management.log:
> WARN  [cloud.network.NetworkManagerImpl] (AgentConnectTaskPool-154:ctx-045d85e1) Unable
to setup agent 4 due to Can not find network: cloudbr0
> WARN  [apache.cloudstack.alerts] (AgentConnectTaskPool-154:ctx-045d85e1)  alertType::
7 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message::
>  Incorrect Network setup on agent, Reinitialize agent after network names are setup,
details : Can not find network: cloudbr0
> INFO  [utils.exception.CSExceptionErrorCode] (AgentConnectTaskPool-154:ctx-045d85e1)
Could not find exception: com.cloud.exception.ConnectionException in
>  error code list for exceptions
> WARN  [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-154:ctx-045d85e1) Monitor
NetworkManagerImpl_EnhancerByCloudStack_2ed679b3 says there is an
> error in the connect process for 4 due to Incorrect Network setup on agent, Reinitialize
agent after network names are setup, details : Can not find netw
> ork: cloudbr0
> INFO  [agent.manager.AgentManagerImpl] (AgentConnectTaskPool-154:ctx-045d85e1) Host 4
is disconnecting with event AgentDisconnected
> WARN  [cloud.network.NetworkManagerImpl] (AgentConnectTaskPool-155:ctx-aeecdc27) Unable
to setup agent 4 due to Can not find network: cloudbr0
> In agent.log:
> 2013-07-30 19:26:35,445 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) Request:Seq
4-1791557633:  { Cmd , MgmtId: 161330500648, via: 4, Ver: v1,
>  Flags: 100111, [{"com.cloud.agent.api.CheckNetworkCommand":{"networkInfoList":[{"physicalNetworkId":200,"privateNetworkName":"cloudbr1","publicNetworkNa
> me":"cloudbr0","guestNetworkName":"cloudbr0","storageNetworkName":"cloudbr1"}],"wait":0}}]
}
> 2013-07-30 19:26:35,445 DEBUG [cloud.agent.Agent] (agentRequest-Handler-1:null) Processing
command: com.cloud.agent.api.CheckNetworkCommand
> 2013-07-30 19:26:35,458 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
matchPifFileInDirectory: file name 'p1p4'
> 2013-07-30 19:26:35,458 DEBUG [kvm.resource.LibvirtComputingResource] (agentRequest-Handler-1:null)
failing to get physical interface from bridgecloudbr0, did not find an eth*, bond*, or vlan*
in /sys/devices/virtual/net/cloudbr0/brif

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message