Snapshot export locations always shown even when not supported
Bug #1660686 reported by
Rodrigo Barbieri
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Rodrigo Barbieri | ||
Bug Description
Even for shares that are created with a share type that specifies mount_snapshot_
In that case, drivers should not be creating the export resource, nor manila be reading from drivers and exposing them.
| description: | updated |
| Changed in manila: | |
| importance: | Undecided → Medium |
| milestone: | none → ocata-rc1 |
| assignee: | nobody → Rodrigo Barbieri (rodrigo-barbieri2010) |
| Changed in manila: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to manila (master) | #1 |
| Changed in manila: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/manila 4.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4b6f1bf4494fdf8
Author: Rodrigo Barbieri <email address hidden>
Date: Tue Jan 31 15:46:11 2017 -0200
Fix snapshot export locations incorrectly handled
Snapshot export locations should only be created for shares
with property mount_snapshot_
should not be created, even if returned by drivers.
Change-Id: Ie0ce3c4f2e7e29
Closes-bug: #1660686