Bug 1694948 - The OCS upgrade playbook does not enable server.tcp-user-timeout on all volumes
Summary: The OCS upgrade playbook does not enable server.tcp-user-timeout on all volumes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-ansible
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jose A. Rivera
QA Contact: Prasanth
URL:
Whiteboard:
Depends On:
Blocks: 1703695
TreeView+ depends on / blocked
 
Reported: 2019-04-02 06:55 UTC by Ashmitha Ambastha
Modified: 2019-04-27 17:04 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-18 12:28:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Ashmitha Ambastha 2019-04-02 06:55:30 UTC
Description of problem:
The OCS upgrade playbook misses enabling server.tcp-user-timeout on all volumes. The ansible playbook should be enabling the server.tcp-user-timeout as it is an important part of OCS upgrades. 

The "server.tcp-user-timeout" option specifies the maximum amount of the time (in seconds) the transmitted data from the application can remain unacknowledged from the brick.
It is used to detect force disconnections and dead connections (if a node dies unexpectedly, a firewall is activated, etc.,) early and make it possible for applications to reduce the overall failover time.

OCS upgrade playbook at the path : 

../openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml

Version-Release number of selected component (if applicable): All OCS versions

How reproducible: always. 

Actual results: OCS upgrade playbook does not enable server.tcp-user-timeout to 42 for all the volumes. 

Expected results: OCS upgrade playbook should enable server.tcp-user-timeout to 42 for all the volumes.

Comment 2 Jose A. Rivera 2019-04-04 20:11:43 UTC
Seems like a legit bug.

Comment 3 Raghavendra Talur 2019-04-18 12:28:02 UTC
The requirement to set the server.tcp-user-timeout came because RHGS 3.4.0 was missing it in the code defaults.

With https://bugzilla.redhat.com/show_bug.cgi?id=1623874 and https://code.engineering.redhat.com/gerrit/#/c/150699/, it is part of the RHGS defaults.

If we ask all users to upgrade to v3.11.0 or onwards then we don't have to make any changes in the openshift-ansible.

Closing the bug for the same reason.


Note You need to log in before you can comment on or make changes to this bug.