tempest/zuul.d
melanie witt 89a6811cd0 Bump http_timeout in devstack-tempest
In the gate we occasionally see failures like the following:

  urllib3.exceptions.ReadTimeoutError:
    HTTPSConnectionPool(host='10.209.0.62', port=443):
    Read timed out. (read timeout=60)

  urllib3.exceptions.ReadTimeoutError:
    HTTPSConnectionPool(host='10.209.99.246', port=9696):
    Read timed out. (read timeout=60)

where Tempest gives up waiting for an HTTP response after 60 seconds.

It doesn't appear to be related only to one service, as it has been
seen when calling Nova API or Neutron API (the port=9696 example is a
call to Neutron API).

We could try bumping the http_timeout from the default 60 seconds to 90
seconds to see if it helps in slow environments.

Related-Bug: #1999893

Change-Id: I2b2a6a4dee40ee86ca89f6f7f9a83409f8312617
2024-05-30 21:23:56 +00:00
..
base.yaml Bump http_timeout in devstack-tempest 2024-05-30 21:23:56 +00:00
integrated-gate.yaml Merge "Enable tempest cleanup with record_resources in jobs" 2024-05-21 14:21:17 +00:00
project.yaml Switch back the tox constraint to master 2024-05-03 12:26:40 -07:00
stable-jobs.yaml Stop running jobs for stable/zed 2024-05-03 12:17:12 -07:00
tempest-specific.yaml Allow tempest cleanup delete resources based on prefix 2024-03-29 20:14:15 +01:00