Actions
Feature #48586
closedmgr/dashboard: Drop invalid RGW client instances, improve logging
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Component - RGW
Target version:
% Done:
0%
Source:
Development
Tags:
Backport:
nautilus, octopus
Description
- Log RGW settings for easier problem tracking.
- Drop RGW client instances that do not exist anymore. This happens when a RGW service is removed via the orchestrator. The Dashboard tries to access the RGW client using the previous settings which leads to an error which might be confusing. Without dropping the error message 'RGW REST API failed request ...' is displayed instead of the correct one 'No RGW found'. Dropping the RGW client instance will produce correct error messages the next time the backend tries to establish a new connection.
Updated by Volker Theile over 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 38406
Updated by Ernesto Puerta over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 3 years ago
- Copied to Backport #48592: octopus: mgr/dashboard: Drop invalid RGW client instances, improve logging added
Updated by Backport Bot over 3 years ago
- Copied to Backport #48593: nautilus: mgr/dashboard: Drop invalid RGW client instances, improve logging added
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 143 to Component - RGW
Actions