You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/07/09 19:23:48 UTC
[jira] [Commented] (CLOUDSTACK-3414) Physical Netwok traffic lable
update requires Management Server restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703522#comment-13703522 ]
Alena Prokharchyk commented on CLOUDSTACK-3414:
-----------------------------------------------
Its not specific to vmWare. When the label gets changed, the hosts have to be reconnected - this can happen either by calling reconnectHost, or by the management server restart when all the hosts get reconnected.
This is by design because all the setup and checks on the backend, happen during the host startup process, and it was never meant to be dynamic because it would affect existing vms on the hosts. Closing the bug with "by design" resolution.
> Physical Netwok traffic lable update requires Management Server restart
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3414
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3414
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Sailaja Mada
> Fix For: 4.2.0
>
>
> Setup : VMWARE Adv Zone.
> Note: This issue may not be specific to VMWARE
> Steps:
> 1. Tried to configure Adv Zone with VMWARE
> 2. Configure Physical network 1 with Management Traffic with invalid traffic label ( Ex: vSwitch0,,vmwaresvs)
> 3. Configure Physical network 2 with public & guest Traffic with correct DVSwitch traffic label ( Ex: newdv1,,vmwaredvs)
> 4. Now System VM's are failed to start as it failed to create network for Mgmt traffic.
> 2013-07-09 14:00:50,521 INFO [vmware.resource.VmwareResource] (DirectAgent-7:10.102.192.18) Prepare NIC device based on NicTO: {"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"789e034d-e287-4389-beac-29a10326c0ea","mac":"02:00:41:48:00:05","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false}
> 2013-07-09 14:00:50,525 INFO [vmware.resource.VmwareResource] (DirectAgent-7:10.102.192.18) Prepare network on vmwaresvs P[vSwitch0,,vmwaresvs:untagged] with name prefix: cloud.private
> 2013-07-09 14:00:50,525 WARN [vmware.resource.VmwareResource] (DirectAgent-7:10.102.192.18) Unrecognized broadcast type in VmwareResource, type: LinkLocal. Use vlan info from labeling: untagged
> 2013-07-09 14:00:50,552 ERROR [vmware.mo.HypervisorHostHelper] (DirectAgent-7:10.102.192.18) Unable to find vSwitchvSwitch0,,vmwaresvs
> 2013-07-09 14:00:50,553 WARN [vmware.resource.VmwareResource] (DirectAgent-7:10.102.192.18) StartCommand failed due to Exception: java.lang.Exception
> Message: Unable to find vSwitchvSwitch0,,vmwaresvs
> java.lang.Exception: Unable to find vSwitchvSwitch0,,vmwaresvs
> at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:830)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2923)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2687)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:479)
> at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-07-09 14:00:50,556 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null) Seq 1-763953202: Cancelling because one of the answers is false and it is stop on error.
> 2013-07-09 14:00:50,557 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null) Seq 1-763953202: Response Received:
> 6. Now updated Mgmt traffic label to vSwitch0.
> 7. DB got updated automatically .
> 8. But System Vm's are still failed to start with this
> 9. Restarted Management server (server cloudstack-management stop/ start)
> 10. Now system VM's are up with network name vSwitch0.
> Expected results :
> 1. Changes to Physical network traffic labels should be dynamic,
--
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