Actions
Bug #62659
closedmgr/nfs: report actual errno instead of EIO for single export update failure
Status:
Closed
Priority:
Normal
Assignee:
Category:
python interface
Target version:
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
It makes sense to send a generalised errno(EIO in our case) but if there is just a single error while trying to modify an export using 'ceph nfs export apply <cluster> -i <conf/json file>' then it makes sense to send it's respective errno instead of EIO.
Updated by Dhairya Parmar 9 months ago
- Subject changed from mgr/(object_format && nfs/export): report respective errno instead of EIO in case of a single export update failure to mgr/nfs: report respective errno instead of EIO in case of a single export update failure
Updated by Dhairya Parmar 9 months ago
- Subject changed from mgr/nfs: report respective errno instead of EIO in case of a single export update failure to mgr/nfs: report actual errno instead of EIO for single export update failure
Updated by Dhairya Parmar 9 months ago
- Status changed from New to In Progress
- Pull request ID set to 53240
Updated by Dhairya Parmar 8 months ago
- Status changed from In Progress to New
- Pull request ID deleted (
53240)
Updated by Dhairya Parmar 8 months ago
- Related to Bug #62641: mgr/(object_format && nfs/export): enhance nfs export update failure response added
Updated by Dhairya Parmar 3 months ago
Actions