neutron helm override needs to set rpc_response_max_time to 60secs

[Ghada Khalil]

Brief Description
-----------------
In stx.1.0, stx-neutron hard-coded the rpc_response_max_timeout value to 60 seconds. With the migration to containers and upstream neutron, this patch was dropped and the default is now set to 600 seconds. To align with the previous starlingx behavior, the networking TL (Matt Peters) recommended that the default be set to 60 seconds by the system through a neutron helm override.

Severity
--------
Potentially major -- If the maximum rpc timeout is too big, some requests which should fail will be held for a long time before the server returns failure.

Steps to Reproduce
------------------
# On a running system, verify the rpc_response_max_timeout in neutron.conf
kubectl get pod -n openstack | grep neutron
kubectl exec -it $neutron-server -n openstack bash
cat /etc/neutron/neutron.conf | grep rpc_response_max_timeout

Expected Behavior
------------------
rpc_response_max_timeout should be set to 60 seconds; the default in stx.1.0

Actual Behavior
----------------
rpc_response_max_timeout is not set and therefore defaults to 600 seconds; the upstream openstack default

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
Any

Branch/Pull Time/Commit
-----------------------
Any recent load w/ container support

Last Pass
---------
Never

Timestamp/Logs
--------------
Not required

Test Activity
-------------
N/A - this came up in discussions with the test team about the user overriding this setting

[Ghada Khalil (gkhalil)]

Marking as stx.2.0 - agreed with networking TL that we should align the timeout to the value previously used by starlingx neutron

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/670959

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/670959
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=4af3091c15946cd658fd8ceade96f30d1f554804
Submitter: Zuul
Branch: master

commit 4af3091c15946cd658fd8ceade96f30d1f554804
Author: marvin <email address hidden>
Date: Tue Jul 16 11:19:25 2019 +0800

    Change rpc_response_max_timeout default to 60 seconds

    In stx.1.0, stx-neutron hard-coded the rpc_response_max_timeout value
    to 60 seconds. With the migration to containers and upstream neutron,
    the default is now set to 600 seconds. To align with the previous
    starlingx behavior, the rpc_response_max_timeout set to 60 seconds
    by the system through a neutron helm override.

    Change-Id: Ibf0f591ac9cb05dac09add37b3c31f6f5b66446d
    Closes-Bug: #1836413
    Signed-off-by: marvin <email address hidden>