<p dir="ltr"><br>
On 26 May 2015 18:35, "Avra Sengupta" <<a href="mailto:asengupt@redhat.com">asengupt@redhat.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> What you are refering with the glusterd being restarted might be true, but I don't remember if the two different peer addresses were before and after restarting glusterd, or after restarting glusterd and before/after peer status. We might need to re-do this exercise on a rackspace vm to get more clarity.<br>
I will encourage to do it before this patch gets into the codebase.<br>
><br>
> Regards,<br>
> Avra<br>
><br>
><br>
> On 05/26/2015 06:26 PM, Kaushal M wrote:<br>
>><br>
>> These are my findings regarding the issue KP mentioned with<br>
>> volume-snapshot-clone.t.<br>
>><br>
>> From what I gathered, the double peerinfo objects issue was observed<br>
>> only via logs. Additional logging was added to<br>
>> glusterd_peer_rpc_notify to log the objects address and<br>
>> peerinfo->hostname . I did the same and observed the same in my logs.<br>
>> But what I found was that glusterd was being restarted in between the<br>
>> logs with different address. So the peerinfo objects were bound to<br>
>> have different addresses.<br>
>><br>
>> Avra, can you confirm if the above is correct? In the case it is, then<br>
>> I can help debug the issue being faced.<br>
>><br>
>> I've been running the test on a local vm but, I've not gotten it to<br>
>> fail, even without Avra's partial fix. I spoke to Atin regarding this,<br>
>> and he informed me that the failures are only hit on the rackspace<br>
>> slave VMs. I'll try get access to a slave VM and check the issue out.<br>
>><br>
>> ~kaushal<br>
>><br>
>> On Tue, May 26, 2015 at 3:37 PM, Krishnan Parthasarathi<br>
>> <<a href="mailto:kparthas@redhat.com">kparthas@redhat.com</a>> wrote:<br>
>>><br>
>>> All,<br>
>>><br>
>>> The following are the regression test failures that are being looked<br>
>>> at by Atin, Avra, Kaushal and self.<br>
>>><br>
>>> 1) ./tests/bugs/glusterd/bug-974007.t to be fixed by <a href="http://review.gluster.org/10872">http://review.gluster.org/10872</a><br>
>>><br>
>>> 2) ./tests/basic/volume-snapshot-clone. to be fixed (partially) by <a href="http://review.gluster.org/10895">http://review.gluster.org/10895</a><br>
>>> There is another issue ('other' part) where there are 2 peerinfo objects for a given peer/node. This<br>
>>> is being investigated by Kaushal.<br>
>>><br>
>>> Will keep this thread updated as and when more progress is made.<br>
>>><br>
>>> cheers,<br>
>>> KP<br>
>>> _______________________________________________<br>
>>> Gluster-devel mailing list<br>
>>> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
>>> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
><br>
><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</p>