Bug 1447208

Summary: Need a NetBSD machine to debug regression failure
Product: [Community] GlusterFS Reporter: Sanoj Unnikrishnan <sunnikri>
Component: buildAssignee: Nigel Babu <nigelb>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
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-05-05 10:18:01 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
public key id_rsa.pub none

Description Sanoj Unnikrishnan 2017-05-02 06:31:38 UTC 
Created attachment 1275570 [details]
public key id_rsa.pub

I would like to debug the regression failure in https://review.gluster.org/#/c/16938/. Need a setup for the same

PFA, my public key
Comment 1 Nigel Babu 2017-05-02 08:30:05 UTC 
You should be able to SSH in as jenkins.gluster.org. Let me know if you run into any troubles. The NetBSD machines are a little special. The tools are almost like Linux, but not quite. For starters, after you ssh in, you might want to do switch to bash rather than sh. Just type `bash`. I'd also recommend taking a look at the scripts in /opt/qa, especially build.sh and regression.sh. It's different from our usual regression scripts.

Most recently Hari has worked on NetBSD and I suspect Nithya knows the developer environment better than I do.
Comment 2 Sanoj Unnikrishnan 2017-05-05 10:15:22 UTC 
Thanks for the setup. wiki page was helpful