Bug 1383025 – Failed to provision GlusterFS volumes, error 'no volume plugin matched'

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1383025 - Failed to provision GlusterFS volumes, error 'no volume plugin matched'

Summary:	Failed to provision GlusterFS volumes, error 'no volume plugin matched'

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage (Show other bugs)
Sub Component:
Version:	3.4.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity urgent
Target Milestone:	---
Target Release:	---
Assigned To:	hchen
QA Contact:	Jianwei Hou
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1386117
	Show dependency tree / graph

Reported:	2016-10-09 03:57 EDT by Jianwei Hou
Modified:	2017-03-08 13 EST (History)
CC List:	12 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Clones:	1386117 (view as bug list)
Environment:
Last Closed:	2017-01-18 07:42:09 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0066	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.4 RPM Release Advisory	2017-01-18 12:23:26 EST

Groups: None (edit)

Description Jianwei Hou 2016-10-09 03:57:14 EDT

Description of problem:
Failed to dynamically provision GlusterFS/CephRBD volume and PV, got error 'no volume plugin matched'.

Version-Release number of selected component (if applicable):
openshift v3.4.0.8
kubernetes v1.4.0+776c994
etcd 3.1.0-alpha.1

How reproducible:
Always

Steps to Reproduce:
1. Prepare Heketi and create endpoints, service, storageclass, secret following  https://github.com/kubernetes/kubernetes/blob/master/examples/experimental/persistent-volume-provisioning/README.md
2. Create PVC
3. oc describe pvc

Actual results:
Both PV and GlusterFS volume were not created dynamically. 

Events:
  FirstSeen        LastSeen        Count        From                                SubobjectPath        Type                Reason                        Message
  ---------        --------        -----        ----                                -------------        --------        ------                        -------
  21s                11s                2        {persistentvolume-controller }                        Warning                ProvisioningFailed        no volume plugin matched


Expected results:
1. PV and volume should be provisioned successfully.

Additional info:
Volume was successfully provisioned while testing on upstream.

Comment 6 Andy Goldstein 2016-10-18 17:46:15 EDT

See https://trello.com/c/UsShKRgM/238-8-create-a-glusterfs-dynamic-provisioner-gluster#comment-58069809bf82a36fa727a665

Comment 7 Humble Chirammal 2016-10-20 09:32:15 EDT

https://github.com/openshift/origin/pull/11446

Comment 8 Humble Chirammal 2016-10-21 07:38:15 EDT

(In reply to Humble Chirammal from comment #7)
> https://github.com/openshift/origin/pull/11446

Above PR is closed and made the changes in https://github.com/openshift/origin/pull/11460/ which got merged just now in Origin. @jhou you should be able to use GlusterFS provisioner from now on. This has endpoint and secret support.

Comment 9 Jianwei Hou 2016-10-25 01:23:16 EDT

Verified this has been fixed in:
oc v3.4.0.15+9c963ec
kubernetes v1.4.0+776c994

Once this is ON_QA, I'll update it as Verified.

Comment 10 Troy Dawson 2016-10-28 16:05:27 EDT

This has been merged into ose and is in OSE v3.4.0.17 or newer.

Comment 12 Liang Xia 2016-10-31 04:15:06 EDT

Based on #comment 9, move to verified.

Comment 14 errata-xmlrpc 2017-01-18 07:42:09 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0066

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