Bug 1558320

Summary:	Freebsd smoke fails due to disk full
Product:	[Community] GlusterFS	Reporter:	Raghavendra G <rgowdapp>
Component:	project-infrastructure	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, mscherer, nigelb, rgowdapp
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-08-03 10:26: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:

Description Raghavendra G 2018-03-20 03:07:13 UTC

Description of problem:

https://build.gluster.org/job/freebsd-smoke/27214/console
https://build.gluster.org/job/freebsd-smoke/27214/

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 M. Scherer 2018-03-21 13:35:49 UTC

So the error is:

12:49:07 Running autogen.sh in argp-standalone ...
12:49:23 autom4te-2.69: cannot open > /tmp/am4tFcUqUR/warnings: No space left on device
12:49:23 automake-1.15: error: autoconf failed with exit status: 1

Comment 2 M. Scherer 2018-03-21 13:39:30 UTC

And the disk is no longer full, it seems someone did the cleanup already.

Does it work now ?

Comment 3 Raghavendra G 2018-03-21 13:48:22 UTC

(In reply to M. Scherer from comment #2)
> And the disk is no longer full, it seems someone did the cleanup already.
> 
> Does it work now ?

I don't know. It was a job which failed. I've not tried specifically on this VM/machine.

From console output of failed run:
12:49:23 autom4te-2.69: cannot open > /tmp/am4tFcUqUR/warnings: No space left on device
12:49:23 automake-1.15: error: autoconf failed with exit status: 1

Comment 4 M. Scherer 2018-03-21 13:50:36 UTC

We have only 2 FreeBSD builders, so I suspect that the chance are high to use that builder.

Comment 5 Nigel Babu 2018-08-03 10:26:25 UTC

Given freebsd is running now, going to close this bug.