Bug 2233800 - avoid ballooning client_mount_timeout by 10x (5 -> 50 minutes) [7.0]
Summary: avoid ballooning client_mount_timeout by 10x (5 -> 50 minutes) [7.0]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 7.0
Assignee: Radoslaw Zarzynski
QA Contact: skanta
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2237662
TreeView+ depends on / blocked
 
Reported: 2023-08-23 13:25 UTC by Ilya Dryomov
Modified: 2024-04-12 04:25 UTC (History)
17 users (show)

Fixed In Version: ceph-18.2.0-34.el9cp
Doc Type: Bug Fix
Doc Text:
.Increased timeout retry value for `client_mount_timeout` Previously, due to the mishandling of the `client_mount_timeout` configurable, the timeout for authenticating a client to monitors could reach up to 10 retries disregarding its high default value of 5 minutes. With this fix, the previous single-retry behavior of the configurable is restored and the authentication timeout works as expected.
Clone Of: 2216230
Environment:
Last Closed: 2023-12-13 15:22:10 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 61733 0 None None None 2023-08-23 13:25:46 UTC
Red Hat Issue Tracker RHCEPH-7259 0 None None None 2023-08-23 13:26:36 UTC
Red Hat Product Errata RHBA-2023:7780 0 None None None 2023-12-13 15:22:14 UTC

Comment 9 errata-xmlrpc 2023-12-13 15:22:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 7.0 Bug Fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:7780
Comment 10 Red Hat Bugzilla 2024-04-12 04:25:26 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.