[doc] Check for usage of same Cephx ID as manila service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Invalid
|
Low
|
Dustin Schoenbrun |
Bug Description
https:/
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/manila" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit bd21193decf596f
Author: Dustin Schoenbrun <email address hidden>
Date: Mon Aug 1 17:24:21 2016 -0400
Check for usage of same Cephx ID as manila service
There is an issue that happens when access is granted to a manila share
using the same Cephx ID that Manila uses when it is communicating with
the Ceph backend (e.g. the identity specified by the cephfs_auth_id
configuration option). When a request is made to revoke access to the
share with that Cephx ID, the share will become stuck in the
"deleting" state.
This commit adds logic to the _allow_access method in the CephFS Native
driver that checks to see if the Cephx ID given is the same that Manila
is using for its communication with the Ceph backend. If that is the
case, the creation of the access rule will fail with an error.
APIImpact
DocImpact
Change-Id: Ida89b0061db1c8
Closes-Bug: #1608592
summary: |
- Check for usage of same Cephx ID as manila service + [doc] Check for usage of same Cephx ID as manila service |
tags: | added: cephfs driver |
Dustin: Any documentation to be written in the devref/user guide for this change that you committed?