Re: unsupported volume type after update to 1.1.3

> > For now, yes. We're looking at ways to make dynamic provisioning more > widely available, even outside of a cloud environment. We'd prefer to not > implement more recyclers and instead make more provisioners. > Ok thanks, the PV is Bound again: status: accessModes: - ReadWriteOnce -

Re: unsupported volume type after update to 1.1.3

On Tue, Feb 23, 2016 at 9:00 AM, Mark Turansky wrote: > There is no recycler for glusterfs, so "no volume plugin matched" would > occur when the volume is being reclaimed by the cluster after its release > from a claim. > yes, the pvc was probably remove when the

Re: unsupported volume type after update to 1.1.3

Hi Philippe, Has the claim for this volume been deleted? There is no recycler for glusterfs, so "no volume plugin matched" would occur when the volume is being reclaimed by the cluster after its release from a claim. Mark On Tue, Feb 23, 2016 at 8:46 AM, Philippe Lafoucrière <

unsupported volume type after update to 1.1.3

Hi, We have a volume with status = "Failed" after upgrading to 1.1.3. All our volumes are mounted through glusterfs, and all the others are fine, the issue is just with one of them: Name: pv-storage-1 Labels: Status: Failed Claim: