[Gluster-users] GlusterFS 3.1.1 - peer attach bug

[Jacob Shucart]

Kon,

I will try to reproduce this locally and file a bug.

-Jacob

-----Original Message-----
From: Kon Wilms [mailto:konfoo at gmail.com]
Sent: Thursday, December 09, 2010 2:47 PM
To: Jacob Shucart
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] GlusterFS 3.1.1 - peer attach bug

On Thu, Dec 9, 2010 at 2:08 PM, Jacob Shucart <jacob at gluster.com> wrote:
> Can you tell me a little more about the node?  Does it have several IP
> addresses?  Did you get the same results with all of the IP addresses?
 Or
> just one of them?  When I tried to probe the IP address of the local
node,
> I received a message:
>
> Probe on localhost not needed
>
> This is the expected behavior.

One on the backend with a pair of bonded interfaces, one on the
frontend for gfs access, and another on the frontend (virtual) for
ucarp:

bond0     Link encap:Ethernet  HWaddr a4:ba:db:0c:59:4f
          inet addr:172.16.16.50  Bcast:172.16.16.0  Mask:255.255.255.0
eth0      Link encap:Ethernet  HWaddr a4:ba:db:0c:59:4b
          inet addr:10.2.16.50  Bcast:10.2.31.255  Mask:255.255.240.0
eth2      Link encap:Ethernet  HWaddr a4:ba:db:0c:59:4f
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
eth3      Link encap:Ethernet  HWaddr a4:ba:db:0c:59:4f
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
eth0:ucarp Link encap:Ethernet  HWaddr a4:ba:db:0c:59:4b
          inet addr:10.2.16.57  Bcast:10.2.31.255  Mask:255.255.240.0

I get the probe not needed response as you do, but a peer status
displays the bogus local node with nulled uuid (which cannot be
deleted except for doing it manually).

Cheers
Kon