Xena accept transfer policy breaks volume transfer workflow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Rajat Dhasmana | ||
Xena |
Fix Released
|
High
|
Rajat Dhasmana |
Bug Description
We did a bunch of work during the Xena release to update the policies across cinder to support three consistent personas called project-admin, project-member, and project-reader.
These personas are inline with changes we're making across the rest of the OpenStack community for improving authorization user experience.
During the Xena cycle we updated the tranfer volume policy from being open to checking the user's project [0].
Unfortunately, this breaks the following work flow:
1. user in project foo puts a volume into transfer state
2. user in project foo gives volume ID to user in project bar to accept
3. user in project bar accepts the volume
Step 3 will fail because the user making the request has a token scoped to a project that isn't the volume's original project (foo).
Again, this didn't fail in the past since the policy defaulted to open (""). We should consider a policy change so that we don't break this flow since volume transfer is designed to share volumes between projects.
Changed in cinder: | |
importance: | Undecided → High |
tags: | added: policy rbac |
Changed in cinder: | |
assignee: | nobody → Brian Rosmaita (brian-rosmaita) |
status: | New → In Progress |
Changed in cinder: | |
assignee: | Brian Rosmaita (brian-rosmaita) → nobody |
assignee: | nobody → Rajat Dhasmana (whoami-rajat) |
milestone: | none → yoga-3 |
Fix proposed to branch: master /review. opendev. org/c/openstack /cinder/ +/824131
Review: https:/