Project

General

Profile

Feature #48438

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

Added by Volker Theile about 2 months ago. Updated about 2 months ago.

Status:
Fix Under Review
Priority:
Normal
Assignee:
Category:
dashboard/rgw
Target version:
% Done:

0%

Source:
Tags:
Backport:
octopus
Reviewed:
Affected Versions:
Pull request ID:

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.

after_rm_rgw.png View (22.4 KB) Volker Theile, 12/02/2020 04:35 PM

History

#2 Updated by Volker Theile about 2 months ago

  • Description updated (diff)

#3 Updated by Volker Theile about 2 months ago

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

#4 Updated by Volker Theile about 2 months ago

  • Subject changed from mgr/dashboard: Drop invalid RGW client instances to mgr/dashboard: Drop invalid RGW client instances, improve logging
  • Description updated (diff)

Also available in: Atom PDF