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

[Rob Hoes <Rob.Hoes@xxxxxxxxxx>]

That's right, the IP configuration of the management interface if set when you 
run the installer, and this information is written to /etc/firstboot.d/data/... 
and never updated. After a pool eject, this information is re-used to configure 
the management interface. Could you check if /etc/firstboot.d/data/interface-* 
and network.conf contain the right settings?

I have some patches to address this (update the firstboot data before the 
eject), which I will send to the list soon. Meanwhile, you could manually 
update the firstboot data if needed.

Cheers,
Rob

> -----Original Message-----
> From: Dave Scott
> Sent: 07 July 2010 11:14
> To: 'Anthony Xu'; xen-api@xxxxxxxxxxxxxxxxxxx
> Cc: Rob Hoes
> Subject: RE: [Xen-API] after pool-eject, ip address of ejected host is
> corrupted
> 
> 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