<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><DIV>Hi£¬Jainme.</DIV>
<DIV> </DIV>
<DIV> I think curruent codes don't have solved the bug complelely. The key problems the the following snippets are executed parallel.<BR>class OpenNebulaHM < OpenNebulaNetwork<BR> XPATH_FILTER = "TEMPLATE/NIC[VLAN='YES']"</DIV>
<DIV> def initialize(vm, deploy_id = nil, hypervisor = nil)<BR> super(vm,XPATH_FILTER,deploy_id,hypervisor)<BR> @bridges = get_interfaces<BR> end</DIV>
<DIV> </DIV>
<DIV>so bridges variable maybe have the same name bridge. because bridge is a ruby instance variable£¬not a ruby class variable.<BR><BR><BR></DIV>
<DIV></DIV>
<DIV id="divNeteaseMailCard"></DIV>
<DIV><BR></DIV>At 2013-12-12 01:53:18,"Jaime Melis" <jmelis@c12g.com> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" id="isReplyContent">
<DIV dir="ltr">Hi,
<DIV><BR></DIV>
<DIV>yes, this is a known bug which is already solved in OpenNebula >= 4.0 by implementing locking mechanisms.</DIV>
<DIV><A href="http://dev.opennebula.org/issues/1722">http://dev.opennebula.org/issues/1722</A><BR></DIV>
<DIV><BR></DIV>
<DIV>cheers,<BR>Jaime</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV></DIV>
<DIV class="gmail_extra"><BR><BR>
<DIV class="gmail_quote">On Wed, Dec 11, 2013 at 9:46 AM, cmcc.dylan <SPAN dir="ltr"><<A href="mailto:dx10years@126.com" target="_blank">dx10years@126.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<DIV style="LINE-HEIGHT: 1.7; FONT-FAMILY: arial; FONT-SIZE: 14px">
<DIV>Hi everyone£¡</DIV>
<DIV> </DIV>
<DIV> I find a problem when we create two or more instances on one host at the same time£¬we meet the error "device onebrxxxx alreay exists can't create bridge with the same name". </DIV>
<DIV> The reason is that instances all try to create their bridge£¬although they check whether or not their birdge is existed. because it's at the same time, they all get a result that their bridge is not existed, and then they create it.</DIV>
<DIV> But when they really create, the same bridge has already been created by other instances.</DIV>
<DIV> </DIV>
<DIV> Has the problem been fixed now£¿ I use opennebula-3.8.1.</DIV>
<DIV> </DIV>
<DIV> Look forward your answers!</DIV><SPAN class="HOEnZb"><FONT color="#888888">
<DIV> </DIV>
<DIV> dylan.</DIV></FONT></SPAN></DIV><BR><BR><SPAN title="neteasefooter"><SPAN></SPAN></SPAN><BR>_______________________________________________<BR>Users mailing list<BR><A href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</A><BR><A href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV><BR clear="all">
<DIV><BR></DIV>-- <BR>
<DIV dir="ltr">Jaime Melis<BR>C12G Labs - Flexible Enterprise Cloud Made Simple<BR><A href="http://www.c12g.com/" target="_blank">http://www.c12g.com</A> | <A href="mailto:jmelis@c12g.com" target="_blank">jmelis@c12g.com</A><BR>
<DIV><BR></DIV>
<DIV>--</DIV>
<DIV><BR></DIV>
<DIV>Confidentiality Warning: The information contained in this e-mail and</DIV>
<DIV>any accompanying documents, unless otherwise expressly indicated, is</DIV>
<DIV>confidential and privileged, and is intended solely for the person</DIV>
<DIV>and/or entity to whom it is addressed (i.e. those identified in the</DIV>
<DIV>"To" and "cc" box). They are the property of C12G Labs S.L..</DIV>
<DIV>Unauthorized distribution, review, use, disclosure, or copying of this</DIV>
<DIV>communication, or any part thereof, is strictly prohibited and may be</DIV>
<DIV>unlawful. If you have received this e-mail in error, please notify us</DIV>
<DIV>immediately by e-mail at <A href="mailto:abuse@c12g.com" target="_blank">abuse@c12g.com</A> and delete the e-mail and</DIV>
<DIV>attachments and any copy from your system. C12G's thanks you for your</DIV>
<DIV>cooperation.</DIV></DIV></BLOCKQUOTE></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>