Gluster snapshots in Container native storage

Solution In Progress - Updated -

Issue

By default, GlusterFS does mount even deactivated snapshot(s) under /run/gluster/snaps. Since we do have a mount, there is a possibility that some process may access the mount, causing issues when trying to umount the volume for instance when deleting the snapshot.

Since in Container Native Storage everything is automated, the snapshot deletion failure will cause problems such as reaching the maximum limit of snapshots or stale snapshots being present because of the above issue.

Environment

  • OCP-3.4
  • OCP-3.5
  • CNS-3.4
  • CNS-3.5
  • RHGS-3.1
  • RHGS-3.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content