From 4af3091c15946cd658fd8ceade96f30d1f554804 Mon Sep 17 00:00:00 2001 From: marvin Date: Tue, 16 Jul 2019 11:19:25 +0800 Subject: [PATCH] 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 --- .../stx-openstack-helm/manifests/manifest.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml b/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml index da21198b1a..6ed9d5901e 100644 --- a/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml +++ b/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml @@ -1249,6 +1249,7 @@ data: max_overflow: 64 max_pool_size: 1 idle_timeout: 60 + rpc_response_max_timeout: 60 router_status_managed: true vlan_transparent: true wsgi_default_pool_size: 100