cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrija Panic <andrija.pa...@gmail.com>
Subject Re: Agent deleting/stoping main bridge on Linux ???
Date Wed, 04 Mar 2015 16:09:32 GMT
I forgot to add - this is ACS 4.3.0 and CentOS 6.x... breth1-500 is the
main bridge used for Shared Network (yes, I know, somewhat confusing name
for the bridge...)

On 4 March 2015 at 17:07, Andrija Panic <andrija.panic@gmail.com> wrote:

> Hi people.
>
> on physical host, I was having breth1-500(bridge) with eth1(joined to this
> bridge) - all defined manually in Centos network config files.
> (when you boot physical host - this bridge is active of course)
>
> When I deploy new VM with Shared Network with vlan 500, new device is
> created eth1.500 and joined to this bridge - which is fine, and then vnet0
> device from VM is also joined to the bridge...
>
>
>
> When I stop the last VM that is using this Shared Network, CloudStack
> (agent?) removes eth1.500 from bridge (fine with me), and ***then removed
> eth1 from bridge (which I manually configured !!!) and later stoped/removed
> the whole bridge***
>
> If you try to start new VM again (joined to Shared Network with vlan 500)
> - then no bridge is available, VM is started, but no vnet device, no
> breth1-500 bridge up, and no eth1.500 up.
> No bridge was available - but also bridge was not created on the fly...
>
>
> Is there any explanation - why the heck would my manually configured
> bridge get deleted?
>
> --
>
> Andrija Panić
>



-- 

Andrija Panić

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message