Actions
Feature #48438
openmgr/dashboard: Drop invalid RGW client instances, improve logging
Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
Component - RGW
Target version:
% Done:
0%
Source:
Tags:
Backport:
octopus
Description
1. Log which settings are used by the backend to connect to a RGW service. This will make it easier to check this in case of problems.
2. After removing a RGW service the UI will show an incorrect error message
because the backend is caching the instance containing the connection information. Showing a 'RGW REST API failed request ...' is incorrect, the message should be 'No RGW found'.
Dropping the invalid instance will show the correct error message when the backend tries to establish a new connection the next time.
Files
Updated by Volker Theile over 3 years ago
- File after_rm_rgw.png after_rm_rgw.png added
Updated by Volker Theile over 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 38406
Updated by Volker Theile over 3 years ago
- Subject changed from mgr/dashboard: Drop invalid RGW client instances to mgr/dashboard: Drop invalid RGW client instances, improve logging
- Description updated (diff)
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 143 to Component - RGW
Actions