Didn't the script /usr/bin/cloudstack-agent-upgrade run while you
updated the cloudstack-agent ?
Bjoern
On 10/21/2013 6:20 AM, Andrija Panic wrote:
HI,
I have done upgrade from 4.0.0 to 4.2, and it all went fine, until I stoped
and tried to start VMs (Vm belongs to an account, which has it's on VLAN
dedicated for private network)... and got errors about not being able to
joint eth1.500 to breth1-500 because it is already joined to cloudVirBr500
(original bridge that I manualy created during original CS 4.0.0
installation, inside /etc/sysconfig/network-scripts/).
So if I use brctl and remove interface from old bridhe and join it to new
bridgem, then all VMs DO have internet acces, and all fine.
But if I change/reconfigure OS, that is, renam cloudVirBr500 to breth1-500
(on host OS, /etc/sysconfig/network-scripts/) than CloudStack agent give
me alert that it could not find public interface and does not start. Then I
edit the CS agent conf file, and define new bridge "breth1-xxx" for public
network, and agent starts fine, but with alert state, and constantly
disconnecting from CS MGMT host...
Does anybody have good explanation on how to behave with this cloud bridge
naming convention now in 4.2 ?
BTW: using advanced networking, eth0-->cloudBr0, eth1-->cloudVirBr500, this
is configured via /etc/sysconfig/network-scripts/.
eth0 (management, storage, guest,,,) eth1 (guest, public)
Maybe I should NOT define cloudVirBr500 at all ?
Thanks,
