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

Bug 1698694

Summary: regression job isn't voting back to gerrit
Product: [Community] GlusterFS Reporter: Atin Mukherjee <amukherj>
Component: project-infrastructureAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6CC: bugs, dkhandel, gluster-infra, mscherer
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: 2019-04-29 05:27:39 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:

Description Atin Mukherjee 2019-04-11 02:43:38 UTC
Description of problem:

Please see https://review.gluster.org/#/c/glusterfs/+/22544/ & https://build.gluster.org/job/centos7-regression/5518/ which should have voted back and that didn't happen.

Comment 1 Deepshikha khandelwal 2019-04-11 04:15:30 UTC
I thought I solved this issue.

But looking more into the problem it seems the issue is not with Gerrit trigger plugin of Jenkins but with the builder. As I see all the patches which had due vote built on the same 203builder. Looking at what recent changes introduced this.

Comment 2 M. Scherer 2019-04-11 13:46:26 UTC
Mhh, I see:

17:51:40 Host key verification failed.

Could be something related to reinstallation of the builder last time.

Comment 3 M. Scherer 2019-04-11 13:51:28 UTC
Ok so I suspect the problem is the following. We reinstalled the builder, so the home was erased. The script do run ssh review, but it was blocked on the key verification step, because no one was here to type "yes", since this was the first attempt. I did it (su - jenkins, ssh review.gluster.org), and I suspect this should be better.

If the symptom no longer appear, then my hypothesis was good. I think the fix would be to change the ssh command to accept the key on first use, i will provide a patch.

Comment 4 M. Scherer 2019-04-11 14:37:59 UTC
https://review.gluster.org/#/c/build-jobs/+/22548 for my proposed fix

Comment 5 Deepshikha khandelwal 2019-04-29 05:27:39 UTC
It is fixed now.