Don't allow creating images on encrypted volumes when cinder backend is nfs
Bug #1884482 reported by
Rajat Dhasmana
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| glance_store |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
With [1] we are enabling encryption support on nfs backend.
This will affect the consuming APIs (like glance_store) and can cause unexpected behavior while creating/using these volumes.
The best action would be to block creation/usage of encrypted nfs volumes on glance_store side.
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to glance_store (master) | #1 |
| Changed in glance-store: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit becd57467ad54d7
Author: Rajat Dhasmana <email address hidden>
Date: Tue Jun 2 09:15:50 2020 +0000
Don't allow image creation with encrypted nfs volumes
With change[1], we will enabled encrypted volume support for cinder
nfs driver.
Before enabling that, we require handling in cinder consuming projects
(like glance_store) to not have unexpected behavior.
This patch blocks image creation if the destination volume (in which
the image will be written) is an encrypted nfs volume.
[1] https:/
Closes-Bug: #1884482
Change-Id: I3b4c6782e561f2