[08:22] <shang__> hi all, can we remove a node from maas (status: allocated to X) without destroying the whole environment?
[09:27] <shang> hi all, I have re-register the node, but the node didn't refresh the information somehow. It is trying to reach the old info: http://ubuntuone.com/5foIzHnGDKOYzAqvHAGECm
[09:28] <shang> the URL it is trying to reach is not there, because I have re-enlist/re-commissioning already
[15:30] <roaksoax> smoser: ping
=== matsubara is now known as matsubara-lunch
[16:13] <roaksoax> Daviey: ping
[16:18] <Daviey> roaksoax: hey
[16:21] <roaksoax> Daviey: howdy! so I was wondering if you ever experienced this:
[16:22] <roaksoax> Daviey: when trying to get the config from the BMC, the network always report IP address of 0.0.0.0
[16:22] <roaksoax> Daviey: even though the IP address is set
[16:22] <roaksoax> Daviey: both with freeipmi tools and with ipmitool
[16:22] <roaksoax> Daviey: this seems to be messing up with ipmi detection
[16:25] <Daviey> roaksoax: nope, not seen that before
[16:25] <Daviey> ugh
[16:25] <Daviey> What hardware?
[16:25] <roaksoax> Daviey: micro servers
[16:25] <roaksoax> Daviey: and seems to be also happening with HP Proliant's
[16:25] <Daviey> hmm, their implementation of IPMI is pants
[16:26] <Daviey> I did mess up networking once, had to use the kernel path to fix it.
[16:26] <Daviey> roaksoax: sorry, No idea!
[16:26] <roaksoax> funny thing is that this used to work and now it doesn't
[16:26] <roaksoax> unless that's something to do with the interfaces in the kernel itself
[16:28] <Daviey> shrug !
[16:28] <Daviey> Sorry roaksoax, not adding much value to this i know
[16:28] <roaksoax> Daviey: no worries, was worth a shot to see if you had experienced that before :)
=== matsubara-lunch is now known as matsubara
[17:41] <smoser> roaksoax, here now.
[17:49] <roaksoax> smoser: no worries :) found what I was looking for, thanks though
=== matsubara is now known as matsubara-afk