RE: [Xen-API] after pool-eject, ip address of ejected host is corrupted

[Dave Scott <Dave.Scott@xxxxxxxxxxxxx>]

Hi,
 
> Hi all,
> 
> I have two host:
> H1: 192.168.1.111  ( pif ip address is 192.168.1.111)
> H2: 192.168.1.112  (pif ip address is 192.168.1.112)
> 
> they are in a pool, H1 is master, after I pool-eject H2, H2 reboots.
> after reboot, there is not ip address for nic/bridge if I execute
> ifconfig. And I found out pif ip address of H2 is 192.168.1.111(which
> is
> H1's ip address).
> 
> That means I need go to lab to reconfigure H2 ip address every time I
> pool-eject it. It's not convenient.
> 
> Is there any way the host ip address is preserved after it is
> pool-ejected?
> 
> Thanks in advance!

I think what happens is that the "firstboot" init.d script is run on the host 
after eject. This uses configuration written by the host installer in 
/etc/firstboot.d/data/... which might be slightly out-of-date.

I think Rob [cc:d] has some thoughts on how to make this more sensible :-)

Cheers,
Dave

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api