Private volume types are not working for multi tenancy
Bug #1636791 reported by
Denis Egorenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
Medium
|
Unassigned | ||
10.0.x |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
According to blueprint https:/
Meanwhile, i can't do this restriction and volumes with specified type/backend/access can be created in other tenants:
http://
Result: Volume was created in another tenant.
Upstream bug: https:/
description: | updated |
Changed in mos: | |
assignee: | Denis Egorenko (degorenko) → nobody |
Changed in mos: | |
importance: | Undecided → High |
assignee: | nobody → MOS Cinder (mos-cinder) |
milestone: | none → 9.2 |
Changed in mos: | |
assignee: | MOS Cinder (mos-cinder) → Ivan Kolodyazhny (e0ne) |
Changed in mos: | |
importance: | High → Medium |
description: | updated |
Changed in mos: | |
assignee: | Ivan Kolodyazhny (e0ne) → Michael Dovgal (mdovgal) |
Changed in mos: | |
assignee: | Michael Dovgal (mdovgal) → nobody |
To post a comment you must log in.
Denis, please provide steps to reproduce, a diagnostic snapshot and MOS versions which are affected.