Bug 1653147

Summary:	Build Status: Failed - at scan.coverity.com
Product:	[Community] GlusterFS	Reporter:	Sunny Kumar <sunkumar>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Nigel Babu <nigelb>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	atumball, bugs, gluster-infra, nigelb, sankarshan
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:	2018-12-17 06:42:03 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 Sunny Kumar 2018-11-26 04:39:18 UTC

Description of problem:

Gluster build is failing at scan.coverity.com resulting in failure in reporting new or fixed coverity issue.

Dashboard is also failing to show individual issue with Error code 20.
 
How reproducible:

Always

Actual results:
Build Status: Failed - No further action needed

Expected results:
Should run coverity scan at scheduled time.


Additional info:

Comment 1 Amar Tumballi 2018-11-26 04:46:13 UTC

Looks to be an issue with scan.coverity.com website. I am trying to trigger another build for gluster-block, and it is failing there too. Also not able to check the defects. 

Not an gluster-infra issue is what I believe. Good to keep it open for some more time, till we see coverity.com get fixed, and then see if this is still an issue with gluster-infra.

Comment 2 Sunny Kumar 2018-11-26 05:42:25 UTC

I have a doubt about that because I am member of other community project also and coverity scan is running fine there and able to see dashboard for individual CID. So I think it requires investigation from our side.

/Sunny

Comment 3 Nigel Babu 2018-12-03 06:22:25 UTC

This is a problem at the Coverity end. They have a huge backlog and we were retriggering our runs every day putting us at the back of the queue. I've disabled submitting a new job until we get the first result. Currently 296th in queue.

Comment 4 Nigel Babu 2018-12-17 06:42:03 UTC

Update: The last run that we triggered on 24th Nov now has results. I've kicked off a new run on Friday. That's at position 37 in the queue. There's nothing more to do from the infra point of view, so I'm closing out this bug as Works For Me.