Bug #35921
mgr/dashboard: Catch LookupError when checking the RGW status
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Component - RGW
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
This exception is thrown by the RGW client function _determine_rgw_addr(). Without catching that exception a 'The server encountered an unexpected condition which prevented it from fulfilling the request.' will be displayed in the UI instead of displaying a notification panel with a hint that the Object Gateway is not running.
History
#1 Updated by Volker Theile over 5 years ago
- Status changed from New to Fix Under Review
#2 Updated by Ricardo Marques over 5 years ago
- Status changed from Fix Under Review to Resolved
#3 Updated by Ernesto Puerta almost 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 143 to Component - RGW