You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Wido den Hollander (JIRA)" <ji...@apache.org> on 2012/10/11 15:25:03 UTC
[jira] [Created] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Wido den Hollander created CLOUDSTACK-316:
---------------------------------------------
Summary: 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
Re: [jira] [Commented] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by Marcus Sorensen <sh...@gmail.com>.
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)
<ji...@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
[jira] [Updated] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "Sudha Ponnaganti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudha Ponnaganti updated CLOUDSTACK-316:
----------------------------------------
Fix Version/s: 4.0.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
[jira] [Assigned] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "edison su (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
edison su reassigned CLOUDSTACK-316:
------------------------------------
Assignee: edison su
> 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
> Assignee: edison su
> 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
[jira] [Updated] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "Sudha Ponnaganti (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudha Ponnaganti updated CLOUDSTACK-316:
----------------------------------------
Assignee: Wido den Hollander (was: edison su)
> 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
> Assignee: 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
[jira] [Commented] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "Marcus Sorensen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474221#comment-13474221 ]
Marcus Sorensen commented on CLOUDSTACK-316:
--------------------------------------------
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)
> 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
[jira] [Commented] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "Wido den Hollander (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "Chandan Purushothama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chandan Purushothama closed CLOUDSTACK-316.
-------------------------------------------
Successfully added a Ubuntu 12.04 KVM Host to the CloudStack Setup. The Host has the following bridge structure.
root@Rack3Host17:~# brctl show
bridge name bridge id STP enabled interfaces
asfbr0 8000.bc305bd41c36 no eth0
asfbr1 8000.bc305bd41c37 no eth1
cloud0 8000.000000000000 no
virbr0 8000.000000000000 yes
root@Rack3Host17:~#
root@Rack3Host17:~# ifconfig
asfbr0 Link encap:Ethernet HWaddr bc:30:5b:d4:1c:36
inet addr:10.223.59.2 Bcast:10.223.59.63 Mask:255.255.255.192
inet6 addr: fe80::be30:5bff:fed4:1c36/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:935551 errors:0 dropped:0 overruns:0 frame:0
TX packets:58913 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:199281936 (199.2 MB) TX bytes:4484904 (4.4 MB)
asfbr1 Link encap:Ethernet HWaddr bc:30:5b:d4:1c:37
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
cloud0 Link encap:Ethernet HWaddr fa:f5:3f:b1:11:38
inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::f8f5:3fff:feb1:1138/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:812 (812.0 B)
eth0 Link encap:Ethernet HWaddr bc:30:5b:d4:1c:36
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3724402 errors:0 dropped:5207 overruns:0 frame:0
TX packets:58920 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2410731394 (2.4 GB) TX bytes:4740058 (4.7 MB)
Interrupt:16 Memory:da000000-da012800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2776 errors:0 dropped:0 overruns:0 frame:0
TX packets:2776 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:269616 (269.6 KB) TX bytes:269616 (269.6 KB)
virbr0 Link encap:Ethernet HWaddr 02:a3:5b:b0:58:b0
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
root@Rack3Host17:~#
root@Rack3Host17:~# ip route
default via 10.223.59.1 dev asfbr0 metric 100
10.223.59.0/26 dev asfbr0 proto kernel scope link src 10.223.59.2
169.254.0.0/16 dev cloud0 proto kernel scope link src 169.254.0.1
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
root@Rack3Host17:~#
============================
Verified on Build with the following Info:
============================
This is the version information for the manifests in the JAR files.
Implementation_Version: 2.2.20121012230921
> 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
> Assignee: 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
[jira] [Resolved] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "edison su (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
edison su resolved CLOUDSTACK-316.
----------------------------------
Resolution: Fixed
fixed in 8a6dbbfaf42687b47e22902923e29aa1f357b488 on 4.0&master branch.
> 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
> Assignee: 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
[jira] [Commented] (CLOUDSTACK-316) KVM Agent setup fails due to
cloudbr0 set as public network interface
Posted by "edison su (JIRA)" <ji...@apache.org>.
[ 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