bd21193dec
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: Ida89b0061db1c8780a19475510b830d013a5c154 Closes-Bug: #1608592
6 lines
178 B
YAML
6 lines
178 B
YAML
---
|
|
fixes:
|
|
- Check the Cephx ID used when granting access to a CephFS share to make
|
|
sure it's not the same as the one Manila uses to communicate with the
|
|
Ceph backend.
|