Hmm, this does seem like a GUI bug, although I've set up Basic in the past so I'm not sure where the regression might have been. It's been awhile though, so perhaps I just set up a cloudbr0. Even if you intended your guest basic network to double as the public, wouldn't you at least need to provide a reserved IP range for public IPs for the SSVMs and consoleproxies?
Further, the current 3.0.2 advanced install docs are confused about basic networking: "There can be only one physical network in the zone" yet "We strongly recommend the use of separate NICs for management traffic and guest traffic" "That physical network carries three traffic types": Guest, Management, Storage, and Public (four?) "CloudStack will assign IP addresses in the CIDR of the pod to the guests in that pod." - this makes it sound as though the IP range provided in the pod setup (the only range asked for during basic zone setup) will be used for guest traffic. However, that means that your guests are going to use the network you set up for management! Clearly there's something missing in the GUI setup, no? On Thu, Oct 11, 2012 at 7:33 AM, Wido den Hollander (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474142#comment-13474142 > ] > > Wido den Hollander commented on CLOUDSTACK-316: > ----------------------------------------------- > > Checking my api-server.log I see this: > > 2012-10-11 14:54:55,513 INFO [cloud.api.ApiServer] (catalina-exec-5:null) > (userId=2 accountId=2 sessionId=FF59B183869EB5D6931A3B4386E8F8BE) > 0:0:0:0:0:0:0:1 -- GET > command=addTrafficType&trafficType=Guest&physicalnetworkid=ac1e061f-08b5-4e42-8637-51aa6342b5c5&kvmnetworklabel=vlanbr672&response=json&sessionkey=PKgIfLQ%2F5Is1rJEmuyAG6HQ2BjY%3D&_=1349960095344 > 200 { "addtraffictyperesponse" : > {"id":"c0c57ed9-70f7-412a-aebd-69cafe4e80a4","jobid":"81d2128a-c508-4221-97ad-6204164a4899"} > } > 2012-10-11 14:54:55,530 INFO [cloud.api.ApiServer] (catalina-exec-3:null) > (userId=2 accountId=2 sessionId=FF59B183869EB5D6931A3B4386E8F8BE) > 0:0:0:0:0:0:0:1 -- GET > command=addTrafficType&trafficType=Management&physicalnetworkid=ac1e061f-08b5-4e42-8637-51aa6342b5c5&kvmnetworklabel=vlanbr670&response=json&sessionkey=PKgIfLQ%2F5Is1rJEmuyAG6HQ2BjY%3D&_=1349960095348 > 200 { "addtraffictyperesponse" : > {"id":"74630522-3e20-4d6f-b112-23a3e8c695f6","jobid":"56385149-fe98-43f3-9f95-ba26076c72ed"} > } > > Is this a GUI issue? Should the GUI set the "kvmnetworklabel" for the public > network during the wizard or should this be handled by the management server? > > However, in my GUI right now I don't see a way to modify the public network > label. > >> 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 >> >> 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
