Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1435093

Summary: Need a NetBSD system to debug a new test case for gfid split-brain resolution
Product: [Community] GlusterFS Reporter: Karthik U S <ksubrahm>
Component: project-infrastructureAssignee: Nigel Babu <nigelb>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-infra, nigelb
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-07 06:50:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
SSH key none

Description Karthik U S 2017-03-23 06:52:12 UTC 
Description of problem:
The new test case for gfid mismatch resolution with favorite-child-policy is failing in the NetBSD slave, but it passes in my system.
You can find the patch at: https://review.gluster.org/#/c/16878/


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Nigel Babu 2017-03-23 09:55:12 UTC 
Can you attach your SSH key, please?
Comment 2 Karthik U S 2017-03-23 10:52:58 UTC 
Created attachment 1265683 [details]
SSH key
Comment 3 Nigel Babu 2017-03-23 11:00:32 UTC 
You should be able to ssh in as jenkins.gluster.org. Please let me know when you're done with the machine.

NetBSD can be a little complicated to debug. So if you run into troubles, please feel free to ping me.
Comment 4 Karthik U S 2017-03-24 05:16:53 UTC 
I am not able to login to this machine. Its giving

ssh: Could not resolve hostname nbslavej.cloud.gluster.org: Name or service not known

Could you take a look?
Comment 5 Nigel Babu 2017-03-24 07:39:11 UTC 
Sorry, typo! It's nbslave7j.cloud.gluster.org
Comment 6 Karthik U S 2017-03-28 05:54:25 UTC 
Nigel, you can take this machine back. The test case passed now, without using this machine. If I need a machine for the same issue in the future, will reopen the bug.
Comment 7 Nigel Babu 2017-04-07 06:50:25 UTC 
Node released into pool.