Bug 1558320 - Freebsd smoke fails due to disk full
Summary: Freebsd smoke fails due to disk full
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-20 03:07 UTC by Raghavendra G
Modified: 2018-08-03 10:26 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-03 10:26:25 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.