[
https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474389#comment-13474389
]
edison su commented on CLOUDSTACK-316:
--------------------------------------
There is always an issue here for two nics in basic zone, the current security
group code can only support one physical bridge.
Is it ok move the support for multiple bridges in basic zone into 4.1.0?
> KVM Agent setup fails due to cloudbr0 set as public network interface
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-316
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-316
> Project: CloudStack
> Issue Type: Bug
> Components: KVM, Management Server
> Affects Versions: 4.0.0
> Environment: Ubuntu 12.04
> CloudStack 4.0.0-incubator
> Reporter: Wido den Hollander
> Fix For: 4.0.0
>
>
> I just set up a fresh CloudStack 4.0 platform and tried to add a host via the
> wizard.
> My Basic network settings:
> - guest: vlanbr672
> - private: vlanbr670
> During the wizard there is never a prompt for the public network, you can
> only set the storage label, but I didn't do that.
> I kept waiting for the hypervisor to come online, but the agent wouldn't
> start. The log showed:
> 2012-10-11 14:55:46,835 DEBUG [cloud.resource.ServerResourceBase]
> (main:null) Retrieving network interface: cloudbr0
> 2012-10-11 14:55:46,835 DEBUG [cloud.resource.ServerResourceBase]
> (main:null) Unable to get network interface for cloudbr0
> 2012-10-11 14:55:46,835 DEBUG [cloud.resource.ServerResourceBase]
> (main:null) Retrieving network interface: null
> 2012-10-11 14:55:46,835 DEBUG [cloud.resource.ServerResourceBase]
> (main:null) Retrieving network interface: null
> ...
> ....
> .....
> ......
> 2012-10-11 14:55:50,617 DEBUG [utils.script.Script] (main:null)
> Executing: /bin/bash -c brctl show | grep cloudbr0 | awk '{print $4}'
> 2012-10-11 14:55:50,624 DEBUG [utils.script.Script] (main:null) Execution
> is successful.
> 2012-10-11 14:55:50,624 DEBUG [utils.script.Script] (main:null)
> Executing: /bin/bash -c ls /proc/net/vlan/null
> 2012-10-11 14:55:50,630 DEBUG [utils.script.Script] (main:null) Exit
> value is 2
> 2012-10-11 14:55:50,630 DEBUG [utils.script.Script] (main:null) ls:
> cannot access /proc/net/vlan/null: No such file or directory
> ...
> ....
> .....
> 2012-10-11 14:55:50,649 DEBUG [kvm.resource.LibvirtComputingResource]
> (main:null) Failed to get public nic name
> 2012-10-11 14:55:50,649 ERROR [cloud.agent.AgentShell] (main:null) Unable
> to start agent: Failed to get public nic name
> This was due to this setting in agent.properties:
> public.network.device=cloudbr0
> My setup doesn't have cloudbr0, so why was this set?
> The management server log shows me:
> 2012-10-11 14:55:14,545 DEBUG [utils.ssh.SSHCmdHelper]
> (catalina-exec-21:null) Executing cmd: cloud-setup-agent -m 31.25.100.163 -z
> 1 -p 1 -c 1 -g 614b7f96-b6e9-38f2-984b-956af817f771 -a --pubNic=cloudbr0
> --prvNic=vlanbr670 --guestNic=vlanbr672
> 2012-10-11 14:55:47,555 DEBUG [utils.ssh.SSHCmdHelper]
> (catalina-exec-21:null) cloud-setup-agent -m 31.25.100.163 -z 1 -p 1 -c 1 -g
> 614b7f96-b6e9-38f2-984b-956af817f771 -a --pubNic=cloudbr0 --prvNic=vlanbr670
> --guestNic=vlanbr672 output:CloudStack Agent setup is done!
> As you can see, the management server came up with "cloudbr0" for the public
> network, while I never configured that.
> Should public network be set to guest network in a Basic KVM zone?
--
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
