openstack/ironic-python-agent
Code Issues Proposed changes

Extend the lookup timeout to 600 seconds

Browse Source 
Changes the default lookup timeout to be 600 seconds which
reduces the risk of lookup failing as a write operation
to the backing database is performed upon lookup thanks to
generation of an agent token.

Overall, this is fairly harmless since by default ramdisks
restart the agent if they were not able to successfully
start.

Change-Id: I35c64c0b4f9b3b607df1bc0c4c2a852aa3595cbd
Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/896207
(cherry picked from commit 4efcce5310)
This commit is contained in:
Julia Kreger 2023-08-24 08:29:07 -07:00 committed by Dmitry Tantsur
parent 69f66cf866
commit 30744024d4
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ironic_python_agent/config.py
View File

@ -121,7 +121,7 @@ cli_opts = [
cfg.IntOpt('lookup_timeout',
min=0,
default=int(APARAMS.get('ipa-lookup-timeout', 300)),
default=int(APARAMS.get('ipa-lookup-timeout', 600)),
help='The amount of time to retry the initial lookup '
'call to Ironic. After the timeout, the agent '
'will exit with a non-zero exit code. '

9
releasenotes/notes/extend-ipa-lookup-timeout-05ee5b1372792dbe.yaml Normal file
View File

@ -0,0 +1,9 @@
---
fixes:
- |
The default timeout value for the agent to lookup itself in an Ironic
deployment has been extended to 600 seconds from 300 seconds. This is
to provide better stability for Ironic deployments under heavy load
which may be unable to service new requests. This is particularly true
when the backing database is SQLite for Ironic due to the limited write
concurrency of the database.