On Mon, Sep 09, 2013 at 08:53:45PM +0000, Kelven Yang wrote: > > > On 9/9/13 12:07 PM, "Darren Shepherd" <darren.s.sheph...@gmail.com> wrote: > > >I just ran into this. For whatever reason my box listed eth2 before > >eth0 for "ifconfig -a" so it looked like management server mac changed. > > Then nothing worked... > > It is supposed to work if you are sure a previous running MS java process > is killed and the IP associated is still valid for the setup. A mac change > will cause CloudStack to think there is another MS node is UP, however, it > will try to detect if there is any other node which is currently using the > MS IP, it may do self-fencing to shut itself down if a previous running MS > java process is still running there. > > The only requirement for it to work is that, mac address can be changed, > but the associated IP should be valid to the setup > only last week this was found to be a problem with 4.2.0 by someone who tried this internally. cf: https://issues.apache.org/jira/browse/CLOUDSTACK-4621
> Kelven > > > >I finally just hacked up the code to get it to > >work again. > > > >So whats the real procedure if you do a chassis swap and your management > >server MAC addr changes? How does cloudstack deal with that? > > > >Darren -- Prasanna., ------------------------ Powered by BigRock.com
