If this failure happens, the discovery has done, but the discovered node will not continue to do the rest of the tasks in the chain table.
Thanks Best Regards ---------------------------------------------------------------------- Wang Xiaopeng (王晓朋) IBM China System Technology Laboratory Tel: 86-10-82453455 Email: [email protected] Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193 From: Jarrod Johnson <[email protected]> To: xCAT Users Mailing list <[email protected]> Date: 2015/08/21 10:26 Subject: Re: [xcat-user] "Failed to notify" during xCAT discovery of any node Fwiw, this is not uncommon. I see this commonly and haven't invested debug effort since it is harmless. I suspect there is a race condition. On Aug 20, 2015 10:11 PM, Chris Samuel <[email protected]> wrote: On Fri, 21 Aug 2015 01:43:02 AM Xiao Peng Wang wrote: > The thing is xCAT cannot make socket connection to that node, could check > whether the ip of the node has been changed? Yeah, the node correctly releases its dynamic DHCP range address and then grabs its proper IP address - this is from its first discovery attempt. Aug 14 14:18:26 snowy-m xcat[18089]: xcatd: Processing discovery request from 10.14.3.99 Aug 14 14:18:29 snowy-m xcat[18089]: snowy-test has been discovered Aug 14 14:18:29 snowy-m xcat[18089]: Failed to notify 10.14.3.99 that it's actually snowy-test. Aug 14 14:18:31 snowy-m dhcpd: DHCPRELEASE of 10.14.3.99 from 40:f2:e9:ba:4a:c8 via bond0 (found) Aug 14 14:18:35 snowy-m dhcpd: DHCPDISCOVER from 40:f2:e9:ba:4a:c8 via bond0 Aug 14 14:18:35 snowy-m dhcpd: DHCPOFFER on 10.14.0.35 to 40:f2:e9:ba:4a:c8 via bond0 Aug 14 14:18:35 snowy-m dhcpd: DHCPREQUEST for 10.14.0.35 (10.14.0.33) from 40:f2:e9:ba:4a:c8 via bond0 Aug 14 14:18:35 snowy-m dhcpd: DHCPACK on 10.14.0.35 to 40:f2:e9:ba:4a:c8 via bond0 Aug 14 14:18:40 snowy-m xcat: credentials: sending x509cert Aug 14 14:18:40 snowy-m xcat[30388]: xCAT: Allowing getcredentials x509cert from snowy-test Aug 14 14:18:41 snowy-m xcat[30461]: xCAT: Allowing nextdestiny for snowy-test from snowy-test Aug 14 14:18:46 snowy-m xcat[30527]: xCAT: Allowing getbmcconfig for snowy-test from snowy-test [...] At that point I could use rpower to power it off, so it all seems to be working correctly! All the best, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: [email protected] Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci ------------------------------------------------------------------------------ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user ------------------------------------------------------------------------------ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
