Bug 2109931 - Too frequent async task polling causes delay in timeout detection
Summary: Too frequent async task polling causes delay in timeout detection
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z9
: 16.1 (Train on RHEL 8.2)
Assignee: Takashi Kajinami
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On: 2035406
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-22 13:42 UTC by Takashi Kajinami
Modified: 2024-10-01 19:16 UTC (History)
4 users (show)

Fixed In Version: openstack-tripleo-heat-templates-11.3.2-1.20220725053424.29a02c1.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2035406
Environment:
Last Closed: 2022-12-07 20:29:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1955682 0 None None None 2022-07-25 05:28:04 UTC
Red Hat Issue Tracker OSP-17812 0 None None None 2022-07-22 13:46:17 UTC
Red Hat Product Errata RHSA-2022:8796 0 None None None 2022-12-07 20:30:09 UTC

Description Takashi Kajinami 2022-07-22 13:42:48 UTC
+++ This bug was initially created as a clone of Bug #2035406 +++

Description of problem:

Currently some tasks like paunch uses async mechanism in ansible.
These tasks have the first task to run a long running job asynchronously and the second task to run periodically check status of the first task.

Currently the second polling task is retried every 3 seconds but this interval is not guaranteed and it can be delayed for example there are multiple nodes, and more frequent interval causes more additional overhead. This makes the timeout detection happen very late.

In the real field we saw that the paunch task timed out in a controller node after 1 hour but ansible detected that after 2 hours.


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


How reproducible:
Sometimes, when timeout is detected

Steps to Reproduce:
1.
2.
3.

Actual results:
Timeout is detected a while after the task times out

Expected results:
Timeout is detected immediately after the task times out


Additional info:

Comment 16 errata-xmlrpc 2022-12-07 20:29:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat OpenStack 16.1.9 (openstack-tripleo-heat-templates) security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:8796


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