Project

General

Profile

Feature #48586

mgr/dashboard: Drop invalid RGW client instances, improve logging

Added by Volker Theile about 1 month ago. Updated 9 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
dashboard/rgw
Target version:
% Done:

0%

Source:
Development
Tags:
Backport:
nautilus, octopus
Reviewed:
Pull request ID:

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.

Related issues

Copied to mgr - Backport #48592: octopus: mgr/dashboard: Drop invalid RGW client instances, improve logging Resolved
Copied to mgr - Backport #48593: nautilus: mgr/dashboard: Drop invalid RGW client instances, improve logging Resolved

History

#1 Updated by Volker Theile about 1 month ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 38406

#2 Updated by Ernesto Puerta about 1 month ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Backport Bot about 1 month ago

  • Copied to Backport #48592: octopus: mgr/dashboard: Drop invalid RGW client instances, improve logging added

#4 Updated by Backport Bot about 1 month ago

  • Copied to Backport #48593: nautilus: mgr/dashboard: Drop invalid RGW client instances, improve logging added

#5 Updated by Nathan Cutler 9 days 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".

Also available in: Atom PDF