Manila-CI: glusterfs (NFS) driver CI fails because backend Glusterfs volume runs out of space
Bug #1498792 reported by
Ramana Raja
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack-plugin-glusterfs |
Fix Committed
|
Undecided
|
Ramana Raja |
Bug Description
glusterfs (NFS) driver CI uses directory mapped layout. Shares are created within GlusterFS volume. During the CI run, the GlusterFS volume runs out of available space, so shares are not created, and tempest tests fail.
Pasting the log of manila scheduler service,
[req-b46ed283-
[req-b46ed283-
[req-b46ed283-
Changed in devstack-plugin-glusterfs: | |
assignee: | nobody → Ramana Raja (rraja) |
Changed in devstack-plugin-glusterfs: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/226639 /git.openstack. org/cgit/ stackforge/ devstack- plugin- glusterfs/ commit/ ?id=830a57308b0 5159b21553b9c33 51b9cbd94de3c5
Committed: https:/
Submitter: Jenkins
Branch: master
commit 830a57308b05159 b21553b9c3351b9 cbd94de3c5
Author: Ramana Raja <email address hidden>
Date: Wed Sep 23 12:52:38 2015 +0530
Manila-CI: increase size of backend GlusterFS vol
The glusterfs (NFS) driver CI that currently uses directly mapped
layout sometimes fails since the backend GlusterFS volume within
which the driver creates shares does not have sufficient space to
allow Tempest to create shares for testing.
Closes-Bug: #1498792 08bb91df55e856e 08bca01e88f
Change-Id: If9ac5088346379