
The requests to Openstack services hang/fail sometimes due to message loss when connecting to internal service endpoints. This issue was observed before and fixed in commit https://review.opendev.org/#/c/683818/ by setting net.ipv4.tcp_tw_reuse to 0, however, it's still being seen on recent STX loads. It has been tested and proved that requests go through ingress pod do not have the issue. This commit updates helm charts and manifest to make all requests sending to openstack services go to ingress pod and then ingress would forward requests to the corresponding api service. Changes included: - update helm-toolkit manifest job-ks-endpoint.yaml to provide an ability to conditionally configure all types of openstack endpoints with public endpoint url when endpoints.identity.force_public_endpoint is true. Same update for keystone and keystone-api-proxy. With the update, for example, the admin,internal and public endpoints for neutron will be neutron.openstack.svc.cluster.local:80 - update armada manifest to make neccessary overrides in openstack service configuration file to make communications between services go through ingress Change-Id: Icd646dd07d544da420a75f920bd7c3e8fc931327 Closes-Bug: 1880777 Signed-off-by: Angie Wang <angie.wang@windriver.com>
Description
StarlingX OpenStack Armada App
Languages
Python
96.6%
Smarty
1.9%
Makefile
1%
Shell
0.4%